Author: azeez Date: Thu May 29 04:38:31 2008 New Revision: 17583 URL: http://wso2.org/svn/browse/wso2?view=rev&revision=17583
Log: updated docs Modified: trunk/wsas/java/modules/documentation/src/site/xdoc/installation_guide.xml Modified: trunk/wsas/java/modules/documentation/src/site/xdoc/installation_guide.xml URL: http://wso2.org/svn/browse/wso2/trunk/wsas/java/modules/documentation/src/site/xdoc/installation_guide.xml?rev=17583&r1=17582&r2=17583&view=diff ============================================================================== --- trunk/wsas/java/modules/documentation/src/site/xdoc/installation_guide.xml (original) +++ trunk/wsas/java/modules/documentation/src/site/xdoc/installation_guide.xml Thu May 29 04:38:31 2008 @@ -167,7 +167,7 @@ <h1>Installing WSO2 Web Services Application Server [EMAIL PROTECTED]@ in the Standalone Mode</h1> -<a name="win"></a> +<a name="win"></a> <a name="Installing1"/> <h2 id="Installing">Installing on Microsoft Windows</h2> @@ -220,7 +220,7 @@ Check your WSO2 WSAS instance using the URL https://localhost:9443 </p> -<a name="linux"></a> +<a name="linux"></a> <h2 id="Installing2">Installing on Linux</h2> @@ -230,7 +230,7 @@ <li><a href="#linux_binary_installers">Using Binary Installers (deb/rpm)</a></li> </ol> -<a name="linux_binary"></a> +<a name="linux_binary"></a> <h3 id="Installing3">Installing using Binary Distribution</h3> <ol> @@ -247,7 +247,7 @@ <li>Check your WSO2 WSAS instance using the URL https://localhost:9443</li> </ol> <!--<h3>Troubleshooting Installation</h3>--> -<a name="linux_binary_installers"></a> +<a name="linux_binary_installers"></a> <h3 id="Installing4">Installing using Binary Installers (deb/rpm)</h3> @@ -269,7 +269,7 @@ (You can also stop the server from the shell. e.g., /etc/init.d/wso2wsas stop) </li> </ol> -<a name="linux_trouble"></a> +<a name="linux_trouble"></a> <h3 id="Troublesho">Troubleshooting Installation</h3> @@ -277,7 +277,7 @@ /usr/bin/wso2wsas (after WSO2 WSAS , [EMAIL PROTECTED]@ has been installed), if the error message 'Permission denied' pops up, then check the file permission of the run.sh script and set the execution permission.</p> -<a name="uninstall"></a> +<a name="uninstall"></a> <h2 id="Modify">Remove Installation</h2> @@ -311,7 +311,7 @@ <p>In <strong>Redhat Linux</strong> systems, use the rpm utility to remove the WSO2 WSAS installation. e.g.,: rpm -e [EMAIL PROTECTED]@</p> -<a name="mgtconsole"></a> +<a name="mgtconsole"></a> <h2 id="Accessing">Accessing the Management Console</h2> @@ -346,7 +346,7 @@ <p>Your feedback on WSO2 WSAS is most appreciated. Please send them to our <a href="mail-lists.html">mailing lists</a>.</p> -<a name="intro"></a> +<a name="intro"></a> <h2 id="Introducti1">Introduction</h2> @@ -356,12 +356,13 @@ <p>WSO2 WSAS 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 name="app_servers"></a> +<a name="app_servers"></a> <h3 id="J2EE">J2EE Application Servers</h3> <p><strong>Apache Tomcat Server:</strong></p> <ul> + <li><a href="#Tomcat6.0.x">version 6.0.x</a></li> <li><a href="#Tomcat5.5.x">version 5.5.x</a></li> <li><a href="#Tomcat5.0.x">version 5.0.x</a></li> <li><a href="#Tomcat4.1.x">version 4.1.x</a></li> @@ -370,7 +371,7 @@ <p><strong>JBoss AS:</strong></p> <ul> <li><a href="#JBoss">version 3.2.x</a></li> - <li><a href="#JBoss">version 4.0.x</a></li> + <li><a href="#JBoss">version 4.x.x</a></li> </ul> <p><strong>Apache Geronimo AS:</strong></p> @@ -391,10 +392,10 @@ described below.</p> <a name="req"></a> <!--<h2>Setting up the Environment and Tools</h2>--> <!--<h2>Upgrading from Previous Versions</h2>--> - <a name="specific"></a> + <a name="specific"></a> <h2 id="Applicatio">Application Server Specific Information</h2> -<a name="specific_installation"></a> +<a name="specific_installation"></a> <h3 id="Installati">Installation Instructions</h3> @@ -469,18 +470,48 @@ <a id="tom"></a> <h4><strong>Apache Tomcat Server:</strong></h4> -<a id="Tomcat5.5.x"></a> +<a id="Tomcat6.0.x"></a> -<p><strong>a) Version 5.5.x</strong></p> +<p><strong>a) Version 6.0.x</strong></p> -<p>1. Enabling SSL on Tomcat</p> + <p>1. Enabling SSL</p> + <p>To enable SSL on Tomcat 6.0.x the server XML should contain the following + segment:</p> + <pre> + <Connector port="9443" protocol="HTTP/1.1" SSLEnabled="true" + maxThreads="150" scheme="https" secure="true" + clientAuth="false" sslProtocol="TLS" + keystoreFile="wso2wsas/conf/wso2wsas.jks" keystorePass="wso2wsas"/> + </pre> + + <p>2. Registering the WSO2 WSAS Data Store</p> + <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" + auth="Container" + type="javax.sql.DataSource" + maxActive="100" + maxIdle="30" + maxWait="10000" + username="wso2wsas" + password="wso2wsas" + driverClassName="org.apache.derby.jdbc.EmbeddedDriver" + url="jdbc:derby:../database/WSO2WSAS_DB"/> + </Context> + </pre> +<p><strong>b) Version 5.5.x</strong></p> + +<p>1. Enabling SSL</p> <p>To enable SSL on Tomcat 5.5.x the server XML should contain the following segment:</p> <pre> <Connector port="9443" maxHttpHeaderSize="8192" maxThreads="150" minSpareThreads="25" - maxSpareThreads="75" - enableLookups="false" disableUploadTimeout="true" + maxSpareThreads="75" + enableLookups="false" disableUploadTimeout="true" acceptCount="100" scheme="https" secure="true" clientAuth="false" sslProtocol="TLS" keystoreFile="wso2wsas/conf/wso2wsas.jks" @@ -507,9 +538,9 @@ </Context></pre> <a id="Tomcat5.0.x"></a> -<p><strong>b) Version 5.0.x</strong></p> +<p><strong>c) Version 5.0.x</strong></p> -<p>1. Enabling SSL on Tomcat</p> +<p>1. Enabling SSL</p> <p>To enable SSL on Tomcat 5.0.x the server XML should contain the following segment</p> @@ -544,7 +575,7 @@ </Context></pre> <a id="Tomcat4.1.x"></a> -<p><strong>c) Version 4.1.x</strong></p> +<p><strong>d) Version 4.1.x</strong></p> <p>1. Enabling SSL on Tomcat</p> @@ -552,7 +583,7 @@ segment</p> <pre><Connector className="org.apache.coyote.tomcat4.CoyoteConnector" port="9443" minProcessors="5" maxProcessors="75" - enableLookups="true" + enableLookups="true" acceptCount="100" debug="0" scheme="https" secure="true" @@ -590,12 +621,13 @@ <h4><strong>2. JBoss AS</strong></h4> -<p><strong><a>Version 3.2.x and 4.0.x</a></strong></p> +<p><strong><a>Version 3.2.x and 4.x.x</a></strong></p> <p>1. Enabling SSL on JBoss</p> <p>To enable SSL on JBoss, add the following segment to - JBOSS_HOME/server/default/deploy/jbossweb-tomcatxx.sar/server.xml as a child + JBOSS_HOME/server/default/deploy/jbossweb-tomcatxx.sar/server.xml or + JBOSS_HOME/server/default/deploy/jboss-web.deployer/server.xml as a child of the jboss.web Service element.</p> <pre><Connector port="9443" address="${jboss.bind.address}" maxThreads="100" strategy="ms" maxHttpHeaderSize="8192" @@ -641,7 +673,7 @@ 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> +<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> _______________________________________________ Wsas-java-dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/wsas-java-dev
