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

configuration file, hatomcat.conf. If this file is changed, please
remember to distribute the new file to all cluster nodes).
- Start the tomcat instance again if you stopped it
cd /etc/cmcluster/pkg/tomcat_pkg1/ $PWD/toolkit.sh start
- Allow monitoring scripts to continue normally as shown below:
rm -f /etc/cmcluster/pkg/tomcat_pkg1/tomcat.debug
A message "Starting Tomcat toolkit monitoring again after
maintenance" appears in the Serviceguard Package Control script log.
- Enable the package failover
cmmodpkg -e tomcat_pkg1
Note: If the package fails during maintenance (example, the node
crashes), the package will not automatically fail over to an
adoptive node. It is the responsibility of the user to start
the package up on an adoptive node. Please refer to the
manual "Managing Serviceguard" for more details
Note: This feature is enabled only when the configuration variable
MAINTENANCE_FLAG is set to "yes" in the tomcat toolkit
configuration file
/etc/cmcluster/pkg/tomcat_pkg1/hatomcat.conf
G. Configuring Apache web server with Tomcat in a single package
NOTE: This section contains details on configuring Apache web server
with Tomcat in a single package only for the legacy method of
packaging. For configuring Apache and Tomcat in a single package
using the modular method of packaging, please refer to the whitepaper
"Modular package suport in Serviceguard for Linux and ECM Toolkits"
located at http://docs.hp.com/en/ha.html
Tomcat can be setup in a stand alone configuration that allows web
browsers to be connected directly to the tomcat servlet or through
web server such as Apache. To integrate Tomcat with Apache, the JK
Connector is used. The mod_jk component needs to be configured in
Apache in order to make Apache work with Tomcat. When the user
chooses this type of configuration and it needs to be deployed in a
highly available Serviceguard environment then both the Apache and
Tomcat toolkit need to be configured in a single package. The
example below gives the steps for configuring such a package:- This
example assumes that both Apache and Tomcat server are configured on
a single Volume group vg01 (in case of LVM) and a single mount point
/share/pkg_1.