Managing Serviceguard Extension for SAP Version B.05.10, December 2012

When starting the SAPINST installer for kernel 6.40, the first screen shows installation options that
are generated from an XML file called product.catalog located at
<SAPINST_MASTER_DVD>/IM<X>_OS/SAPINST/UNIX/<OS>. The standard catalog file
product.catalog has to be either:
• Replaced by product_ha.catalog in the same directory on a local copy of the DVD
-Or-
• The file product_ha.catalog can be passed as an argument to the SAPINST installer
It is recommended to pass the catalog as an argument to SAPINST. The XML file that is meant to
be used with SGeSAP clusters is included on the installation DVD/CD's distributed by SAP.
The SAPINST_USE_HOSTNAME option can be set as an environment variable, using export or
setenv commands. It can also be passed to SAPINST as an argument.
cd <COMPONENT_TMP_DIR>
<SAPINST_MASTER_DVD>/IM<X>_OS/SAPINST/UNIX/<OS>/sapinst\
<SAPINST_MASTER_DVD>/IM<X>_OS/SAPINST/UNIX/<OS>\
product_ha.catalog \
SAPINST_USE_HOSTNAME=reloc_jci>
The SAP installer should now have started.
Afterwards, the virtualized installation is complete, 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. In this stage 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.
SAP Web Dispatcher High Availability
SAP supports the installation of the Web Dispatcher in two different ways:
1. As W-type instance into an exclusive Web Dispatcher SID as Standalone Engine using sapinst.
2. Unpacking the Web Dispatcher archive into a /usr/sap/<SID>/sapwebdisp directory
of a SAP Netweaver installation and bootstrapping it there.
In case of installation as an instances, it can be clustered using sgesap/sapinstance module. One
or more SAP Web Dispatcher instances can be configured into the package.
The second installation type is handled by SGeSAP’s sapinfra module. For more information, see
installation step OS472.
SAP Gateway High Availability
SAP supports SAP Gateway (“G”) instances, installed with sapinst as a Standalone Engine with
an exclusive SID. SAP Gateway can be clustered using the module sgesap/sapinstance.
Replicated Enqueue Conversion
This section describes how a SAP ABAP Central Instance DVEBMGS<INSTNR> can be converted
to use the Enqueue Replication feature for seamless failover of the Enqueue Service. The whole
section can be skipped if Enqueue Replication is not going to be used. It can also be skipped in
case Replicated Enqueue is already installed. The proceeding manual conversion steps can be
done for SAP applications that are based on ABAP kernel 4.6D and 6.40. These kernels are
supported on SGeSAP with Replicated Enqueue, and SAP is not delivering installation routines that
install Replicated Enqueue configurations for these releases, so the manual conversion steps become
necessary. The 4.6D kernel does require some kernel executables of the 6.40 kernel to be added.
If the SAP installation was done for Netweaver 2004 Java-only, Netweaver 2004s, or a newer
release as documented in section “SAP Pre-Installation Considerations” (page 46), only the second
50 Step-by-Step Cluster Conversion