Managing Serviceguard Extension for SAP, December 2007

Understanding Serviceguard Extension for SAP

The Replicated Enqueue

Chapter 132

Since there are no classical SAP Central Instances in configurations that

use Replicated Enqueue, the package naming convention shifts from

ci<SID> to ascs<SID> and from jci<SID> to scs<SID>. The SGeSAP

package types remain to be ci and jci. Package names for the Enqueue

Replication usually are arep<SID> and rep<SID> or alternatively

ers<INR><SID>. There might be two ERS instances for a single SAP

system, so the instance number needs to be added to create a unique

package naming.

Figure 1-5 Replicated Enqueue Clustering for ABAP and JAVA Instances

Enqueue Services also come as integral part of each ABAP DVEBMGS

Central Instance. This integrated version of the Enqueue Service is not

able to utilize replication features. The DVEBMGS Instance needs to be

split up in a standard Dialog Instance and a ABAP System Central

Service Instance (ASCS).

SGeSAP Cluster

Automated Replicated Enqueue

shared

disks

node1

ascsC11

scsC11

dbC11

ers00c11

JD04

node2

push

node3

ers01C11

d03C11

Application Servers not part of cluster