Managing Serviceguard Extension for SAP on Linux (IA64 Integrity and x86_64), February 2008

Step-by-Step Cluster Conversion
SAP Preparation
Chapter 386
NOTE For JAVA-only based installations the only possible installation option is
a High Availability System installation.
A Netweaver 2004s 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]
• Central Instance (D) [ABAP and/or JAVA stack]
• Dialog Instance(s) (D) [ABAP and/or JAVA stack]
The potential SPOFs (Single Point of Failure) are the SCS, ASCS and DB
instances. The Dialog instance can be installed redundantly on nodes
inside or outside the cluster. The ABAP Central Instance for Netweaver
2004s is similar to a simple Dialog Instance, except that it is
pre-configured 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 2004s 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 become Serviceguard Extension for SAP on Linux packages. It will be
more convenient to do this once the SAP installation has taken place.
The following steps are performed as root user to prepare the cluster for
the SAP installation.