[jboss-cvs] JBossAS SVN: r85199 - projects/docs/enterprise-EWS/1.0.0/Release_Notes/en-US.
jboss-cvs-commits at lists.jboss.org
jboss-cvs-commits at lists.jboss.org
Tue Mar 3 19:23:04 EST 2009
Author: irooskov at redhat.com
Date: 2009-03-03 19:23:04 -0500 (Tue, 03 Mar 2009)
New Revision: 85199
Modified:
projects/docs/enterprise-EWS/1.0.0/Release_Notes/en-US/Release_Notes.xml
Log:
updated release notes with updated information for running a zip installation
Modified: projects/docs/enterprise-EWS/1.0.0/Release_Notes/en-US/Release_Notes.xml
===================================================================
--- projects/docs/enterprise-EWS/1.0.0/Release_Notes/en-US/Release_Notes.xml 2009-03-03 23:27:09 UTC (rev 85198)
+++ projects/docs/enterprise-EWS/1.0.0/Release_Notes/en-US/Release_Notes.xml 2009-03-04 00:23:04 UTC (rev 85199)
@@ -298,7 +298,38 @@
<formalpara>
<title>Running Tomcat version 5 or 6</title>
<para>
- After extracting the zip file, update the config file to suit your installation. For Tomcat version 5 this will be <filename>tomcat5/conf/tomcat5.conf</filename> and for Tomcat version 6 it will be <filename>tomcat6/conf/tomcat6.conf</filename>.
+ After extracting the zip file, check to see if a user called <varname>tomcat</varname> exists on the system by running the following command:
+ </para>
+<programlisting>
+id tomcat
+</programlisting>
+ <para>
+ If the user does not exist then it will need to be added, along with the appropriate usergroup. In order to achieve this, execute the following:
+ </para>
+<programlisting>
+groupadd -g 91 -r tomcat 2> /dev/null || :
+useradd -c "Tomcat" -u 91 -g tomcat -s /bin/sh -r -d /home/tomcat tomcat 2> /dev/null || :
+</programlisting>
+ <para>
+ Once this is completed, if the <varname>tomcat</varname> user will be running Tomcat, then the ownership of the tomcat directories will need to be changed to reflect this:
+ </para>
+ <para>
+ For Tomcat 5:
+ </para>
+<programlisting>
+chown -R tomcat:tomcat tomcat5
+</programlisting>
+ <para>
+ For Tomcat 6:
+ </para>
+<programlisting>
+chown -R tomcat:tomcat tomcat6
+</programlisting>
+ <para>
+ To test that the above commands have been successful, check that the <varname>tomcat</varname> user has execution permission to the tomcat install path.
+ </para>
+ <para>
+ Now update the config file to suit your installation. For Tomcat version 5 this will be <filename>tomcat5/conf/tomcat5.conf</filename> and for Tomcat version 6 it will be <filename>tomcat6/conf/tomcat6.conf</filename>.
</para>
</formalpara>
<para>
@@ -346,8 +377,36 @@
<formalpara>
<title>Running the HTTP Server</title>
<para>
- After extracting the zip file, update the configuration file, <filename>httpd/conf/httpd.conf</filename>, as needed. Then change to the subdirectory <filename>httpd/bin</filename>.
+ After extracting the zip file, check to see if a user called <varname>apache</varname> exists on the system by running the following command:
</para>
+<programlisting>
+id apache
+</programlisting>
+ <para>
+ If the user does not exist then it will need to be added. In order to achieve this, execute the following:
+ </para>
+<programlisting>
+useradd -c "Apache" -u 48 -s /sbin/nologin -r -d install_path/httpd/www apache 2> /dev/null || :
+</programlisting>
+ <para>
+ Once this is completed, if the <varname>apache</varname> user will be running the http server, then the ownership of the httpd directories will need to be changed to reflect this:
+ </para>
+<programlisting>
+chown -R apache:root httpd
+</programlisting>
+ <para>
+ In order to login as the <varname>apache</varname> user, execute:
+ </para>
+<programlisting>
+su -s /bin/bash apache
+</programlisting>
+ <para>
+ To test that the above commands have been successful, check that the <varname>apache</varname> user has execution permission to the httpd install path.
+ </para>
+ </para>
+ <para>
+ Now update the configuration file, <filename>httpd/conf/httpd.conf</filename>, as needed. Then change to the subdirectory <filename>httpd/bin</filename>.
+ </para>
</formalpara>
<para>
Start the HTTP server by executing:
@@ -370,16 +429,24 @@
<formalpara>
<title>Running Apache Tomcat Native</title>
<para>
- In order to use the native library for Tomcat, the <varname>LD_LIBRARY_PATH</varname> variable must point to the library. For example if it's in <filename>$CATALINA_HOME/lib</filename>, then set the following:
+ In order to use the native library for Tomcat, the <varname>LD_LIBRARY_PATH</varname> variable must point to the library.
</para>
</formalpara>
+ <para>
+ For Tomcat 5 set the following:
+ </para>
<programlisting>
-LD_LIBRARY_PATH=$LD_LIBRARY_PATH:$CATALINA_HOME/lib
-export LD_LIBRARY_PATH
+export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:$CATALINA_HOME/server/lib
</programlisting>
<para>
- Since it depends on the <filename>apr</filename> package, it's best to install <filename>libapr-1.so</filename> at the same place as the above library.
+ For Tomcat 6 set the following:
</para>
+<programlisting>
+ export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:$CATALINA_HOME/lib
+</programlisting>
+ <!-- <para>
+ Since it depends on the <filename>apr</filename> package, it is best to install <filename>libapr-1.so</filename> at the same place as the above library.
+ </para> -->
<para>
Start Tomcat and check that you see a message similar to:
</para>
@@ -391,6 +458,9 @@
Feb 8, 2008 12:27:41 PM org.apache.coyote.http11.?Http11AprProtocol init
INFO: Initializing Coyote HTTP/1.1 on http-8080
</screen>
+ <para>
+ In order to use <classname>log4j</classname> logging in Tomcat 6, copy the content of the <filename>extras/</filename> directory into the <filename>lib/</filename> directory and restart Tomcat.
+ </para>
</section>
</section>
More information about the jboss-cvs-commits
mailing list