Managing Serviceguard Extension for SAP on Linux (IA64 Integrity and x86_64), February 2008

Step-by-Step Cluster Conversion
SAP Preparation
Chapter 3 87
NW04S400 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 /${SGCONF}/<SID>
NW04S420 Preparation Step:
Create standard Serviceguard package configuration and control files for
each package.
The SAP Netweaver 2004s instances are mapped to Serviceguard
Extension for SAP on Linux package types as follows:
• The ASCS Instance requires a ci package type.
• The SCS instance requires a jci package type.
• The database requires a db 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 ${SGCONF}/<SID>/<pkg_name>.control.script
cmmakepkg -p ${SGCONF}/<SID>/<pkg_name>.config
An example for SAP System C11 and a combined single Serviceguard
package using the standard naming convention would be:
cmmakepkg -s ${SGCONF}/<SID>/dbcijciC11.control.script
cmmakepkg -p ${SGCONF}/<SID>/dbcijciC11.config
NW04S430 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
${SGCONF}/<SID>/<pkg_name>.config:
PACKAGE_NAME, NODE_NAME, RUN_SCRIPT, HALT_SCRIPT, SUBNET