HP Serviceguard Enterprise Cluster Master Toolkit User Guide, December 2012 (5900-2145)

Table 24 (page 98) lists the files that are installed for the modular method of packaging. apache.1
is an Attribute Definition File (ADF) that is installed in /etc/cmcluster/modules/ecmt/apache.
Table 24 Files in Modular Method Packaging
DescriptionFile Name
This script is called by the Master Control Script and acts as an interface
between the Master Control Script and the Toolkit interface script (toolkit.sh).
tkit_module.sh
It is responsible for calling the Toolkit Configuration File Generator Script
(described below).
The tkit_gen.sh file is located in /etc/cmcluster/scripts/ecmt/
apache after installation.
tkit_gen.sh
This script is called by the Module Script when the package configuration is
applied using 'cmapplyconf' to generate the toolkit user configuration file in
the package directory (TKIT_DIR).
The apache.1 file is located in /etc/cmcluster/scripts/ecmt/apache
after installation.
apache.1
For every parameter in the legacy toolkit user configuration file, there is an
attribute in the ADF. It also has an additional attribute TKIT_DIR which is
analogous to the package directory in the legacy method of packaging. The
ADF is used to generate a modular package ASCII template file.
The HP-UX Web Server suite, which includes the Apache application, must be installed on all nodes
that are configured to run the package. A typical clustered configuration for an Apache Web
Server application is to configure one node as a primary node and the other nodes as standby
nodes. The application runs on the primary node, and accepts HTTP/HTTPS requests, and sends
responses to the clients. If the primary node fails, a standby node will takes over the application.
This means that all necessary configuration information on each node must be identical and the
resources must be available to all supporting nodes. The dynamic web pages and shared data
must be stored on shared disks and these disks must be accessible to each node.
Apache Web Server supports multiple instances of the server daemons running on a node
simultaneously. Each Apache package corresponds to a separate Apache server instance with its
own SERVER_ROOT directory. SERVER_ROOT is a user configurable variable, present in the toolkit
user configuration file hahttp.conf. Each instance supports one or more web sites, depending
on whether it has been configured to use "virtual hosts" or not.
After Apache is installed, the SERVER_ROOT directory defines an Apache server instance. This
directory contains the appropriate configuration file directory named "conf" that specifies how an
Apache server instance is configured. The Apache configuration directives within this file determines
the locations of log files, web documents, and domain name address for a specific Apache server
instance.
NOTE: In an HP-UX 11.x environment, the Apache server is usually installed in the location
/opt/hpws22/apache and the configuration file httpd.conf resides in the "conf" sub-directory
under the "SERVER ROOT" directory.
Apache Package Configuration Overview
Apache starts up by reading the httpd.conf file from the "conf" sub-directory of the
SERVER_ROOT directory which is configured in the toolkit user configuration file hahttp.conf.
Configuration rules include the following:
• Each node must have the same version of the HP-UX based Apache Web Server.
• Each node must have the same SERVER_ROOT directory where identical copies of the
configuration file for each instance are placed.
• Each node must have the same document root directory where identical copies of the web
document for each instance are placed.
98 Using an Apache Toolkit in a HP Serviceguard Cluster