Managing Serviceguard Extension for SAP on Integrity Linux, December 2005

Step by Step Installation of SGeSAP on Integrity Linux for SAP WAS Central Instances
Cluster Configuration
Chapter 274
Serviceguard Configuration
Refer to the standard Serviceguard for Linux for Integrity manual
Managing Serviceguard for Linux to learn about creating and editing a
cluster configuration file and how to apply it to initialize a cluster with
cmquerycl(1m) and cmapplyconf(1m). The following section assumes that
a cluster is up and running on the intended primary node and all backup
nodes.
The toolkits are configured up to now, but what is missing are the
standard configuration and control files for Serviceguard packages.
Logon as root on the primary host.
IS800 Installation Step:
Enter the package directory ${SGCONF}/<SID>. Create standard package
configuration and control files for each package.
For the one package concept:
cmmakepkg -p dbci.config
cmmakepkg -s dbci.sh
For the two package concept you need two configuration and two control
files:
cmmakepkg -p db.config
cmmakepkg -p ci.config
cmmakepkg -s db.sh
cmmakepkg -s ci.sh
For the a application server package installation you need:
cmmakepkg -p d<INSTNR><SID>.config
cmmakepkg -s d<INSTNR><SID>.sh
IS810 Installation Step:
The created configuration file(s) need to be edited. Refer to the Managing
Serviceguard for Linux user’s guide for general information about the file
content. The naming convention <pkgtype><SID> should be used for the
PACKAGE_NAME parameter. Example:
PACKAGE_NAME dbciC11