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

NOTE: All xxxRELOC parameters listed above have to use the same syntax as the IP[]-array in the package
control file.
When using the automounter the NFSRELOC does not need to be specified.
Subsection for the DB component: OS610
Serviceguard Extension for SAP on Linux performs activities specific to the database you use.
Specify the underlying database vendor using the DB parameter. Possible options are: ORACLE and MaxDB.
Refer to the Serviceguard Extension for SAP on Linux release notes to see whether the required vendor is
available for the SAP application component.
Example:
DB=ORACLE
Specify the relocatible IP address of the database instance. Be sure to use exactly the same syntax as
configured in the IP[]-array in the package control file.
Example:
DBRELOC=1.1.1.22
In the subsection for the DB component there is an optional paragraph for Oracle and MaxDB database
parameters. Depending on your need for special Serviceguard setups and configurations have a look at
those parameters and their description.
The variable db<SID>_SGESAP_COMP links the Serviceguard package name (=db<SID>) to SGeSAP
component type "DB". For example variable dbSX1_SGESAP_COMP=DB links Serviceguard package dbSX1
with SGeSAP component type "DB".
Example:
db<SID>_SGESAP_COMP="DB"
Subsection for the CI component: OS620
Provide information about the Central Instance if it will part of Serviceguard Extension for SAP on Linux
package.
Set the parameter CINAME to the SAP instance name where ABAP Enqueue and Message Service are located.
This usually is the Central Instance or the ABAP System Central Service. The name is either DVEBMGS or
ASCS. Note that the instance ID as defined by CINR is not part of CINAME.
Set the parameter CINR to the Instance ID of your Central Instance where ABAP Enqueue and Message
Service are located. This is most likely a SAP Central Instance or a ABAP System Central Service Instance.
The relocatible IP address of the instance should be specified in CIRELOC.
The variable ascs<SID>_SGESAP_COMP links the Serviceguard package name (=ascs<SID>) to SGeSAP
component type "CI". For example variable ascsSX1_SGESAP_COMP=CI links Serviceguard package
ascsSX1 with SGeSAP component type "CI"
The parameter CIENQUEUE_PROC_NAME can be used to specify the process name of the Standalone
Enqueue Service to be monitored. An example: CIENQUEUE_PROC_NAME = "en.sapSX1_ASCS02".
Example:
CINAME=DVEBMGS
CINR=00
CIRELOC=1.1.1.23
ascs<SID>_SGESAP_COMP=CI
In the subsection for the CI component there is a paragraph for optional parameters. Depending on your
need for special Serviceguard setups and configurations have a look at those parameters and their description.
Subsection for the AREP component: OS630
Serviceguard Extension for SAP on Linux 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 (arep) component refers to the
replication unit for protecting ABAP System Services.
84 Step-by-Step Cluster Conversion