Managing Serviceguard Extension for SAP, December 2007

Step-by-Step Cluster Conversion
SAP Preparation
Chapter 398
Afterwards, the virtualized installation for SAP J2EE Engine 6.40 is
completed, but the cluster still needs to be configured. The instances are
now able to run on the installation host, provided the corresponding
Serviceguard packages got started up front. It is not yet possible to move
instances to other nodes, monitor the instances or trigger automated
failovers. Do not shut down the Serviceguard packages while the
instances are running. It is possible to continue installing content for the
SAP J2EE Engine, before the cluster conversion as described in the
sections below gets performed.
Generic SAP Installation
Netweaver 2004s introduced High Availability installation options.
Similar options were used for Netweaver 2004SR1 JAVA-only
installations. All SAP components that are based on pre-Netweaver
2004s technology get installed in a standard fashion. No special case
applies due to the fact that the system is going to be clustered
afterwards. The required file systems should already be set up as
documented in Chapter 2 ‘Planning the Storage Layout’ to prevent
avoidable conversion activities in a later stage.
If the SAP application is not installed yet, consult the appropriate SAP
Installation Guides and perform the installation according to the
guidance given there.