HP Serviceguard Extension for SAP (SGeSAP) manual Configuration of Application Server Handling

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 relocatible IP address of the SAP instance for the replication service in REPRELOC. For 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 relocatible 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.

For 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 exist, it is effective for compatibility reasons.

•If a sap<pkg_name>.conf file exist, it will overrule previous files and is effective.

•If a sap.config file exist, it will overrule previous files and is effective.

•If a sap<pkg_name>.configfile exist, 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.

72 Step-by-Step Cluster Conversion