Managing Serviceguard Extension for SAP Version B.05.10, September 2010

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.
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 Installation Considerations', only the second part 'Creation
of Replication Instance' is required. The split of the Central Instance is then already effective and
an [A]SCS instance was created during installation.
In this case it is sufficient to ensure that the [A]SCS startup profile does not use local Restart
for the enqueue process and that the instance profile contains recommended replication parameter
settings, for example:
enque/server/internal_replication = true
enque/server/replication = true
enque/server/threadcount = 1
enque/enrep/keepalive_count = 0
enque/process_location = local
enque/table_size = 4096
ipc/shm_psize_34 = 0
Using Replicated Enqueue heavily changes the SAP instance landscape and increases the resource
demand: two additional SAP instances will be generated as the outcome of the splitting procedure.
There is a requirement for at least one additional unique SAP System ID. Unique means, that
the ID is not in use by any other SAP instance of the cluster. There is also a requirement for one
or two additional shared LUNs on the SAN and one or two additional virtual IP addresses for
SAP Preparation 43