Managing Serviceguard Extension for SAP Version B.05.10, December 2012

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 exists, it is effective for compatibility reasons.
• If a sap<pkg_name>.conf file exists, it will overrule previous files and is effective.
• If a sap.config file exists, it will overrule previous files and is effective.
• If a sap<pkg_name>.config file exists, 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
Optional Step: OS670
The following arrays are used to configure special treatment of ABAP Application Servers during
package start, halt or failover .
These Application Servers are not necessarily 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 the failover node to allow
the failover to succeed. Often, this includes stopping less important SAP Systems, namely
consolidation or development environments. If any of these instances is a Central Instance, it might
be that there are additional Application Servers belonging to it. Not all of them are necessarily
running locally on the failover node. They can optionally be stopped before the Central Instance
gets shut down. This mechanism replaces the deprecated SERVER_CONSOLIDATION variable
and the RM* arrays of earlier SGeSAP 3.x versions.
• In the ASSID[*]-array specify the SAP System IDs of the instances that should be treated
with the package. Making this a configurable option allows to specify instances that belong
to the clustered SAP components. It also allows specification of different SIDs for less critical
SAP applications.
• In the ASHOST[*]-array, refer to the hosts on which the instances reside—this can be either
inside or outside of the cluster.
• The ASNAME[*]-array holds the instance names. These names are built by the abbreviations
of the services that are offered by the Application Server. The name of a Dialog instance
usually is D, the name of a Central Instance often is DVEBMGS.
• The ASNR[*]-array contains the instance IDs. If the corresponding ASHOST-entry specifies
a host that is part of the cluster, be sure to provide an ID that is different form the IDs used by
any packaged instance. You should also make sure that there is no other SAP instance on the
same host is using that ID.
• The ASTREAT[*]-array defines the way the instance is treated if the status of the package
changes. There are five different values that may be configured in any combination:
96 Step-by-Step Cluster Conversion