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
4. On the other nodes in the cluster remove or rename the /opt/hpws22/tomcat directory.
5. Configure the hatomcat.conf file as required for the Tomcat Server package on all nodes
in case of legacy packages and the Tomcat toolkit parameters in the package ASCII file in
case of modular packages.
NOTE: The following sections describe the method for creating the Serviceguard package using
the legacy method. For information on creating the Serviceguard package using the modular
method, see the white paper Modular 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.
Setting up the Package
The following procedure describes the method to configure a Serviceguard package running the
Tomcat instance, which includes customizing the Serviceguard package configuration file and
package control script. For more information on cluster configuration, see the latest Managing
Serviceguard manual available at http://www.hp.com/go/hpux-serviceguard-docs —>HP
Serviceguard .
In the following procedure, consider that the name of the Serviceguard Tomcat package is
"tomcat_pkg1", which consists of one service named "tomcat1_monitor". The Tomcat instance is
listening to a relocatable IP address "192.168.0.201" and all its configuration and document
files are on a file system "/shared/tomcat_1" directory. This file system resides on a logical volume
"lvol1" in a shared volume group "/dev/vg01". Consider that you have already determined the
Serviceguard cluster configuration, including cluster name, node names, heartbeat IP addresses,
and so on. For more information, see the latest Managing Serviceguard manual available at http://
www.hp.com/go/hpux-serviceguard-docs —>HP Serviceguard .
NOTE: To increase the number of packages that can be added to this cluster, modify the cluster
configuration file and set the variable MAX_CONFIGURED_PACKAGES to reflect the number of
packages to be added to the cluster. After the edit, apply the change to the cluster via
cmapplyconf -C cluster_config_file.
Before you configure the package, create a directory (for example, /etc/cmcluster/pkg/
tomcat_pkg1) to run this package. This directory must belong to a single Tomcat package. Copy
all Tomcat toolkit scripts from the directory /opt/cmcluster/toolkit/tomcat to the package
directory.
To create both the package configuration (tomcat_pkg.conf) and package control
(tomcat_pkg.cntl) files, cd to the package directory (example, cd
/etc/cmcluster/pkg/tomcat_pkg1).
For Example:
$ mkdir /etc/cmcluster/pkg/tomcat_pkg1
$ cd /etc/cmcluster/pkg/tomcat_pkg1
$ cp /opt/cmcluster/toolkit/tomcat/*.
To configure a Serviceguard package running the Tomcat instance:
1. Create a Serviceguard package configuration file with the command cmmakepkg -p
tomcat_pkg1.confaccording to the instructions provided. Edit the package configuration
file tomcat_pkg1.conf as indicated by the comments in that file. The package name must
be unique within the cluster.
For Example:
PACKAGE_NAME tomcat_pkg1
NODE_NAME node1
NODE_NAME node2
Setting up the Package 115