Managing Serviceguard Extension for SAP, December 2007

Step-by-Step Cluster Conversion
Chapter 3 79
3 Step-by-Step Cluster
Conversion
This chapter describes in detail how to implement a SAP cluster using
Serviceguard and Serviceguard Extension for SAP (SGeSAP). 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 virtualize 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 Application Server configuration section can be omitted.
Various SGeSAP 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 (jdb),
• Replicated Enqueue for both ABAP and JAVA System Central
Services ([a]rep),
• ABAP Dialog Instances and Application Servers (d),
• JAVA Dialog Instances and Application Servers (jd)
• Highly Available NFS (sapnfs) and
• Combinations of these package types (dbci, jdbjci, 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 ERP, SAP ECC, SAP SRM/EBP, SAP CRM, SAP EP,
SAP KW, SAP SEM, SAP WPS and SAP XI/PI. Refer to the support
matrix published in the release notes of SGeSAP to get details whether
your SAP component is supported in Serviceguard clusters on HP-UX.