HP Serviceguard Extension for SAP (SGeSAP) manual Step-by-Step Cluster Conversion

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

•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 to 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 SAP specific parameter in order 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 since 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 then be installed into a virtualized environment, which obsoletes the SAP Application Server Configuration steps that usually concluded a manual cluster conversion.

Therefore, it is important to first decide which kind of SAP installation is intended. The installation of a SAP High Availability System was introduced with Netweaver 2004s. For Netweaver 2004 JAVA-only installations there is a similar High Availability Option for SAPINST. All older SAP kernels need to be clustered manually. The SAP preparation chapter covers all three cases. It also describes how Enqueue Replication can be activated for use with SGeSAP. The exact steps for that also depend on the SAP release that gets used.

Other differences in cluster layout derive from the usage of HP Serviceguard Cluster Filesystem. Alternative setups use HA NFS packages and automounter technology to ensure cluster-wide access to filesystems.

Finally, the underlying database of course also causes slightly different installation steps.

34 Step-by-Step Cluster Conversion