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 30 User Configuration Variables (continued)
DescriptionUser Configuration Variables
periodically checking whether this port is listening. If multiple instances of
tomcat are configured, this port needs be unique for each instance. The default
value is 8081.
Specify a time interval in seconds for monitoring the Tomcat instance. The
monitor process checks the Tomcat daemons at this interval to validate they
are running. The default value is 5 seconds.
MONITOR_INTERVAL (for example,
MONITOR_INTERVAL=5)
This variable holds the number attempts to check the 'tomcat' daemon
processes before it exits to fail state. The 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. It 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, create a group email ID and specify for this
parameter. If the email ID is not specified for this parameter, the script does not send out this email.
NOTE: Before you configure the toolkit, create the package directory (for example,
/etc/cmcluster/pkg/tomcat_pkg1), and then copy all toolkit scripts to the package directory.
To configure the Tomcat toolkit that includes user configuration file and run the package, follow
the below steps:
1. Edit the Tomcat Toolkit user configuration file.
In the package directory, edit the user configuration file (hatomcat.conf ) as indicated by
the comments in that file.
For Example:
CATALINA_HOME="/opt/hpws22/tomcat"
CATALINA_BASE="/shared/tomcat_1"
MAINTENANCE_FLAG="yes"
MONITOR_PORT=8081
2. Distribute all package files in the package directory to the other package nodes. All nodes
must have an identical file path for these files. For this example, each package node must
have the following files in the package directory:
For Example:
tomcat_pkg.conf #Package configuration file
tomcat_pkg.cntl #Package control file
hatomcat.conf #Tomcat toolkit user configuration file
hatomcat.mon #Tomcat toolkit monitor program
hatomcat.sh #Tomcat toolkit main script
toolkit.sh #Interface file between the package
#control file and the toolkit
3. Apply the Serviceguard package configuration using the command cmapplyconf -P
tomcat_pkg.conf.
Use the same procedure, to create multiple Tomcat instances for Serviceguard packages that will
run on the cluster.
Error Handling
On startup, the Tomcat server application checks the existence of the server.xml file in the
directory <CATALINA_BASE/conf>. If the configuration file does not exist at this location or if the
Tomcat does not start for some other reason, he Tomcat toolkit script halts he package on that node
Error Handling 119