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

Create standard package configuration and control files for each package.
The SAP JAVA instances are mapped to Serviceguard Extension for SAP on Linux package types as follows:
The SCS Instance requires a (jci) package type. The database requires a (db) package type. The package
files are recommended to be named <pkg_name>.control.script for a control file and
<pkg_name>.config for a configuration file.
The packages are created with the following commands:
cmmakepkg -s ${SGCONF}/<SID>/<pkg_name>.control.script
cmmakepkg -p ${SGCONF}/<SID>/<pkg_name>.config
An example for SAP System C11 and a single package using the standard naming convention would be:
cmmakepkg -s ${SGCONF}/<SID>/dbjciC11.control.script
cmmakepkg -p ${SGCONF}/<SID>/dbjciC11.config
Preparation Step: NW04J430
The created configuration file(s) need to be edited. Refer to the Managing Serviceguard user's guide for
general information about the file content.
A minimum configuration will do for the purpose of supporting the SAP installation.
At least the following parameters should be edited in: ${SGCONF}/<SID>/<pkg_name>.config:
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
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]=1.1.1.31
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.
Preparation Step: NW04J440
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 use of virtualized IP
addresses, 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.
Preparation Step: NW04J445
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: NW04J1300
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.
54 Step-by-Step Cluster Conversion