9.3. Use Jsvc with Tomcat 6
Unlike Tomcat 7, there is no wrapper script available to use when running Jsvc with Tomcat 6. Users can write their own scripts for this purpose using the configuration parameters described in the following table:
| Options | Default Value | Description |
|---|---|---|
-home | /home2/java/j2sdk{version} | The Java home directory location. Tomcat 6 requires JDK version 1.6 or later. |
-Dcatalina.home | /opt/jboss-ews-2.0/tomcat6 | The Tomcat installation directory. |
-user | tomcat | The user Tomcat uses. |
-Djava.io.tmpdir | /var/tmp | The temporary directory used by Tomcat 6. |
-pidfile | /var/run/jsvc.pid | The file where the process ID (PID) for the running instance of Tomcat is stored. |
-Dcatalina.base | /opt/jboss-ews-2.0/tomcat6 | The directory that contains the specific configuration and set up information if multiple servers are using the same installation. |
-outfile | stdout | The file where the stdout output of the embedded Java Virtual Machine is redirected. |
-errfile | stderr | The file where the stderr output of the Java Virtual Machine is redirected. |
-stop | - | Stops Jsvc cleanly. The PID file location set with the -pidfile parameter contains information created when Jsvc starts. This file and its information is used to stop the Jsvc instance. |
Parameters that are used after specifying an option (for example, the parameters in the table that begin with
-D) are used by the embedded Java Virtual Machine that is started by Jsvc. The following is an example of how such parameters are used:
-Djava.library.path=/opt/jboss-ews-2.0/tomcat6
Similarly, the classpath can be added using
-cp. The following example illustrates a sample classpath option that starts org.apache.catalina.startup.Bootstrap:
-cp $JAVA_HOME/lib/tools.jar:$CATALINA_HOME/bin/commons-daemon.jar:$CATALINA_HOME/bin/bootstrap.jar