HP Serviceguard Contributed Toolkit Suite Version A.04.02.02 on Linux User Guide (December, 2012)

node in the cluster. However, you must ensure that the mount point of the shared file system is
identical across all Apache toolkit package nodes.
NOTE: HP recommends that you use the shared configuration option for configuring this toolkit
because you do not have to maintain identical copies of the files and directories on all the nodes.
The information is automatically accessible to all the nodes.
Each website is assigned with an IP address (or domain address that maps to a particular IP
address) through the configuration file. These relocatable IP addresses are created for each Apache
toolkit package and added to its package control script. When the Apache toolkit package is
switched over from one node to another, this particular instance is stopped and IP addresses are
removed on the primary node. Then, the IP addresses are reallocated and the instance is started
on the adoptive node. Clients are automatically connected through these IP addresses to the website
on the adoptive node.
Multiple instance configuration
Apache web server is a multi-instance application, which means more than one instance of the
Apache web server runs on a single node at the same time. For example, if two nodes each are
running one Apache instance, and one node fails, the Apache instance on the failed node can
successfully fail over to the other node. In addition, the healthy node continues to run its own
instance. Multiple Apache instance configuration can be a local or shared configuration, or a
combination of both.
Using SG Apache toolkit
After installing the SG Apache toolkit, you can use the toolkit to:
• Configure Apache toolkit packages in an SG/LX environment
• Manage Apache toolkit packages
Configuring Apache toolkit packages
You can configure Apache toolkit packages using either legacy or modular style of packaging.
Configuring legacy Apache toolkit packages
The subsequent sections explain how to configure Apache web server as a single instance package
and as a multiple instance package using the Apache toolkit, using the legacy style of packaging.
Configuring a single instance
For easy comprehension, the following naming conventions are used in this section:
• A Serviceguard Apache toolkit package is referred as APACHE1.
• The corresponding service name is referred as apache1_service.
• The Apache instance listens to a relocatable IP address.
• The node names used are node1 and node2.
You can configure a volume using either local or shared configuration. Using the local configuration,
you configure volumes on the local file system. The server root directory and the document root
directory are maintained in the local file system. However, using the shared configuration, the
server root directory and the document root directory are maintained on a volume group that is
shared among the nodes of the cluster.
Following is a sample procedure that indicates the steps that you must complete to configure an
Apache instance that uses shared storage for all Apache instance data. You must configure all
Apache instance files on a shared file system /mnt/vgtry1/apache directory, which resides
on a logical volume lvol from a shared volume group /dev/vgtry1.
Using SG Apache toolkit 11