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

function customer_defined_run_cmds
{
# Start the Tomcat Web Server.
/etc/cmcluster/pkg/tomcat_pkg1/toolkit.sh start
test_return 51
}
Edit the customer_defined_halt_cmds function to execute the
toolkit.sh script with the stop option. In the example below, the
line "/etc/cmcluster/pkg/tomcat_pkg1/toolkit.sh stop" was added,
and the ":" null command line deleted.
EXAMPLE:
function customer_defined_halt_cmds
{
# Stop the Tomcat Web Server.
/etc/cmcluster/pkg/tomcat_pkg1/toolkit.sh stop
test_return 51
}
3. Configure the Tomcat user configuration file "hatomcat.conf" as
explained in the next section
4. Copy this package configuration directory to all other package
nodes
You can use the same procedure to create multiple Tomcat packages
(multiple Tomcat instances) that will be running on the cluster.
D. Setting up The Toolkit
D.1 Toolkit Overview
After installing the toolkit, four scripts and one README file will be
installed in the location /opt/cmcluster/toolkit/tomcat. Two more
scripts and one file will be installed which will be used only for
modular packages. The two scripts will be in the
/etc/cmcluster/scripts/ecmt/tomcat directory. The third file will be in
the /etc/cmcluster/modules/ecmt/tomcat directory.
For legacy packages, one user configuration script (hatomcat.conf)
and
three functional scripts (toolkit.sh, hatomcat.sh and hatomcat.mon)
will
work together to integrate the Tomcat server with the Serviceguard
package