Managing Serviceguard Extension for SAP, December 2007

Step-by-Step Cluster Conversion
SAP Preparation
Chapter 394
NW04J445 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 /etc/cmcluster/C11/jdbcijciC11.config
cmrunpkg -n <installation_host> jdbcijciC11
All virtual IP address(es) should now be configured. A ping command
should reveal that they respond to communication requests.
NW04J1300 Preparation Step:
Before installing the J2EE Engine some OS-specific parameters have to
be adjusted. Verify or modify HP-UX kernel parameters as recommended
by NW04 Master Guide Part 1. Be sure to propagate changes to all nodes
in the cluster.
NW04J1310 Preparation Step:
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.
NW04J1320 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 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.