HP Serviceguard Linux Contributed Toolkit Suite A.04.02.01 User Guide (696979-001, June 2012)

3. Create a separate, distinct CATALINA_BASE directory for each Tomcat Serviceguard package.
4. Configure all Tomcat instances to listen to package re-locatable IP addresses.
For information on configuring virtual hosts, see Tomcat Server documentation.
NOTE: For a local configuration, you must install and configure Tomcat in the same location
on the primary and all backup nodes and set up the identical (or equivalent) configuration
files in the same server root directory on all nodes. Also, all web application directories must
exist on all nodes and should contain identical files.
For a shared configuration, you need to configure the web application directories on shared
file system. One or more shared file systems may be used. Ensure that all required components
which are on shared storage are available at the same time. It is not required to place the
CATALINA_BASE directory on a shared file system to use the shared storage.
You may choose a local CATALINA_BASE directory for configuration files and place only the
web application directories on a shared file system. However, you must configure identical
CATALINA_BASE directories and identical configuration files on all nodes.
Supported Configuration
This section explains the following supported configurations for Tomcat toolkit packages:
Local configuration
Tomcat data and configuration files are present on the local disk on all the nodes is enabled for
the Tomcat toolkit package. The data and configuration files must be identical across all the nodes
configured for the Tomcat toolkit package in the cluster and it must be available on the same
location. If you make any change to the database, you must replicate the same change to all the
nodes.
Shared configuration
In a shared configuration, the configuration and data files are placed all on the shared storage.
The same Tomcat data and configuration file are shared between the cluster nodes, so you need
not maintain identical copies on each node. In a cluster environment, each Tomcat database server
instance must have unique IP addresses. When the package is created, one or more relocatable
IP addresses are created for each Tomcat database server. When the Tomcat database server
package switches over from one node to another, this instance is stopped, IP addresses are removed
from the primary node, IP addresses are reallocated to a standby node, and the instance is started
on that node. Clients are automatically connected or manually reconnected through these IP
addresses to the identical Tomcat database server on the standby node.
Multiple Tomcat Instances Configuration
Tomcat servlet engine is a multi-instance application, so, more than one instance of the Tomcat
can run on a single node at the same time. For example, if two nodes each are running an instance
of Tomcat and one of the nodes fail, then Tomcat instance on the failed node is failed over to the
other node. In addition, the healthy node continues to run its own instance as well. You can
configure multiple Tomcat instances either as a local configuration or shared configuration, or a
combination of both.
Using Tomcat toolkit
After installing the Tomcat toolkit, you can use this toolkit to:
• Configure packages in an SG/LX environment
• Manage packages
54 Tomcat Toolkit