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 268
3. stop_addons_postci: relates to start_addons_preci
4. stop_addons_predb: relates to start_addons_postdb
5. stop_addons_postdb: relates to start_addons_predb
The customer.functions template that is delivered with SGeSAP/LX
IPF provides several examples within the hook functions. They can be
activated via additional parameters in the lower part of sap.config.
OS670 Optional Step:
SAPROUTER is a sample additional program that always starts on the
Central Instance host.
To start an saprouter on the CI host automatically, specify:
SAPROUTER_START=1
You can also provide an option string that is passed to the saprouter, for
example to set the path to the saprouttab file to reside on a shared
volume.
Typically, set a maximum of one saprouter inside of the cluster.
saprouters cannot share a service port. So make sure that you use
different ones, if a failover to the same node is possible for the
saprouters.
OS680 Optional Step:
Specify RFCADAPTER_START=1 to automatically start the RFC adapter
component, e.g. for Exchange Infrastructure XI 2.0 installations. Make
sure that the JAVA executables can be reached via the path of <sid>adm.
Example:
RFCADAPTER_START=1
RFCADAPTER_CMD=”run_adapter.sh”