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

3 Step-by-Step Cluster Conversion
This chapter describes in detail how to implement a SAP cluster using Serviceguard and Serviceguard
Extension for SAP (Serviceguard Extension for SAP on Linux). It is written in the format of a step-by-step guide.
It gives examples for each task in great detail. Actual implementations might require a slightly different
approach. Many steps synchronize cluster host configurations or virtualized SAP instances manually. If these
tasks are already covered by different means, it might be sufficient to quickly check that the requested result
is already achieved. For example, if the SAP application component was already installed using a virtual
IP address, many steps from the SAP WAS configuration section can be omitted.
SGeSAP/LX Naming Conventions and Package Types
Various Serviceguard Extension for SAP on Linux package types are supported, including
• SAP Central Instances and ABAP System Central Services (ci)
• JAVA System Central Services (jci)
• Database Instances for ABAP components (db)
• Database Instances for J2EE components (db)
• Replicated Enqueue ABAP System Central Services (arep)
• Replicated Enqueue for the JAVA System Central Services (rep)
• ABAP Dialog Instances and Application Servers (d)
• Highly Available NFS (sapnfs)
• Combinations of these package types (dbci, dbjci, dbcijci,...)
These package types are used to provide failover capabilities to the following SAP components: SAP WAS,
SAP BW, SAP APO, SAP R/3, SAP R/3 Enterprise, SAP SRM/EBP, SAP CRM, SAP EP, SAP KW, SAP SEM,
SAP WPS and SAP XI. Refer to the support matrix published in the release notes of Serviceguard Extension
for SAP on Linux to get details whether your SAP component is supported in Serviceguard clusters on Linux.
liveCache packages require package type (lc). This package type gets covered in Chapter 4.
SGeSAP/LX Package Names
In order to ensure a consistent naming scheme in the following installation and configuration steps, the
Serviceguard Extension for SAP on Linux package names are assembled from the package type and SAP
System ID:
<pkg_name> = <pkg_type><SID> or, in case of ambiguous results
<pkg_name> = <pkg_type><INSTNR><SID>
Examples: dbC11, ciC11, dbciC11, dbcijciC11, dbC11, jciC11, dbjciC11, d01C11, d02C11,
arepC11<SID>
There is one exception in the naming convention, which concerns the Serviceguard package used for NFS
file systems in an SAP environment. Since this package can provide NFS support for all the SAP packages
in a cluster, the name (sapnfs) without any SID was chosen.
For a detailed description and combination restrictions on those packages, refer to chapter 1 - Designing
Serviceguard Extension for SAP on Linux Cluster Scenarios.
Installation Tasks and Installation Steps
The installation steps cover Suse, SLES and Redhat RHEL using Serviceguard 11.16 or higher.
The process is split into the following logical tasks:
• SAP Preparation
• Linux Configuration
• Cluster Configuration
SGeSAP/LX Naming Conventions and Package Types 47