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

Step-by-Step Cluster Conversion
Cluster Configuration
Chapter 3134
cmmakepkg -p db.config
cmmakepkg -s db.control.script
cmmakepkg -p ci.config
cmmakepkg -s ci.control.script
cmmakepkg -p d01.config
cmmakepkg -s d01.control.script
NOTE The above creates a default Serviceguard package. which in the first step
is not related to any of the SGeSAP/LX components yet. This package
can be started, stopped and relocated to other cluster nodes without
having any impact on the start or stop of any of the above SAP instances
(db), (ci) and (d01). The relationship to the start and stop SAP instances
will be established – in a later step - when the
customer_defined_halt_cmds and the customer_defined_run_commands
functions in the xxx.control.script scripts are edited a replaced with
the appropriate SGeSAP/LX commands for these SAP instances.
Configuring SGeSAP/LX on Linux
The Serviceguard configuration templates (xxx.config) must be edited.
They are located in directory ${SGCONF}/<SID>.
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. In the case of SAP
instance C11 the package name for (db), (ci) and (d01) would be:
db.config:
PACKAGE NAME dbC11
ci.config:
PACKAGE NAME ciC11
d01.config
PACKAGE NAME d01C11