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

NOTE: It sometimes can be convenient for testing to allow root write access via NFS. This can be
enabled with flag -o rw, no_root_squash.... Use with caution.
Serviceguard Extension for SAP on Linux Configuration - sap.config
This section deals with the configuration of the SAP specifics of the Serviceguard packages SGeSAP/LX SAP
specific configuration file called ${SGCONF}/<SID>/sap.config. The file is structured into four main
sections that serve different purposes:
Section 1: Specification of the Packaged SAP Components
Section 2: Configuration of Application Server Handling
Section 3: Optional Parameters and Customizable Functions
Section 4: Global Defaults
Specification of the Packaged SAP Components
For each type of potentially mission-critical SAP software components there exists a set of configuration
parameters in SECTION 1 of the ${SGCONF}/<SID>/sap.config file. The information delivered here
will be specified exactly once and it will configure all packaged components of a <SID> within the cluster.
This is a central place of configuration, even if the intention is to divide the components into several different
packages. The mapping of components to packages will be done automatically. There is one subsection
per package type:
• db: a database utilized by a SAP WAS-based application.
• ci: a SAP Instance that has SPOF services defined. This might be a Central Instance with integrated
Enqueue and Message Service (DVEBMGS). It might also be a standalone Enqueue and Message
Service as part of a separate ABAP System Central Service instance (ASCS). A Replicated Enqueue
setup can be implemented by configuring at least one additional package in combination with this CI.
• arep: an ASCS Replicated Enqueue instance.
• rep: an SCS Replicated Enqueue instance.
• d: one or more virtualized SAP Application Instances that are considered mission-critical due to special
use cases.
• jci: a SAP JAVA System Central Services Instance that provides Enqueue and Message Service to
SAP J2EE engines that might or might not be part of SAP Web Application Servers (SCS).
NOTE: It is not allowed to specify a [j]ci and an [a]rep component as part of the same package.
Except Dialog Instance components of type d, each component can be specified once at most. Apart from
these exceptions, any subset of the SAP mission critical components can be maintained in sap.config to
be part of one or more packages.
It's important to distinguish between the two components: the Standalone Enqueue Service and the Enqueue
Replication Service.
In SGeSAP/LX context the ABAP Standalone Enqueue Service is configured part of the (ci), the JAVA
Standalone Enqueue Service is configured part of the (jci) component. In SGeSAP/LX context the (rep)
component refers to the JAVA Enqueue Replication Service and the (arep) component refers to the JAVA
Enqueue Replication Service.
Logon to the primary host as root and open the file ${SGCONF}/<SID>/sap.config with a text editor.
Installation Step: IS600
Specify the relocatable IP address where the Serviceguard NFS shared file systems can be reached. Format
is IPv4: nnn.nnn.nnn.nnn .
This value specifies the default for commonly shared file systems. An override is possible for the MaxDB
ini-directory, the global transport directory and the central executable directory individually by specifying
values for SQLRELOC, TRANSRELOC, CTEXERELOC.
Serviceguard Extension for SAP on Linux Configuration - sap.config 83