此内容没有您所选择的语言版本。
2.6. Running on a Solaris Installation
Red Hat Enterprise Web Server consists of Apache Httpd and Apache Tomcat and the set of components needed to run them. These components can be run with the following users and groups who are created after installation:
Running Tomcat version 5 or 6
In order to run Tomcat on Solaris, some service configuration files will need manual editing.
Editing the Tomcat service entails uncommenting and setting the
JAVA_HOME variable to the desired JDK in the configuration file. The configuration file can be found at:
For Tomcat 5:
/opt/redhat/ews/etc/sysconfig/tomcat5
For Tomcat 6:
/opt/redhat/ews/etc/sysconfig/tomcat6
To run Tomcat 5 or 6, the following command must be run as root:
For Tomcat 5:
sbin/tomcat5 start
For Tomcat 6:
sbin/tomcat6 start
By running one of the above commands, the configuration file is read and the user and group are changed to that of the tomcat user account before the
catalina.sh script is executed.
The
catalina.sh script file can be found within:
For Tomcat 5:
/opt/redhat/ews/share/tomcat5/bin
For Tomcat 6:
/opt/redhat/ews/share/tomcat6/bin
To stop Tomcat, one of the following commands can be executed:
For Tomcat 5:
sbin/tomcat5 stop
For Tomcat 6:
sbin/tomcat6 stop
By default,
tomcat-native is automatically added to the LD_LIBRARY_PATH and -Djava.library.path during Tomcat startup. The catalina.sh script detects the running JVM version and adds the /opt/redhat/ews/lib path (/opt/redhat/ews/lib64 for 64 bit JVM) to the library path.
To run Tomcat as a service, use the provided scripts within the
/opt/redhat/ews/etc/init.d directory. The following commands can be used to copy the necessary scripts:
For Tomcat 5:
cp /opt/redhat/ews/etc/init.d/tomcat6 /etc/rc3.d/S70tomcat5
cp /opt/redhat/ews/etc/init.d/tomcat6 /etc/rcS.d/K20tomcat5
For Tomcat 6:
cp /opt/redhat/ews/etc/init.d/tomcat6 /etc/rc3.d/S70tomcat6
cp /opt/redhat/ews/etc/init.d/tomcat6 /etc/rcS.d/K20tomcat6
For information on how to choose the
init level numbers, consult your Solaris documentation. The preferred method of service management is through the Solaris Service Management Facility. In order to read more about this facility, consult the smf(5) manual.
Running the HTTP Server
Apache httpd configuration files are located inside the /opt/redhat/ews/etc/httpd directory. By default all supported modules are loaded and enabled, so it is advised that you edit the httpd.conf file and disable the modules you don't need.
Starting the HTTP server is performed using the provided
apachectl script located inside the /opt/redhat/ews/sbin directory. The apachectl script uses the configuration script, where you can edit and select various startup parameters, including the running of mpm. The file used is /opt/redhat/ews/etc/sysconfig/httpd
To start the HTTP Server, use the following command:
sbin/apachectl start
To stop the HTTP Server, use the following command:
sbin/apachectl stop
If you want your server to continue running automatically after a system reboot, a call to the
apachectl script should be added to your system startup files.
Note
For complete documentation on how to start and stop the HTTP Server, refer to the files,
docs/httpd/invoking.html and docs/httpd/stopping.html respectively.
Running the mod_jk
Running mod_jk on Solaris is the same as running the package on Red Hat Enterprise Linux installed via zip. For detailed instructions see Running the mod_jk