HP Serviceguard Enterprise Cluster Master Toolkit User Guide (5900-2145, April 2013)
Table Of Contents
- HP Serviceguard Enterprise Cluster Master Toolkit User Guide
- Contents
- 1 Introduction
- 2 Using the Oracle Toolkit in an HP Serviceguard Cluster
- Overview
- Supported Versions
- Support for Oracle Database Without ASM
- Supporting Oracle ASM Instance and Oracle Database with ASM
- What is Automatic Storage Management (ASM)?
- Why ASM over LVM?
- Configuring LVM Volume Groups for ASM Disk Groups
- Sample command sequence for configuring LVM Volume Groups
- Serviceguard support for ASM on HP-UX 11i v3 onwards
- Framework for ASM support with Serviceguard
- Installing, Configuring, and Troubleshooting
- Setting up DB instance and ASM instance
- Setting up the Toolkit
- ASM Package Configuration Example
- Modifying a Legacy Database Package Using an Older Version of Oracle ECMT Scripts to use the Scripts Provided for ASM Support
- Adding the Package to the Cluster
- Node-specific Configuration
- Error Handling
- Network Configuration
- Database Maintenance
- Configuring and packaging Oracle single-instance database to co-exist with SGeRAC packages
- Configuring Oracle single-instance database that uses ASM in a Coexistence Environment
- Attributes newly added to ECMT Oracle toolkit
- Configuring a modular failover package for an Oracle database using ASM in a coexistence environment
- Configuring a legacy failover package for an Oracle database using ASM in a Coexistence Environment
- ECMT Oracle Toolkit Maintenance Mode
- Supporting EBS database Tier
- Oracle ASM Support for EBS DB Tier
- 3 Using the Sybase ASE Toolkit in a Serviceguard Cluster on HP-UX
- Overview
- Sybase Information
- Setting up the Application
- Setting up the Toolkit
- Sybase Package Configuration Example
- Creating the Serviceguard package using Modular method
- Adding the Package to the Cluster
- Node-specific Configuration
- Error-Handling
- Network configuration
- Database Maintenance
- Cluster Verification for Sybase ASE Toolkit
- 4 Using the DB2 Database Toolkit in a Serviceguard Cluster in HP-UX
- 5 Using MySQL Toolkit in a HP Serviceguard Cluster
- MySQL Package Configuration Overview
- Setting Up the Database Server Application
- Setting up MySQL with the Toolkit
- Package Configuration File and Control Script
- Creating Serviceguard Package Using Modular Method
- Applying the Configuration and Running the Package
- Database Maintenance
- Guidelines to Start Using MySQL Toolkit
- 6 Using an Apache Toolkit in a HP Serviceguard Cluster
- 7 Using Tomcat Toolkit in a HP Serviceguard Cluster
- Tomcat Package Configuration Overview
- Multiple Tomcat Instances Configuration
- Configuring the Tomcat Server with Serviceguard
- Setting up the Package
- Creating Serviceguard Package Using Modular Method
- Setting up the Toolkit
- Error Handling
- Tomcat Server Maintenance
- Configuring Apache Web Server with Tomcat in a Single Package
- 8 Using SAMBA Toolkit in a Serviceguard Cluster
- 9 Using HP Serviceguard Toolkit for EnterpriseDB PPAS in an HP Serviceguard Cluster
- 10 Support and Other resources
- 11 Acronyms and Abbreviations
- Index

/etc/cmcluster/scripts/ecmt/apache directory. The third file is located in the /etc/
cmcluster/modules/ecmt/apache directory.
For legacy packages, one user configuration script (hahttp.conf) and three functional scripts
(toolkit.sh, hahttp.sh, and hahttp.mon) works together to integrate Apache web server with the
Serviceguard package control script.
Table 24 (page 106) lists the scripts used in legacy packages are:
Table 24 Scripts in Legacy Packages
DescriptionScript Name
This script contains a list of pre-defined variables that can be customized
for the user's environment. This script provides the user a simple format of
User Configuration file (hahttp.conf)
the user configuration data. This file is included (that is, sourced) by the
toolkit main script hahttp.sh.
This script contains a list of internal-use variables and functions that support
the start and stop of an Apache instance. This script is called by the Toolkit
Interface Script and performs the following functions.
Main Script (hahttp.sh)
• On package start, it starts the Apache server instance.
• On package stop, it stops the Apache server instance.
Monitoring functionality is initiated by calling the toolkit with the "monitor"
parameter as "toolkit.sh monitor".
Monitor Script (hahttp.mon)
This script is an interface between the Serviceguard package control script
and the toolkit main script (hahttp.sh).
Interface Script (toolkit.sh)
Toolkit user configuration
All the user configuration variables are kept in a single file hahttp.conf in shell script format.
The variable names and their sample values are listed in Table 25 (page 106):
Table 25 Configuration Variables
DescriptionConfiguration Variables
This is the base directory where HP Apache web server is installed. By
default, HP Apache is installed in the directory /opt/hpws22/apache
and hence this is also the default value.
HP_APACHE_HOME (for example,
HP_APACHE_HOME="/opt/hpws22/
apache")
This variable holds the root directory of an Apache server instance. Each
Apache instance must have its own root directory that contains its own
SERVER_ROOT (for example,
SERVER_ROOT="/opt/hpws22/apache")
server configuration file (httpd.conf). The Apache's system default
server root directory is /opt/hpws22/apache. However, to run
multiple instances in a cluster, set a value for this variable.
This variable holds the Process ID file path of the Apache server instance.
Each Apache instance must have its own PID file that maintains the main
PID_FILE (for example, PID_FILE="/
var/run/httpd_s1.pid")
process ID of the running Apache server instance. If this variable is not
set, the PID file is <package_directory>/httpd.pid.
When this variable is set to "yes" the Apache web server runs in secured
mode where the Apache web server can listen to HTTPS requests
SSL (for example: SSL="no")
otherwise. When set to "no" Apache web server is started in non secure
mode and Apache can only listen to HTTP requests.
This variable enables or disables maintenance mode for the Apache
package. By default, this is set to "yes”. To disable this feature
MAINTENANCE_FLAG (for example,
MAINTENANCE_FLAG ="yes")
MAINTENANCE_FLAG must be set to "no". When Apache must be
maintained the file "<package directory apache.debug" needs to be
created. During this maintenance period apache process monitoring is
paused. Even if the apache instance is brought down the package is
failed over to the adoptive node. To continue monitoring and turn off
maintenance mode, remove the apache.debug file. You must ensure
106 Using an Apache Toolkit in a HP Serviceguard Cluster