Managing Serviceguard Extension for SAP on Linux (IA64 Integrity and x86_64), February 2008

Step-by-Step Cluster Conversion
SAP Preparation
Chapter 3 89
NW04S445 Preparation Step:
The package configuration needs to be applied and the package started.
This step assumes that the cluster as such is already configured and
started. Please refer to the Managing Serviceguard user’s guide if more
details are required.
cmapplyconf -P ${SGCONF}/C11/dbcijciC11.config
cmrunpkg -n <installation_host> dbcijciC11
All virtual IP address(es) should now be configured. A ping command
should reveal that they respond to communication requests.
NW04S1300 Preparation Step:
Before installing the SAP WAS 7.0 some OS-specific parameters have to
be adjusted. Verify or modify the Linux kernel parameters as
recommended by NW04s Master Guide Part 1. Be sure to propagate
changes to all nodes in the cluster.
The SAP Installer checks the OS parameter settings with a tool called
“Prerequisite Checker” and stops the installer when the requirements
are not met.
NW04S1310 Preparation Step:
The SAP J2EE engine needs a supported and tested JAVA SDK on all
cluster nodes.
Check the installed JAVA SDK meets the requirements in the NW04s
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.
NW04S1320 Preparation Step:
Before invoking the SAP installer, some additional requirements have to
be met that are described in the SAP installation documentation for SAP
WAS 7.0. 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.