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

The Central System and Distributed System installations build a traditional SAP landscape. They will install
a database and a monolithic Central Instance. Exceptions are JAVA-only based installations.
NOTE: For JAVA-only based installations the only possible installation option is a High Availability System
installation.
A Netweaver 2004s 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]
• Central Instance (D) [ABAP and/or JAVA stack]
• Dialog Instance(s) (D) [ABAP and/or JAVA stack]
The potential SPOFs (Single Point of Failure) are the SCS, ASCS and DB instances. The Dialog instance can
be installed redundantly on nodes inside or outside the cluster. The ABAP Central Instance for Netweaver
2004s is similar to a simple Dialog Instance, except that it is pre-configured to contain the services Batch,
Update, Spool and Gateway. For JAVA, a Central Instance runs the JAVA Software Deployment Manager
(SDM). These services though can be also configured redundantly with other Dialog Instances.
The SAP Netweaver 2004s 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 have to be created. They provide
the virtual IP addresses that are required during installation. The package(s) will later on be altered to become
Serviceguard Extension for SAP on Linux packages. It will be more convenient to do this once the SAP
installation has taken place. The following steps are performed as root user to prepare the cluster for the
SAP installation.
Preparation Step: NW04S400
Create a Serviceguard package directory on each node of the cluster.
This directory will be used by all packages that belong to the SAP System with a specific SAP System
ID <SID>.
mkdir -p ${SGCONF}/<SID>
Preparation Step NW04S420:
Create standard Serviceguard package configuration and control files for each package.
The SAP Netweaver 2004s instances are mapped to Serviceguard Extension for SAP on Linux package
types as follows:
• The ASCS Instance requires a ci package type.
• The SCS instance requires a jci package type.
• The database requires a db package type.
• The package files are recommended to be named <pkg_name>.control.script for a control
file and <pkg_name>.config for a configuration file.
The packages are created with the following commands:
cmmakepkg -s ${SGCONF}/<SID>/<pkg_name>.control.script
cmmakepkg -p ${SGCONF}/<SID>/<pkg_name>.config
An example for SAP System C11 and a combined single Serviceguard package using the standard naming
convention would be:
cmmakepkg -s ${SGCONF}/<SID>/dbcijciC11.control.script
cmmakepkg -p ${SGCONF}/<SID>/dbcijciC11.config
Preparation Step: NW04S430
The created configuration file(s) need to be edited.
Refer to the Managing Serviceguard user's guide for general information about the file content. A minimum
configuration will do for the purpose of supporting the SAP installation.
At least the following parameters should be edited in ${SGCONF}/<SID>/<pkg_name>.config:
50 Step-by-Step Cluster Conversion