Managing Serviceguard Extension for SAP Version B.05.10, September 2010

NOTE: For Java-only based installations, the only possible installation option is a High
Availability System installation.
It is strongly recommended to use the "High Availability System" option for all new installations
that are meant to be used with SGeSAP.
A SAP Application Server 7.0 may consist of any combination of the following components:
• Java System Central Services Instance (SCS) [Java Message and Enqueue Server]
• ABAP System Central Services Instance (ASCS) [ABAP Message and Enqueue Server]
• Dialog Instance(s) (D, JD, DVEBMGS) [ABAP and/or Java stack]
The potential SPOFs are the SCS, ASCS, and DB instances. The Dialog instance can be installed
redundantly on nodes inside or outside the cluster. The ABAP DVEBMGS instance for Netweaver
2004s (or higher) is similar to a simple Dialog Instance, except that it is preconfigured to contain
the services Batch, Update, Spool, and Gateway. For JAVA, a Central Instance runs the Java
Software Deployment Manager (SDM). These services can be also be configured redundantly
with other Dialog Instances.
The SAP Netweaver CDs/DVDs must be available either as physical copies or images on the
local or shared file system for the duration of the installation.
As preparation, simple Serviceguard packages for the clustered instances need to be created.
These packages provide the virtual IP addresses that are required during installation. The
package(s) will later on be altered to utilize SGeSAP functionality. It will be more convenient to
do this once the SAP installation has taken place. The following steps are performed as a root
user to prepare the cluster for the SAP installation.
Preparation steps MS12xx should be followed to create module-based packages. Preparation
steps LS12xx should be followed to create legacy packages.
Preparation Step: MS1200
Create a tentative Serviceguard package configuration for one or more SAP instances.
The first thing required is a SGeSAP configuration file that can be used to define the SAP
Serviceguard failover package. It is usually created with the following command:
cmmakepkg -m sgesap/sapinstance [-m ...] >./sap.config
For a database package, the module sgesap/dbinstance can be specified.
NOTE: SGeSAP modules can be referred to by using SGeSAP legacy package types. Covered
package types include: ci, scs and ascs, rep and arep.
Specification examples for SGeSAP modules:
cmmakepkg -m sgesap/db -m sgesap/ci
Creates a single package configuration file for database and SAP instance(s) (one package concept).
cmmakepkg -m sgesap/db
cmmakepkg -m sgesap/ci
Separates database and SAP instances into two package configuration files (two package concept).
cmmakepkg -m sgesap/scs
cmmakepkg -m sgesap/ers
Separates System Central Service and Enqueue Replication into two packages.
cmmakepkg -m sgesap/scs -m sgesap/ers
Immediately issues an error message, because System Central Services and Enqueue Replication
cannot share the same package.
Preparation Step: MS1210
The created configuration file needs to be edited.
40 Step-by-Step Cluster Conversion