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

The Serviceguard package running the Standalone Enqueue should be configured to failover to the node
running the Enqueue Replication Service. In the event of a failure of the Serviceguard package for the
Standalone Package it will then failover to that node. It now can reclaim the replicated SAP locks that the
Enqueue Replication Service had collected.
Enqueue Replication for a Dual-Stack Configuration
A SAP system making use of a “dual-stack ABAP/JAVA” configuration, will each have its own Standalone
Enqueue Services and its own Enqueue Replication Services.
For JAVA (SCS) and ERSFor ABAP (ASCS) and ERS
The Standalone Enqueue Service is part of the (SCS) instance.The Standalone Enqueue Service is part of the
(ASCS) instance.
The SCS instance will also be running a SAP Message Server.The ASCS instance will also be running a SAP
Message Server.
One Enqueue Replication Services (ERS) will be running for the JAVA instance.One Enqueue Replication Services (ERS) will be
running for the ABAP instance.
NOTE:
If the SAP system only has ABAP components installed, SAP runs the following instances; ABAP ASCS
and ERS.
•
• If the SAP system is configured to only run JAVA components, SAP runs the following instances; JAVA
SCS and ERS.
• If ABAP and JAVA both are configured, SAP runs ABAP ASCS and ERS as well as JAVA SCS and ERS
instances.
Each instance must be configured to run as its own Serviceguard package. Furthermore, each SAP instance
<SID> must have a unique instance number <INR>
The following configuration is used as an example:
DescriptionSAP Instance
Runs the ABAP Standalone Enqueue Service and the ABAP Message Service for SAP system SX1. SAP instance
number is 02.
ASCS02:
Runs the ABAP Enqueue Replication Service for SAP system SX1. SAP instance number is 12. It contains the
SAP mirror lock data from instance ASCS02
ERS12:
Runs the JAVA Standalone Enqueue Service and the JAVA Message Service for SAP system SX1. SAP instance
number is 03.
SCS03:
Runs the JAVA Enqueue Replication Service for SAP system SX1. SAP instance number is 13. It contains the SAP
mirror lock data from instance SCS03.
ERS13:
The following SGeSAP naming conventions are used for Serviceguard packages:
Example: SGeSAP Package NameSAP Instance
ascsSX1ascs<SID>:
ers12SX1ers<INR><SID>:
scsSX1scs<SID>:
ers13SX1ers<INR><SID>:
Enqueue Replication 23