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

Installation Step: IS1330
The installation is done using the virtual IP provided by the Serviceguard package. SAPINST
can be invoked with a special parameter called SAPINST_USE_HOSTNAME.
This prevents the installer routines from comparing the physical hostname with the virtual
address and drawing wrong conclusions.
The installation of the entire SAP Application Server 7.0 will happen in several steps, depending
on the installation type. Each time a different virtual hostname can be provided.
• First, the SAP System Central Services Component (SCS and/or ASCS) will be installed using
the virtual IP contained in the corresponding Serviceguard package.
• Then, the database instance will be set up and installed on the relocatable IP address of the
DB package.
• After that, the Central Instance and all required Dialog Instances are established. Virtual
IPs can be used here, too. It is recommended to do this, because it preserves the flexibility
to move instances 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 be passed to sapinst as an argument.
cd <COMPONENT_TMP_DIR>
DATA_UNITS/<NW-version>_IM_<OS>_<DB>/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.
42 Step-by-Step Cluster Conversion