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

Table 25 Configuration Variables (continued)
DescriptionConfiguration Variables
that the Apache instance is running properly after the maintenance
phase.
NOTE: If youMAINTENANCE_FLAG to "yes" and touch the
apache.debug file in the package directory, the package is placed
in the toolkit maintenance mode. Serviceguard A.11.19 release has a
new feature which enables individual components of the package to be
maintained while the package is still up. This feature is called Package
Maintenance mode and is available only for modular packages. For
more information using Package Maintenance mode, see theModular
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
This is the tomcat server listening port. This port and the port configured
in the Tomcat configuration file $CATALINA_BASE/conf/
MONITOR_INTERVAL (for example,
MONITOR_INTERVAL=5)
server.xmlmust be same. The toolkit periodically checks whether this
port is listening, to verify the existence of the Tomcat process. If multiple
instances of tomcat are configured, this port must be unique for each
instance. The default value is 8081.
This variable holds a time interval (in seconds) for monitoring the Apache
instance. That is, the monitor process checks the running of httpd
MONITOR_INTERVAL (for example,
MONITOR_INTERVAL=5)
daemons every 'interval' seconds. If not defined, its default value is 5
seconds.
This variable holds the number of times to attempt to check the 'httpd'
daemon processes before giving up and exiting to fail state. If not
defined, its default value is 2.
RETRY_TIMES (for example,
RETRY_TIMES=2)
For the alert mail notification feature, an additional parameter called ALERT_MAIL_ID is introduced
in the ADF. ALERT_MAIL ID sends an email message to the specified email address when
packages fail. This email is generated only when packages fail, and not when a package is halted
by the operator. To send this email message to multiple recipients, a group emaill ID must be
created and specified for this parameter. When email ID is not specified for this parameter, the
script does not send out this email.
The following information provides the steps for configuring the toolkit and running the package.
This includes configuring the Apache toolkit user configuration file.
NOTE: Before working on the toolkit configuration, the package directory (for example, /etc/
cmcluster/pkg/http_pkg1) must be created and all toolkit scripts copied to the package
directory.
To configure the toolkit and run the package:
1. Edit the Apache Toolkit user configuration file.
In the package directory, edit the user configuration file ( hahttp.conf) as indicated by the
comments in that file.
For example:
SERVER_ROOT="/shared/apache1/httpd"
PID_FILE="/var/run/httpd1.pid"
SSL="yes"
MAINTENANCE_FLAG="yes"
2. Copy the entire package directory at the same path on all nodes configured for the package.
For this example, each package node must have the following files in the package directory:
http_pkg.conf #Package configuration file
Setting up the Toolkit 107