Managing Serviceguard Extension for SAP on Linux (IA64 Integrity and x86_64), April 2009

cp ${SAPSTAGE}/sap.functions ${SGCONF}/sap.functions
cp ${SAPSTAGE}/SID/sap.config ${SGCONF}/<SID>/sap.conf
cp ${SAPSTAGE}/SID/customer.functions ${SGCONF}/<SID>/customer.functions
cp ${SAPSTAGE}/SID/sapwas.sh ${SGCONF}/<SID>/sapwas.sh
Enter the package directory ${SGCONF}/<SID>. For each Serviceguard package that will be configured
create:
• a Serviceguard configuration template (xxx.config)
• a Serviceguard control script template (xxx.control.script)
For example for a three package SAP configuration with one database instance (db) and one central instance
(ci) and one dialog instance (d01).
cmmakepkg -p db<SID>.config
cmmakepkg -s db<SID>.control.script
cmmakepkg -p ci<SID>.config
cmmakepkg -s ci<SID>.control.script
cmmakepkg -p d01<SID>.config
cmmakepkg -s d01<SID>.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
Optional Step: OS430
Specify NODE_NAME entries for all hosts on which the package should be able to run.
If the package can run on any of the cluster nodes a "*" can be entered:
NODE_NAME *
In the Serviceguard configuration file (xxx.config) specify the script that gets executed when running or
halting the Serviceguard package. The script that get executed will be the Serviceguard control script
(xxx.control.script).
db.config:
RUN_SCRIPT <SGCONF>/<SID>/db.control.script
HALT_SCRIPT <SGCONF>/<SID>/db.control.script
ci.config:
Cluster Configuration 75