Managing Serviceguard Extension for SAP, December 2007

Step-by-Step Cluster Conversion
Cluster Configuration
Chapter 3 139
/etc/cmcluster/<SID>/customer.functions
Since SGeSAP B.03.12, there is only one file for the package control logic
that can be used for many package combinations; SGeSAP automatically
detects the package setup with the desired SAP component configured.
cp /opt/cmcluster/sap/SID/sapwas.cntl
/etc/cmcluster/<SID>/sapwas.cntl
IS420 Installation Step:
Enter the package directory /etc/cmcluster/<SID>. Create standard
package configuration and control files for each package. The files might
already exist, if the SAP System got installed onto virtual IP addresses.
Decide which package types are needed in the high availability
environment depending on the installed SAP System generate a control
and configuration file for each package. These files should always be
created using the standard Serviceguard commands. The package types
are recommended to be named <pkg_name>.control.script for a
control file and <pkg_name>.config for a configuration file.
For any kind of package (substitute <pkg_type> with your package type):
cmmakepkg -s /etc/cmcluster/<SID>/<pkg_name>.control.script
cmmakepkg -p /etc/cmcluster/<SID>/<pkg_name>.config
IS430 Installation Step:
The created configuration file(s) need to be edited. Refer to the Managing
Serviceguard User’s Guide for general information about the file content.
The naming convention <pkg_name> should be used for the
PACKAGE_NAME parameter.
For example:
PACKAGE NAME dbciC11
Specify NODE_NAME entries for all hosts on which the package should
be able to run.
Specify the package control script names in the package configuration
files:
Specify in /etc/cmcluster/<SID>/<pkg_name>.config:
RUN_SCRIPT /etc/cmcluster/<SID>/<pkg_name>.control.script
HALT_SCRIPT /etc/cmcluster/ <SID>/<pkg_name>.control.script