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

Default SAP installations load the J2EE database scheme into the same database that the ABAP
Engine is using. In this case, no JDB component needs to be specified and this configuration section
does not need to be maintained.
For the parameter JDB, the underlying RDBMS is to be specified. Supported databases are ORACLE
or SAPDB, for example:
JDB=ORACLE
Also, a relocatable IP address has to be configured for the database for J2EE applications in
JDBRELOC.
Additionally, for the J2EE RDBMS, the database instance ID name in JDBSID and database
administrator in JDBADM is required to be specified:
JDBSID=EP6
JDBADM=oraep6
In the subsection for the JDB component there is a paragraph for optional parameters. Depending
on your need for special HA setups and configurations have a look at those parameters and their
description.
Subsection for the JCI component: OS660
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.
Legacy Package Configuration 95