User's Guide

between physical machines. HP does not support a conversion to a virtual IP after the initial installation
on a physical hostname for SAP JAVA engines.
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_USE_HOSTNAME=<reloc_jci>
NOTE: The SAPINST_USE_HOSTNAME parameter is not mentioned in SAP installation documents for the
SAP JAVA engine 6.40, but it is officially supported. The installer will show a warning message that has to
be confirmed.
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>.
</OS></X></SAPINST_MASTER_DVD>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 be starting.
Afterwards, the virtualized installation 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.
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
38 Step-by-Step Cluster Conversion