Managing Serviceguard Extension for SAP, December 2007

Step-by-Step Cluster Conversion
SAP Preparation
Chapter 392
NW04J400 Preparation Step:
Create a Serviceguard package directory on each node of the cluster. This
directory will be used by all packages that belong to the SAP System
with a specific SAP System ID <SID>.
mkdir -p /etc/cmcluster/<SID>
NW04J420 Preparation Step:
Create standard package configuration and control files for each
package.
The SAP JAVA instances are mapped to SGeSAP package types as
follows:
The SCS Instance requires a jci package type. The database requires a
jdb package type. The package files are recommended to be named
<pkg_name>.control.script for a control file and <pkg_name>.config
for a configuration file.
The packages are created with the following commands:
cmmakepkg -s /etc/cmcluster/<SID>/<pkg_name>.control.script
cmmakepkg -p /etc/cmcluster/<SID>/<pkg_name>.config
An example for SAP System C11 and a single package using the
standard naming convention would be:
cmmakepkg -s /etc/cmcluster/<SID>/jdbjciC11.control.script
cmmakepkg -p /etc/cmcluster/<SID>/jdbjciC11.config
NW04J430 Preparation 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.
A minimum configuration will do for the purpose of supporting the SAP
installation.
At least the following parameters should be edited in
/etc/cmcluster/<SID>/<pkg_name>.config:
PACKAGE_NAME, NODE_NAME, RUN_SCRIPT, HALT_SCRIPT, SUBNET
Specify NODE_NAME entries for all hosts on which the package should be
able to run.