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

node startup and shutdown, create a one-node package for each node that runs an Apache
instance.
Active - Passive
In an active-passive configuration, an instance of Apache Web Server can run on only one node
at any time. A package of this configuration is a typical failover package. The active - passive
support on CFS comes with a caution or limitation that, when an Apache instance is up on one
node, no attempts should be made to start the same instance of Apache on any another node.
NOTE: In both active-active and active-passive Apache configurations the Apache installation
on all nodes reside on the single shared CFS mount point. For complete details on how to setup
Apache Web server on CFS, please refer the Apache whitepaper on CFS or CVM support
referenced from the ECMT Release Notes of this version.
Under shared configuration, choose to put Apache binaries as well in shared file system. This can
be configured by 2 methods:
To create a shared configuration for the Apache Web Server on the shared file system mounted
at /mnt/apache:
Method #1
1. Create the shared storage that will be used to store the apache files for all nodes configured
to run the Apache 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/apache.
2. Copy all files from /opt/hpws22/apache to /mnt/apache on any one node.
3. Remove or rename /opt/hpws22/apache on all nodes configured to run the apache
package.
4. Create a symbolic link between /opt/hpws22/apache and /mnt/apache on all nodes
configured to run the package.
Method #2
1. Create the shared storage that will be used to store the apache files for all nodes configured
to run the Apache 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/apache.
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/apache. Copy the Apache files to the shared
storage using the altroot.sh utility:$ /opt/hpws22/util/altroot.sh --apache /mnt/apache
Besides moving the files in the /opt/hpws22/apache directory to the new directory
/mnt/apache, one additional apache file will need to be copied to all the other nodes in the
cluster that are configured to run the package. The next step 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_apacheconf.
4. On the other nodes in the cluster remove or rename the /opt/hpws22/apache directory if
desired.
5. Now configure the hahttp.conf file as required for the Apache Server package on all
nodes in case of legacy packages and the Apache 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
102 Using an Apache Toolkit in a HP Serviceguard Cluster