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

Step-by-Step Cluster Conversion
SAP Preparation
Chapter 394
NW04J420 Preparation Step:
Create standard package configuration and control files for each
package.
The SAP JAVA instances are mapped to Serviceguard Extension for SAP
on Linux package types as follows:
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 single package using the
standard naming convention would be:
cmmakepkg -s ${SGCONF}/<SID>/dbjciC11.control.script
cmmakepkg -p ${SGCONF}/<SID>/dbjciC11.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:
${SGCONF}/<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.
Specify the created control scripts that were created earlier on as run
and halt scripts:
RUN_SCRIPT $SGCONF/<SID>/<pkg_name>.control.script
HALT_SCRIPT $SGCONF/<SID>/<pkg_name>.control.script