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

SGeSAP modules are implemented to work independent of the used package naming. For these
packages, the above naming scheme is a recommendation.
For a description and combination restrictions on those packages, refer to chapter 1—“Designing
SGeSAP Cluster Scenarios.”
The legacy package installation steps cover HP-UX 11i v1, HP-UX 11i v2, and HP-UX 11i v3 using
Serviceguard 11.16 or higher.
Modular packages can be used with HP-UX 11i v2 and HP-UX 11i v3 using Serviceguard 11.18
or higher.
The package creation process is split into the following logical tasks:
• SAP Preparation
• HP-UX Configuration
• Modular Package Configuration
• Legacy Package Configuration
• HA NFS Toolkit Configuration
• Auto FS Configuration
• Database Configuration
• SAP Application Server Configuration
The tasks are presented as a sequence of steps. Each installation step is accompanied by a unique
number of the format XXnnn, where nnn are incrementing values and XX indicates the step
relationship, as follows:
• ISnnn—Installation Steps mandatory for all SAP packages
• OSnnn—Optional Steps
• LSnnn—Installation Steps mandatory for legacy packages only
• MSnnn—Installation Steps mandatory for module based packages only
• ORnnn—Oracle database only steps
• SDnnn—SAPDB/MAXDB or LC database only steps
• DBnnn – DB2 steps only
• REnnn—Replicated Enqueue only steps
If you need assistance during the installation process and need to contact HP support, you can
refer to the installation step numbers to specify your issue. Also include the version of this
document. The installation step numbers were reorganized for this document version and don't
resemble earlier releases.
Whenever appropriate, HP-UX sample commands are given to guide you through the integration
process. It is assumed that hardware as well as the operating system and Serviceguard are already
installed properly on all cluster hosts. Sometimes a condition is specified with the installation
step. Follow the information presented only if the condition is true for your situation.
NOTE: For installation steps in this chapter that require the adjustment of a SAP-specific
parameter to run the SAP system in a switchover environment, example values are given. These
values are for reference ONLY and it is recommended to read and follow the appropriate SAP
OSS notes for SAP's latest recommendation. Whenever possible, the SAP OSS note number is
given.
The SAP Application Server installation types are ABAP-only, Java-only, and Add-in. The latter
includes both the ABAP and the Java stack.
In principle, all SAP cluster installations look very similar. Older SAP systems get installed in
the same way as they would without a cluster. Cluster conversion takes place afterwards and
includes a set of manual steps. Some of these steps can be omitted because the introduction of
high-availability installation options to the SAP installer SAPINST. In this case, a part of the
cluster configuration is done prior to the SAP installation as such. The SAP Instances can be
38 Step-by-Step Cluster Conversion