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

Step-by-Step Cluster Conversion
SAP Preparation
Chapter 3 95
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 with the SAP instances that are
going to be installed. Edit the array and create at least one virtual IP:
IP[0]=xxx.xxx.xxx.xxx
Distribute the edited package templates to all cluster nodes.
Only if the SAP components are meant to be able to run on different
nodes, several packages have to be created using different virtual IPs.
NW04J440 Preparation Step:
Create a debug file on the system on which the installation will run. The
debug file allows manual SAP instance shutdown and startup operations
during installation.
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 SCS instance by running them on
different cluster nodes during normal operation. For convenience, all
SCS and database installation steps should be done on a single machine.
Due to the virtualization, it is easy to separate the instances later on.
Make sure that the JAVA Central Instance JC00 gets installed on the
host where it is meant to be run afterwards.
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 ${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.
NW04J1300 Preparation Step:
Before installing the J2EE Engine some OS-specific parameters have to
be adjusted. Verify or modify the Linux kernel parameters as
recommended by NW04 Master Guide Part 1. Be sure to propagate
changes to all nodes in the cluster.