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

Step-by-Step Cluster Conversion
SAP Preparation
Chapter 3 93
Netweaver 2004 JAVA-only High Availability Option
This section describes the installation of a JAVA-only based Web
Application Server 6.40 as provided as part of Netweaver 2004SR1. A
SAP application relying on a JAVA-only Web Application Server 6.40 is
SAP Enterprise Portal 6.0. This component debuts the virtualized
installation with SAPINST that is generally used for Netweaver 2004s,
but this early procedure differs in many details from the final process.
In a landscape for a SAP WAS 6.40 JAVA the following components exist:
• JAVA System Central Services (SCS) [JAVA Message and Enqueue
Server]
• JAVA Central Instance (JC) [JAVA Dispatcher(s), Server(s), Software
Deployment Manager (SDM)]
• JAVA Dialog Instance(s) (JD) [JAVA Dispatcher(s), Server(s)]
• Database Instance (DB)
The potential SPOFs are the SCS and DB instances. The JAVA Central
instance needs to be installed locally on one server. Dialog instances can
be installed redundantly on nodes inside or outside the cluster.
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.
NW04J400 Preparation Step:
Create a Serviceguard package directory on each node of the cluster. This
directory will be used by all packages that belong to the SAP System
with a specific SAP System ID <SID>.
mkdir -p ${SGCONF}/<SID>