Managing Serviceguard Extension for SAP Version B.05.10, September 2010

Refer to the Managing Serviceguard user guide for general information about the generic file
content. A minimum configuration will do for the purpose of supporting the SAP installation.
At least the following parameters should be edited: package_name, node_name, ip_address
and monitored_subnet.
The package_name can be chosen freely. It is often a good approach to stick to the naming
convention that combines the name of the SAP Instance type and the SAP System ID. Examples:
dbciC11, scsC11. Specify node_name entries for all hosts where the package should be able to
run. 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.
Specify at least one virtual IP. Specify subnets to be monitored in the monitored_subnet
section.
The only SAP-specific parameters that need to be set is the planned SAP system id sap_system.
Preparation Step: MS1220
Create a debug file on the system where the installation takes place.
The debug file allows manual SAP instance shutdown and startup operations during installation.
touch /var/adm/cmcluster/debug_<package_name>
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: MS1230
The configuration file needs to be applied and the packages started.
This step assumes that the cluster as such is already configured and started. Please refer to the
Managing Serviceguard user guide if more details are required.
cmapplyconf -P ./sap.config
cmrunpkg -n <sap_installation_host> <package_name>
All virtual IP addresses should now be configured. A ping command should reveal that they
respond to communication requests.
Preparation Step: IS1300
Before installing the SAP Application Server 7.0, some OS-specific parameters need adjustment.
Verify or modify HP-UX kernel parameters as recommended by the SAP 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.
Check the installed Java SDK with the requirement as of the SAP 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: IS1320
Before invoking the SAP installer, some additional requirements need to be met that are described
in the SAP installation documentation.
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 41