Managing Serviceguard Extension for SAP on Linux (IA64 Integrity and x86_64), April 2009

Be sure to propagate changes to all nodes in the cluster.
Preparation Step: NW04J1310
The SAP J2EE engine needs a supported and tested JAVA SDK on all cluster nodes.
Check the installed JAVA SDK with the requirement as of the NW04 Master Guide Part 1. Be sure to install
the required SDK on all nodes in the cluster.
In case the J2EE engine uses security features that utilize the need for the JAVA Cryptographic Toolkit, it has
to be downloaded both from the Sun website as well as from the SAP Service Marketplace.
Preparation Step: NW04J1320
Before invoking the SAP installer, some additional requirements have to be met that are described in the
SAP installation documentation for SAP WAS 6.40.
These are not specific to cluster implementations and apply to any SAP installation. They usually involve the
setting of environment variables for SAPINST, like the DISPLAY variable, the temporary installation directory
TMP, etc.
Installation Step: NW04J1330
The installation is done using the virtual IP provided in the Serviceguard package.
The SAPINST installer is invoked with the parameter SAPINST_USE_HOSTNAME to enable the installation
on a virtual IP address of Serviceguard. This parameter is not mentioned in SAP installation documents, but
it is officially supported. The installer will show a warning message that has to be confirmed.
The installation of the SAP J2EE Engine 6.40 is done in several steps, depending on the installation type:
• First, the SAP System Central Services Component (SCS) 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 virtual IP address of the DB package.
• After that, the Central Instance and all required Dialog Instances are established.
When starting the SAPINST installer, 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 Serviceguard Extension for SAP on Linux clusters is included on the installation DVD/CD's distributed
by SAP.
SAP Preparation 55