Managing Serviceguard Extension for SAP, December 2007

Step-by-Step Cluster Conversion
SGeSAP Configuration
Chapter 3156
Configuration of Application Server Handling
In more complicated setups, there can be a sap<pkg_name>.config file
for each package. For example a Dialog Instance package can have its
own sap<pkg_name>.config configured to start additional non-critical
Dialog Instances, whereas this setting should not be effective for a
Central Instance package with the same SID.
During startup of a package <pkg_name>, SGeSAP checks the existence
of SAP specific configuration files in the following order:
•If a sap.conf file exist, it is effective for compatibility reasons.
•If a sap<pkg_name>.conf file exist, it will overrule previous files
and is effective.
•If a sap.config file exist, it will overrule previous files and is
effective.
•If a sap<pkg_name>.config file exist, it will overrule previous files
and is effective.
NOTE When configuring package specific configuration files
sap<pkg_name>.config you will usually isolate section 1 in a global
sap.config file. All other sections should then be applied in the package
specific configuration files sap<pkg_name>.config, excluding the first
section.
For example SAP System C11 containing a Central Instance package
with Application Server handling would then have the following SGeSAP
configuration files:
• sap.config – Section 1,3,4 configured
• sapciC11.config – Section 2 configured
OS670 Optional Step:
The following arrays are used to configure special treatment of ABAP
Application Servers during package start, halt or failover. These
Application Servers are not virtualized or secured by Serviceguard, but
an attempt can be triggered to start, stop or restart them with the
package. If any triggered attempt fails, it doesn't automatically cause
failure of the ongoing package operation. The attempts are considered to
be non-critical. In certain setups, it is necessary to free up resources on