HP Enterprise Cluster Master Toolkit User Guide (5900-2131, December 2011)

NOTE: As mentioned before, under shared configuration, you can choose to put the Tomcat
binaries as well in a shared file system. This can be configured by 2 methods:
To create a shared configuration for the Tomcat Server on the shared file system mounted at
/mnt/tomcat:
a. Method 1
1) Create the shared storage that will be used to store the Tomcat files for all nodes
configured to run the Tomcat package. Once that storage has been configured,
create the mount point for that shared storage on these nodes. For this example, the
mount point is "/mnt/tomcat".
2) Copy all files from /opt/hpws22/tomcat to /mnt/tomcat on any one node.
3) Remove or rename /opt/hpws22/tomcat on all nodes configured to run the
Tomcat package.
4) Create a symbolic link between /opt/hpws22/tomcat and /mnt/tomcat on all
nodes configured to run the package.
b. Method 2
1) Create the shared storage that will be used to store the Tomcat files for all nodes
configured to run the Tomcat package. Once that storage has been configured,
create the mount point for that shared storage on these nodes. For this example, the
mount point is "/mnt/tomcat".
2) On any one node in the cluster that is configured to run the package, activate the
shared storage and mount it at the mount point "/mnt/tomcat". Copy the Tomcat
files to the shared storage using the altroot.sh utility: $ /opt/hpws22/util/
altroot.sh --tomcat /mnt/tomcat
Besides moving the files in the /opt/hpws22/tomcat directory to the new directory
/mnt/tomcat, one additional Tomcat file will need to be copied to all the other nodes
in the cluster that are configured to run the package. Step 3 explains which file needs
to be moved.
3) On the same node as above, copy the following file to the other nodes in the cluster
that are configured to run the package:/etc/rc.config.d/hpws22_tomcatconf
.
4) On the other nodes in the cluster remove or rename the /opt/hpws22/tomcat
directory if desired.
5) Now configure the hatomcat.conf file as required for the Tomcat Server package
on all nodes in case of legacy packages and the Tomcat toolkit parameters in the
package ASCII file in case of modular packages.
NOTE: The following sections describe the method for creating the Serviceguard package
using the legacy method. For information on creating the Serviceguard package using the
modular method, see the white paper 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.
Setting Up The Package
The following procedures here show how to configure a Serviceguard package running the Tomcat
instance, which includes customizing the Serviceguard package configuration file and package
control script. See Managing ServiceGuard manual available at http://www.hp.com/go/
hpux-serviceguard-docs —>HP Serviceguard for more detailed instructions on cluster configuration.
The procedures below assume that the user is configuring a Serviceguard Tomcat package named
"tomcat_pkg1", consisting of one service named "tomcat1_monitor". The Tomcat instance is listening
to a relocatable IP address "192.168.0.201" and all of its configuration and document files are
Setting Up The Package 115