Managing Serviceguard Extension for SAP, December 2007

Step-by-Step Cluster Conversion
SGeSAP Configuration
Chapter 3150
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
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 SAP ABAP or SAP add-in installations. Do
not combine a database with a liveCache in a single package.
• 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 of type RE in
combination with this CI.
• arep: an ASCS Replicated Enqueue instance.
• rep: an SCS Replicated Enqueue instance.
• d: one or more virtualized SAP ABAP Application Instances that are
considered mission-critical due to special use cases.
• jdb: a database exclusively utilized by J2EE engines that are not
part of Application Server Instances. Do not combine a database with
a liveCache in a single package.
• 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 Application Servers (SCS).
• jd: one or more virtualized SAP JAVA Application Instances.