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

PACKAGE_NAME, NODE_NAME, RUN_SCRIPT, HALT_SCRIPT, SUBNET
Specify NODE_NAME entries for all hosts on which the package should be able to run.
Specify the created control scripts that were created earlier on as run and halt scripts:
RUN_SCRIPT <SGCONF>/<SID>/<pkg_name>.control.script
HALT_SCRIPT <SGCONF>/<SID>/<pkg_name>.control.script
Specify subnets to be monitored in the SUBNET section.
In the ${SGCONF}<SID><pkg_name>.control.script file(s), there is a section that defines a virtual
IP address array. All virtual IP addresses specified here will become associated to the SAP and database
instances that are going to be installed. Edit the array and create at least one virtual IP:
IP[0]=1.1.1.31
Distribute the edited package templates to all cluster nodes with a remote command such as ftp, scp or
cmcp.
Preparation Step: NW04S440
Create a debug file on the system on which the installation takes place.
The debug file allows manual SAP instance shutdown and startup operations during installation. Basically
all the required file systems for this package get mounted, the virtual IP address is enabled and the SAP
instance now can be started or stopped manually.
touch ${SGCONF}/<SID>/debug
It does not matter, if the system is meant to be run in a multi-tier fashion that separates the database from
the ASCS instance by running them on different cluster nodes during normal operation. For convenience,
all installation steps should be done on a single machine. Due to the virtualization, it is easy to separate the
instances later on.
Preparation Step: NW04S445
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.
Preparation Step: NW04S1300
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.
Preparation Step: NW04S1310
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.
Preparation Step: NW04S1320
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.
SAP Preparation 51