Managing Serviceguard Extension for SAP Version B.05.10, December 2012

The SAP Application Server installation types are ABAP-only, Java-only, and double-stack. 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 installed into
a virtualized environment that 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 causes slightly different installation steps.
SAP Preparation
This section covers the SAP specific preparation, installation, and configuration before creating a
high available SAP System landscape. This includes the following logical tasks:
• SAP Pre-Installation Considerations
• Replicated Enqueue Conversion
SAP Pre-Installation Considerations
This section gives additional information that help with the task of performing SAP installations in
HP Serviceguard clusters. It is not intended to replace any SAP installation manual. SAP installation
instructions provide complementary information and should be consulted in addition to this.
SAP Netweaver 2004s introduced High Availability installation options. In combination with
SGeSAP, these options can be activated to guide the clustering of SAP JAVA-only applications
based on kernel 6.40. The SAP Enterprise Portal 6.0 belongs to this group of applications. All SAP
components that are based on earlier SAP technology should to be installed in the standard way
as described by the SAP Installation Guides. They can be clustered after the initial installation. In
any case, it makes sense to already set up required file systems as documented in chapter “Designing
SGeSAP Cluster Scenarios” (page 8) to prevent avoidable conversion activities in a later stage.
The following paragraphs are divided into these installation options:
• SAP Netweaver High Availability
• Generic SAP Installation
SAP Netweaver High Availability
The SAP Netweaver High Availability options were officially introduced with Netweaver 2004s
technology. They are based on the SAP Application Server 7.x. The SAPINST installer for SAP
kernel 7.x offers the following installation options out of the box:
• Central System
• Distributed System
• High Availability System
46 Step-by-Step Cluster Conversion