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

the failover entity for a combination of ABAP-stack, JAVA-stack, double-stack instances; and

optionally Central Service Instances or Enqueue Replication Service Instances of an SAP System.

For MaxDB or Oracle-based SAP database services, the module sgesap/dbinstance can be

used. The module to cluster SAP liveCache instances is called sgesap/livecache. In addition

to these three major modules, there are two more modules that enable easy clustering of smaller

SAP infrastructure software tools sgesap/sapinfra and allow to manipulate the behavior of

non-clustered SAP instances sgesap/sapextinstance. The covered infrastructure tools include

the SAP sapccmsr, saposcol, rfcadapter, and saprouter binaries. Depending on the

installation type SAP Web Dispatcher can be configured with either sgesap/sapinstance or

sgesap/sapinfra. Other SGeSAP module names exist that provide a combination or subset of

the functionality of some of the five modules mentioned above. They were primarily defined for

convenience reasons to simplify configuration steps for standard use cases.

In legacy packaging, each software Single Point of Failure defines a SGeSAP package type.

SGeSAP follows a consistent naming convention for these package types. The naming conventions

were created to be independent of SAP software release versions. This provides a similar approach

for each SPOF, regardless of whether it appears in the latest SAP Netweaver stack or SAP software

that was released before the first design of SAP Application Server. Older SAP components

sometimes only support a subset of the available clustering options.

Defining a mixture of legacy packages and module-based packages is possible in the same cluster.

MDM 5.5 packages are available in legacy-style packages only.

NOTE: All legacy-style packages will be discontinued at a later point in time.

HP strongly recommends that any SGeSAP configuration use only modular packages.

For more information on modular package creation see sections:

• “Easy package deployment for modular package creation ” (page 69)

• “ Graphical interface for guided modular package creation” (page 72)

• Migrating Packages from Legacy to Modular Style white paper

Table 2 Mapping the SGeSAP legacy package types to SGeSAP modules and different SAP naming

conventions

Commonly used SAP instance namesSGeSAP module namesSGeSAP legacy package type

DVEBMGS (as Central Instance), ASCSsgesap/sapinstance

alternatives: sgesap/scs

sgesap/ci

SCSjci

AREP, ENR, ERSsgesap/sapinstance

alternatives: sgesap/ers

arep

REP, ENR, ERSrep

D, DVEBMGS (new)sgesap/sapinstanced

JDI, JD, JC, Jjd

sgesap/dbinstance

alternatives:sgesap/db

sgesap/maxdb sgesap/oracledb

sgesap/livecachelc

General Concepts of SGeSAP 9