Managing Serviceguard Extension for SAP, December 2007

Step-by-Step Cluster Conversion
SAP Preparation
Chapter 3 93
Specify the created control scripts that were created earlier on as run
and halt scripts:
RUN_SCRIPT /etc/cmcluster/<SID>/<pkg_name>.control.script
HALT_SCRIPT /etc/cmcluster/ <SID>/<pkg_name>.control.script
Specify subnets to be monitored in the SUBNET section.
In the /etc/cmcluster/<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 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 takes place.
The debug file allows manual SAP instance shutdown and startup
operations during installation.
touch /etc/cmcluster/<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.