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

Example 3 For example:
VG[0]="vg01"
LV[0]="/dev/vg01/lvol1"
FS[0]="/share/pkg_1"
FS_MOUNT_OPT[0]="-o rw"
FS_UMOUNT_OPT[0]=""
FS_FSCK_OPT[0]=""
FS_TYPE[0]="vxfs"
Configure the two services one for Tomcat and Apache instances
respectively
SERVICE_NAME[0]="tomcat_pkg1.monitor"
SERVICE_CMD[0]="/etc/cmcluster/pkg/tomcat_pkg1/toolkit.sh monitor"
SERVICE_RESTART[0]=""
SERVICE_NAME[1]="http_pkg1.monitor"
SERVICE_CMD[1]="/etc/cmcluster/pkg/http_pkg1/toolkit.sh monitor"
SERVICE_RESTART[1]=""
Edit the customer_defined_run and customer_defined_halt function
as shown below:-
function customer_defined_run_cmds
{
# ADD customer defined run commands.
/etc/cmcluster/pkg/tomcat_pkg1/toolkit.sh start
/etc/cmcluster/pkg/http_pkg1/toolkit.sh start
test_return 51
}
function customer_defined_halt_cmds
{
# ADD customer defined run commands.
/etc/cmcluster/pkg/tomcat_pkg1/toolkit.sh stop
/etc/cmcluster/pkg/http_pkg1/toolkit.sh stop
test_return 51
}
For more information, see the latest Managing Serviceguard manual available at http://
www.hp.com/go/hpux-serviceguard-docs —>HP Serviceguard and “Using an Apache Toolkit in
a HP Serviceguard Cluster” (page 98).
NOTE: When you bring down Apache or Tomcat application for maintenance, you must touch
the files tomcat.debug and apache.debug in Tomcat and Apache package directories /etc/
cmcluster/pkg/tomcat_pkg1/ and /etc/cmcluster/pkg/http_pkg1/ respectively.
This ensures that monitoring services for both Apache and Tomcat is paused during the maintenance
period.
Both Tomcat and Apache applications, are configured in a single package. To troubleshoot and
debug, you must check the Serviceguard package logs in the directory where the package control
file resides. For application related logs, check the error and logs directory in $SERVER_ROOT
and $CATALINA_BASE for Apache and Tomcat applications respectively.
122 Using Tomcat Toolkit in a HP Serviceguard Cluster