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

For example, for a Serviceguard package configuration file: dbc11.config, when modifying the
RUN_SCRIPT variable, you would substitute:
RUN_SCRIPT<SGCONF>/dbC11.name with the following:
• For SUSE - RUN_SCRIPT /opt/cmcluster/conf/dbC11.name
• For Redhat - RUN_SCRIPT /usr/local/cmcluster/conf/dbC11.name
You can use the ${SGCONF} variable, when modifying the Serviceguard package control script file.
For example for a Serviceguard package control script file, dbC11.control.script when modifying
the SERVICE_CMD variable you would use ${SGCONF} and the system will automatically use the following:
SERVICE_CMD=”${SGCONF}/C11/dbC11.mon"
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
Web AS System 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 systems 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 Serviceguard Extension for SAP on Linux. The exact steps for that also depend on the
SAP release that gets used.
Alternative setups use Highly Available NFS packages and automounter technology to ensure cluster-wide
access to file systems.
Finally, the underlying database of course also causes slightly different installation steps.
The SAP Web Application Server installation types are ABAP-only, JAVA-only and Add-In. The latter includes
both the ABAP and the JAVA stack.
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 Installation Considerations
• Replicated Enqueue Conversion
SAP 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.
The following paragraphs are divided into these installation options:
• Netweaver 2004s High Availability System
• Netweaver 2004 JAVA-only High Availability Option
• Generic SAP Installation
Netweaver 2004s High Availability System
The Netweaver 2004s technology is based on the SAP Web Application Server 7.0. The SAPINST installer
for this offers the following installation options out of the box:
• Central System
• Distributed System
• High Availability System
SAP Preparation 49