Managing Serviceguard Extension for SAP on Integrity Linux, December 2005

Step by Step Installation of SGeSAP on Integrity Linux for SAP WAS Central Instances
Cluster Configuration
Chapter 2 75
Specify NODE_NAME entries for all hosts on which the package should
be able to run.
Specify the package control script names in the package configuration
files:
For one package concept specify in ${SGCONF}/<SID>/dbci.config:
RUN_SCRIPT ${SGCONF}/<SID>/dbci.sh
HALT_SCRIPT ${SGCONF}/<SID>/dbci.sh
For two package concept specify in ${SGCONF}/<SID>/db.config:
RUN_SCRIPT ${SGCONF}/<SID>/db.sh
HALT_SCRIP ${SGCONF}/<SID>/db.sh
For two package concept specify in ${SGCONF}/<SID>/ci.config:
RUN_SCRIPT ${SGCONF}/<SID>/ci.sh
HALT_SCRIPT ${SGCONF}/<SID>/ci.sh
For an application server package specify in
${SGCONF}/<SID>/d<INSTNR><SID>.config:
RUN_SCRIPT ${SGCONF}/<SID>/d<INSTNR><SID>.sh
HALT_SCRIPT ${SGCONF}/<SID>/d<INSTNR><SID>.sh
Specify subnets to be monitored in the SUBNET section.
OS820 Optional Step:
If the SAP message server should be monitored as Serviceguard service,
the dbci.config or ci.config file needs to configure the monitoring. The
recommended naming for the service is <pkgtype><SID>ms.
Example entries:
SERVICE_NAME dbciC11ms
SERVICE_FAIL_FAST_ENABLED YES
SERVICE_HALT_TIMEOUT 300