Using Tomcat Toolkit in a HP Serviceguard Cluster README Revision: B.06.00

If you do not set CATALINA_BASE to an explicit value, it will be
initialized to the same value as is set for CATALINA_HOME (which means
that the same directory is used for all relative path resolutions).
NOTE: In an HP-UX 11.x environment, the Tomcat server is usually
installed in the location /opt/hpws22/tomcat and the
default
configuration file "server.xml" resides in the "conf"
sub-directory under this directory. if HP-UX WSS 2.X is
installed,
then the Tomcat server will be installed in the location
/opt/hpws/tomcat.
A. Tomcat Package Configuration Overview
Tomcat starts up by reading the "server.xml" file from the "conf"
sub-directory of the CATALINA_BASE directory which is configured in
the toolkit user configuration file hatomcat.conf.
Configuration rules include the following:
* Each node must have the same version of the HP-UX based Tomcat
Servlet Engine.
* Each node must have the same CATALINA_BASE directory where
identical copies of the configuration file for each instance are
placed.
* Each node must have the same document root directory where
identical copies of the web document for each instance are placed.
Tomcat servlet engine can be configured in two different ways:
* (local config) by putting the configuration and other web-site
files on a single node, then replicating the files to all other
nodes in the cluster
* (shared config) with configuration files and document root files in
a shared file system
Note: Under a shared configuration, you can choose to put tomcat
binaries as well in a shared file system. The steps to configure this
is covered in this document later.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Local Configuration
In a typical local configuration, nothing is shared between the
nodes. Identical copies of the Tomcat server configuration file and
web documents reside in exactly the same locations on each node.
The user is responsible for maintaining identical copies of the
tomcat components on the different nodes. This is useful when the
information on the web-page is static.