User's Guide

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 they
can also 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 2 'Planning the Storage Layout' 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
The Central System and Distributed System installations build a traditional SAP landscape. They will install
a database and a monolithic Central Instance. Exceptions are Java-only based installations.
NOTE: For Java-only based installations the only possible installation option is a High Availability System
installation.
It is strongly recommended to use the "High Availability System" option for all new installations that are
meant to be used with SGeSAP.
A SAP Application Server 7.0 may consist of any combination of the following components:
• Java System Central Services Instance (SCS) [Java Message and Enqueue Server]
• ABAP System Central Services Instance (ASCS) [ABAP Message and Enqueue Server]
• Dialog Instance(s) (D, JD, DVEBMGS) [ABAP and/or Java stack]
The potential SPOFs are the SCS, ASCS and DB instances. The Dialog instance can be installed redundantly
on nodes inside or outside the cluster. The ABAP DVEBMGS instance for Netweaver 2004s (or higher) is
similar to a simple Dialog Instance, except that it is preconfigured to contain the services Batch, Update,
Spool and Gateway. For JAVA, a Central Instance runs the Java Software Deployment Manager (SDM).
These services though can be also configured redundantly with other Dialog Instances.
The SAP Netweaver CDs/DVDs must be available either as physical copies or images on the local or shared
file system for the duration of the installation.
As preparation, simple Serviceguard packages for the clustered instances have to be created. They provide
the virtual IP addresses that are required during installation. The package(s) will later on be altered to utilize
SAP Preparation 35