[wsas-java-dev] svn commit r457 - wsas/java/trunk/xdocs
svn at wso2.com
svn at wso2.com
Tue Jan 16 21:44:08 PST 2007
Author: marietta
Date: Tue Jan 16 21:44:03 2007
New Revision: 457
Modified:
wsas/java/trunk/xdocs/installation_servlet.html
Log:
Reviewed.
Modified: wsas/java/trunk/xdocs/installation_servlet.html
==============================================================================
--- wsas/java/trunk/xdocs/installation_servlet.html (original)
+++ wsas/java/trunk/xdocs/installation_servlet.html Tue Jan 16 21:44:03 2007
@@ -6,19 +6,18 @@
<meta http-equiv="content-type" content="text/html; charset=iso-8859-1" />
<title>WSO2 Web Services Application Server Servlet Edition
@wso2wsas_version@ - Installation Guide</title>
- <link href="tools/cmd/css/wsas-dist-doc.css" rel="stylesheet" type="text/css"
- media="all" />
+ <link href="tools/cmd/css/wsas-dist-doc.css" rel="stylesheet"
+ type="text/css" media="all" />
</head>
<body>
<h1>WSO2 Web Services Application Server Servlet Edition for Java,
v at wso2wsas_version@ - Installation Guide</h1>
-<p>This installation guide provides details about
-installation of the WSO2 WSAS Servlet Edition for Java.
-This also includes information on how to configure WSO2 WSAS on JBoss,
-Geronimo & Tomcat servers. Some guidelines on installing WSO2 WSAS on other application servers
-has also been included.</p>
+<p>This installation guide provides instructions on how to install the WSO2
+WSAS Servlet Edition for Java. This also includes information on how to
+configure WSO2 WSAS on JBoss, Geronimo and Tomcat servers. Some guidelines on
+installing WSO2 WSAS on other application servers have also been included.</p>
<p>Your feedback on WSO2 WSAS for Java is most appreciated. Please send them
to our <a href="index.html#mail">mailing lists</a>.</p>
@@ -65,9 +64,9 @@
WSO2 WSAS Servlet Edition for Java:
wso2wsas-servlet-edition-java- at wso2wsas_version@.zip</p>
-<p>WSO2 WSAS Servlet Edition has been fully tested on the following J2EE
-Application Servers and specific installation instructions for each these
-servers are listed under <a href="#specific">Application Server Specific
+<p>The WSO2 WSAS Servlet Edition has been fully tested on the following J2EE
+Application Servers, and specific installation instructions for each server
+are listed under the <a href="#specific">Application Server Specific
Installation</a> section.</p>
<a id="app_servers"></a>
@@ -93,9 +92,9 @@
<p><strong>General:</strong></p>
-<p>Web application servers which do not fall under the above list will have
-to follow the <a href="#gen">Generic Application Server Installation
-Steps</a> described below.</p>
+<p>Web application servers that do not fall under the above list will have to
+follow the <a href="#gen">Generic Application Server Installation Steps</a>
+described below.</p>
<a id="req"></a>
<h2>System Requirements</h2>
@@ -116,7 +115,7 @@
<td>Disk</td>
<td>No minimum requirement.
- <p>Approximately 40 MB will be used for war distribution</p>
+ <p>Approximately 40 MB will be used for WAR distribution</p>
</td>
</tr>
<tr>
@@ -136,7 +135,7 @@
<h3>Installation Instructions</h3>
<p>Follow the simple installation steps to successfully install WSO2 WSAS
-into JBoss AS, Apache Geronimo AS or Apache Tomcat server.</p>
+into a JBoss AS, Apache Geronimo AS or Apache Tomcat server.</p>
<p>1. Unzip wso2wsas-servlet-edition-java- at wso2wsas_version@.zip</p>
@@ -147,19 +146,19 @@
<p>4. Select the application server and its version.</p>
-<p>5. After this point there are a few application server specific steps to
-follow:</p>
+<p>5. After this point, there are a few application server specific steps to
+be followed:</p>
<p><strong>Apache Tomcat Server:</strong></p>
<ul>
- <li>Enter tomcat HOME directory</li>
+ <li>Enter Tomcat HOME directory</li>
<li>Prompts whether to replace the existing server.xml
<ul>
- <li>if answer is 'no', then, follow these <a href="#tom">advanced
+ <li>If the answer is No, then, follow the <a href="#tom">advanced
configuration steps</a></li>
- <li>if answer is 'yes', existing server.xml is backed up, then replaced
- with the default server.xml shipped with WSO2 WSAS Servlet Edition
- for Java</li>
+ <li>If the answer is Yes, the existing server.xml is backed up, and
+ then replaced with the default server.xml shipped with the WSO2 WSAS
+ Servlet Edition for Java</li>
</ul>
</li>
</ul>
@@ -167,32 +166,33 @@
<p><strong>JBoss AS:</strong></p>
<ul>
<li>Enter JBoss HOME directory</li>
- <li>Select configuration file set into which WSO2 WSAS for Java will be
- installed from the given options</li>
+ <li>Select the set of configuration files into which WSO2 WSAS for Java
+ will be installed from the given options.</li>
<li>Prompts whether to replace the existing server.xml
<ul>
- <li>if answer is 'no', then, follow these <a href="#JBoss">advanced
+ <li>If the answer is No, then, follow the <a href="#JBoss">advanced
configuration steps</a></li>
- <li>if answer is 'yes', existing Tomcat server.xml backed up and then
- replaced with the default JBoss-Tomcat server.xml shipped with WSO2
- WSAS</li>
+ <li>If the answer is Yes, the existing Tomcat server.xml is backed up,
+ and then replaced with the default JBoss-Tomcat server.xml shipped
+ with WSO2 WSAS</li>
</ul>
</li>
</ul>
-<p>6. Some specific libraries and application server specific files will be
-copied to the relevant directories</p>
+<p style="text-indent: 29pt"> Some specific libraries and application server
+specific files will be copied to the relevant directories.</p>
<p>7. Restart the application server.</p>
-<p>8. Now the Management Console should be available on
-https://localhost:9443/wso2wsas if you used the default settings.</p>
-<a id="specific_config"></a>
+<p style="text-indent: 10pt">Now the Management Console should be available
+on https://localhost:9443/wso2wsas if you used the default settings.</p>
+
+<p><a id="specific_config"></a></p>
<h3>Advanced Configuration Instructions</h3>
<p>We support the following Application Servers out of the box with our
-installer. However, if you wish to manually carry out the configuration the
+installer. However, if you wish to manually carry out the configuration, the
following tips will be helpful:</p>
<a id="tom"></a>
@@ -219,7 +219,7 @@
<p>2. Registering the WSO2 WSAS Data Store</p>
-<p>To register the data source include the following segment in the
+<p>To register the data source, include the following segment in the
server.xml within the 'host' element</p>
<pre><Context path="/wso2wsas" >
<Resource name="jdbc/wso2wsas_db"
@@ -254,8 +254,8 @@
<p>2. Registering the WSO2 WSAS Data Store</p>
-<p>To register the data store include the following segment in the server.xml
-within the 'host' element</p>
+<p>To register the data store, include the following segment in the
+server.xml within the 'host' element</p>
<pre><Context path="/wso2wsas" docBase="tungsten"
reloadable="true" crossContext="true">
<Resource name="jdbc/wso2wsas_db" auth="Container"
@@ -298,7 +298,7 @@
<p>2. Registering the WSO2 WSAS Data Store</p>
-<p>To register Tungsten data store include the following segment in the
+<p>To register the Tungsten data store, include the following segment in the
server.xml within the 'host' element</p>
<pre><Context path="/wso2wsas" docBase="wso2wsas"
reloadable="true" crossContext="true">
@@ -322,7 +322,7 @@
<p>1. Enabling SSL on JBoss</p>
-<p>To enable SSL on JBoss add the following segment to
+<p>To enable SSL on JBoss, add the following segment to
JBOSS_HOME/server/default/deploy/jbossweb-tomcatxx.sar/server.xml as a child
of the jboss.web Service element.</p>
<pre><Connector port="9443" address="${jboss.bind.address}"
@@ -337,7 +337,7 @@
<p>2. Registering the WSO2 WSAS Data Source</p>
-<p>To register the data source create wso2wsas-derby-ds.xml file in
+<p>To register the data source, create the wso2wsas-derby-ds.xml file in
JBOSS_HOME/server/default/deploy with the following text:</p>
<pre><?xml version="1.0" encoding="UTF-8"?>
<datasources>
@@ -357,25 +357,25 @@
<p>1. Creating connectors with Geronimo</p>
-<p>The easiest way to manage the Geronimo server is using the management
-console. The management console can be accessed from the url
-http://localhost:8080/console. Default user name is system and password is
-manager. Web server connectors can be managed by using the "Web Server" link
-found under the "Console Navigation".</p>
+<p>The easiest way to manage the Geronimo server is by using the management
+console. The management console can be accessed from the URL
+http://localhost:8080/console. The default user name is <em>system</em>, and
+the password is <em>manager</em>. Web server connectors can be managed by
+using the "Web Server" link found under the "Console Navigation".</p>
<p>2. Deploying data sources</p>
-<p>Data sources can also be created easily with the management console, using
-the "Data pools" link found under the "Console Navigation". Deployer tool can
-also be used to deploy a data source if deploy plan is present. In this case
-use the following command.</p>
+<p>Data sources can also be easily created with the management console, using
+the "Data pools" link found under the "Console Navigation". The Deployer tool
+can also be used to deploy a data source if a deploy plan is present. In this
+case, use the following command.</p>
<pre>java -jar bin/deployer.jar --user system --password manager deploy <path to deploy plan>
repository/tranql/tranql-connector/1.2/tranql-connector-1.2.rar</pre>
<p>3. Deploying Web applications</p>
-<p>Deployer tool can be used to deploy web applications. Use the following
-command.</p>
+<p>The Deployer tool can be used to deploy web applications. Use the
+following command.</p>
<pre>java -jar bin/deployer.jar --user system --password manager deploy <pathto Web application></pre>
<a id="note"></a>
@@ -387,17 +387,17 @@
conflicts with the older version used by JBoss.</li>
</ul>
<ul>
- <li>On JBoss version 4.0.0 and possibly some other versions if the
+ <li>On JBoss version 4.0.0 and possibly some other versions, if the
jboss-ws4ee.sar is present inside the deploy directory, the admin service
- will not start due to a conflict in the WSDL API. In this case the
+ will not start due to a conflict in the WSDL API. In this case, the
jboss-ws4ee.sar needs to be completely removed from the deploy
directory</li>
</ul>
<ul>
- <li>On JBoss version 4.0.0 and possibly other versions the ant.jar file
+ <li>On JBoss version 4.0.0 and possibly other versions, the ant.jar file
included inside the jbossweb-tomcat50.sar may cause problems with the
- code generation. In order to ensure smooth operation replace the ant.jar
- with the ant-1.6.x.jar found in the wso2wsas lib folder. Also the
+ code generation. In order to ensure a smooth operation, replace the
+ ant.jar with the ant-1.6.x.jar found in the wso2wsas lib folder. Also the
ant-nodeps-x.x.x.jar needs to be copied into the
jbossweb-tomcat50.sar.</li>
</ul>
@@ -427,8 +427,8 @@
</category></pre>
<ul>
<li>In MacOSX the classes.jar needs to be copied into the commons/lib dir
- of Tomcat installation in order to run the generate client and 'try it!'
- features.</li>
+ of the Tomcat installation in order to run the generate client and 'Try
+ it!' features.</li>
</ul>
<a id="gen"></a>
@@ -437,12 +437,12 @@
<h3>Installation Instructions</h3>
For Web application servers other than JBoss, Apache Tomcat and Geronimo,
-follow the installation steps as given below.
+follow the installation steps as given below.
<ol>
<li>Unzip wso2wsas-servlet-edition-java-1.1.zip</li>
<li>Run install.sh for Linux or install.bat for MS Windows from
wso2wsas-servlet-edition-java-1.1/bin</li>
- <li>Select the WSO2WSAS_HOME. </li>
+ <li>Select the WSO2WSAS_HOME.</li>
<li>Select the Application Server's WAR file deployment directory.</li>
<li>Configure HTTP, HTTPS and configure the WSO2 WSAS JNDI datasource. See
<a href="#gen_config">advanced configurations</a> for more details</li>
@@ -452,23 +452,23 @@
</ol>
<h3>Advanced Configuration</h3>
-1. Register a JNDI datasource with JNDI name jdbc/wso2wsas_db Use the
+1. Register a JNDI datasource with the JNDI name jdbc/wso2wsas_db Use the
following details to configure this datasource;
<pre> a. Database Driver : org.apache.derby.jdbc.EmbeddedDriver
b. Database URL : e.g. jdbc:derby:/wso2wsas/WSO2WSAS_DB
c. Database Username : wso2wsas
d. Database Password : wso2wsas</pre>
-<p>NOTE: You should provide the correct path to the WSO2 WSAS Database in the
-Database URL</p>
+<p>NOTE: You should provide the correct path to the WSO2 WSAS database in the
+database URL</p>
<p>2. Copy the wso2wsas-servlet-edition-java-1.1/lib/derby-10.1.1.0.jar and
the wso2wsas-servlet-edition-java-1.1/lib/log4j-1.2.13.jar to your
-application servers classpath.</p>
+application server's classpath.</p>
<p>3. Copy the JDK tools.jar (in the case of Windows and Linux JDKs) or
-classes.jar(in the case of Mac OS X), to your App server's classpath, if they
-are not already added to the App server's classpath.</p>
+classes.jar (in the case of Mac OS X) to your application server's classpath,
+if they have not been added to the application server's classpath already.</p>
<p>4. Enable SSL on your application layer. If you intend to use the key
store file shipped with wso2wsas, you should point your application server to
@@ -485,11 +485,11 @@
after WSO2 WSAS has been successfully installed on your application
server.</p>
-<h3>1. wso2wsas.properties file</h3>
+<h3>1. The wso2wsas.properties file</h3>
-<p>This file is created during installation and can be located at
-wso2wsas.war/WEB-INF/classes/wso2wsas.properties, in your application servers
-webapp deployment directory.</p>
+<p>This file is created during installation and may be located at
+wso2wsas.war/WEB-INF/classes/wso2wsas.properties, in your application
+server's webapp deployment directory.</p>
<p>The wso2wsas.home and other application server specific properties can be
changed by modifying this file. You may have to re-archive the wso2wsas.war
@@ -508,12 +508,11 @@
<h3>3. Changing HTTP/HTTPS ports</h3>
<p>In your application server's configuration file, locate the section where
-these ports have been registered, and changed it to the appropriate
-values.</p>
+the ports have been registered, and changed it to the appropriate values.</p>
<p>If you carried out a Generic installation, in addition to modifying your
-application servers' configuration file, you also have to modify the
-server.xml file which can be found at WSO2WSAS_HOME/conf.</p>
+application server's configuration file, you also have to modify the
+server.xml file, which can be found at WSO2WSAS_HOME/conf.</p>
<a id="mgtconsole"></a>
<h2>Accessing the Management Console</h2>
@@ -525,7 +524,7 @@
(if you are using the default settings). This will take you to the "Sign In"
page of the Management Console seen as below.</p>
-<p><strong>Note:</strong> WSO2 WSAS by default has two listeners; HTTP and
+<p><strong>Note:</strong> By default, WSO2 WSAS has two listeners; HTTP and
HTTPS. The HTTP listener opens on port 9762, while the HTTPS listener opens
on port 9443. The admin functionality is exposed only via HTTPS.</p>
More information about the Wsas-java-dev
mailing list