HP Serviceguard Enterprise Cluster Master Toolkit User Guide, December 2012 (5900-2145)

Table 30 Legal Package Scripts
DescriptionScript Name
This script contains a list of pre-defined variables that can be customized for
the user's environment. This script provides the user a simple format of the
User Configuration file (hatomcat.conf)
user configuration data. This file is sourced by the toolkit main script
hatomcat.sh.
This script contains a list of internal-use variables and functions that support
the start and stop functions of a Tomcat instance. This script is called by the
Toolkit Interface Script to do the following:
Main Script (hatomcat.sh)
• On package start; it starts the Tomcat server instance.
• On package stop; it stops the Tomcat server instance.
This script contains a list of internal variables and functions that supports
monitoring of a Tomcat instance. Monitoring functionality is initiated by calling
the toolkit interface script with the "monitor" parameter.
Monitor Script (hatomcat.mon)
This script is an interface between the Serviceguard package control script
and the toolkit main script (hatomcat.sh).
Interface Script (toolkit.sh)
Toolkit user configuration
All the user configuration variables are kept in a single file hatomcat.conf in shell script format.
The variable names and their sample values are given below in Table 31 (page 117):
Table 31 User Configuration Variables
DescriptionUser Configuration Variables
This is the base directory where HP Tomcat web server is installed. By default,
HP Tomcat is installed in the directory /opt/hpws22/tomcat and hence this
is also the default value.
CATALINA_HOME (for example,
CATALINA_HOME="/opt/hpws22/tomcat")
This variable holds the specific configuration file path of a Tomcat server
instance. Each Tomcat instance must have its own configuration directory that
CATALINA_BASE (for example,
CATALINA_BASE="/opt/hpws22/tomcat")
contains its own server configuration file (server.xml). The Tomcat server
default server root directory is "/opt/hpws22/tomcat". However, to run
multiple instances in a cluster, set a value for this variable.
This is the base directory of the Java Development kit. This software is a
prerequisite for running Tomcat.
JAVA_HOME (for example,
JAVA_HOME=/opt/java1.5)
This variable will enable or disable maintenance mode for the Tomcat package.
By default, this is set to "yes". To disable this feature, setMAINTENANCE_FLAG
MAINTENANCE_FLAG (for example,
MAINTENANCE_FLAG ="yes")
to "no". When Tomcat needs to be maintained the file, <package
directory>/tomcat.debug must be created. During this maintenance
period, the tomcat process monitoring is paused. Even if the tomcat instance
is brought down, the package is failed over to the adoptive node. To continue
monitoring and turn off maintenance mode, remove the tomcat.debug file.
You must ensure that the tomcat instance is running properly after the
maintenance phase.
NOTE: If you set theMAINTENANCE_FLAG to "yes" and touch the
tomcat.debug file in the package directory, the package in toolkit will move
to maintenance mode. In Serviceguard A.11.19 release, a new feature enables
you to individual components of the package while the package is still up.
This feature is called Package Maintenance mode and is available only for
modular packages. For more information using Package Maintenance mode,
see Modular package support in Serviceguard for Linux and ECM Toolkits
available at http://www.hp.com/go/hpux-serviceguard-docs —>HP
Serviceguard Enterprise Cluster Master Toolkit.
This is the tomcat server listening port. This should be as same as the port
configured in the Tomcat configuration file $CATALINA_BASE/conf/
MONITOR_PORT (for example:
MONITOR_PORT=8081)
server.xml. The toolkit checks the existence of the Tomcat process by
Setting up the Toolkit 117