Managing Serviceguard Extension for SAP Version B.05.10, September 2010

SAP J2EE Engine Enqueue and Message Services are isolated in the System Central Service
Instance.
SDM is not part of this instance. Specify the instance name in JCINAME, the instance ID number
in JCINR and relocatable IP address in JCIRELOC, as in the following example:
JCINAME=SCS
JCINR=01
JCIRELOC=0.0.0.0
Subsection for the REP component: OS665
SGeSAP supports SAP stand-alone Enqueue Service with Enqueue Replication.
It's important to distinguish between the two components: the stand-alone Enqueue Service and
the replication. The stand-alone Enqueue Service is part of the ci or jci component. The rep
component refers to the replication unit for protecting JAVA System Central Services. Specify
the instance name in REPNAME, the instance ID number in REPNR and the relocatable IP address
of the SAP instance for the replication service in REPRELOC. Example:
REPNAME=ERS
REPNR=00
REPRELOC=0.0.0.0
Subsection for the JD component: OS666
A set of SAP JAVA Application Servers can be configured in each Serviceguard package.
Set the relocatable IP address of the dialog instance in JDRELOC, the dialog instance name in
JDNAME and the instance ID number in JDNR. The startup of the J2EE engines get triggered
with the package, but the successful run of the JAVA applications does not yet get verified.
Example:
JDRELOC[0]=0.0.0.0
JDNAME[0]=JC
JDNR[0]=10
JDRELOC[1]=0.0.0.0
JDNAME[1]=J
JDNR[1]=11
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 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
Legacy Package Configuration 85