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

If the user chooses to use this configuration, it is the user's
responsibility to ensure the data is propagated to all nodes, and is
consistently maintained. A disadvantage of storing the
configuration on local disks is that this can increase the chance of
the configuration for a Tomcat instance becoming inconsistent if
changes are made, but not distributed to all nodes that can run that
Tomcat instance.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Shared Configuration
In a typical shared configuration, the web application directories
are all on the shared file system. (Placing the CATALINA_BASE
directory in the shared file system is optional.) Since the web
applications (along with the tomcat configuration directory) are on
shared storage - accessible to all nodes in the cluster - there is
no need to maintain local identical copies of the files on each
node. The mount point of the shared file system should be identical
across all the tomcat package nodes. Hence this is the recommended
Tomcat package configuration.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Each web site is assigned IP addresses (or domain addresses that
maps to particular IP addresses) through the configuration file.
These relocatable IP addresses are created for each Tomcat package
and added to its Package Control Script in case of legacy packages
or the Package ASCII file in case of modular packages. When the
Tomcat
package is switched over from one node to another, this particular
instance is stopped and IP addresses are removed on the primary node,
then the IP addresses are reallocated and the instance is started on
the adoptive node. Clients will then be automatically connected
through these IP addresses to the web site on the adoptive node.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Multiple Tomcat Instances Configuration
Tomcat servlet engine is a multi-instance application, which means
more than one instance of the Tomcat can run on a single node
simultaneously. For example, if two nodes are each running an
instance of Tomcat and one node fails,the Tomcat instance on the
failed node can be successfully failed over to the healthy node. In
addition, the healthy node can continue to run its own instance as
well. Multiple Tomcat instance configuration can either be done as a
local configuration or shared configuration or a combination of both.
CATALINA_BASE needs to be unique for each Tomcat instance.
B. Configuring the Tomcat server with Serviceguard