Managing Serviceguard Extension for SAP Version B.05.10, December 2012

Module-based SGeSAP packages will handle the sapstart service agent automatically. For SAP
releases based on kernel 7.10 or higher, SGeSAP can also register an instance with the startup
framework as part of the package startup operation and de-register it as part of the package halt.
If the service agent is started via SGeSAP and configured to autostart the SAP instance, SGeSAP
will monitor the operation to make sure that the instance startup succeeds.
Installation Step: IS474
The configuration file 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.
The SGeSAP package configuration will be distributed to all nodes, verified on all nodes, and
activated by issuing the following command on the package configuration file that was created
and customized above:
cmapplyconf -P ./sap.config
Legacy Package Configuration
This section describes the cluster software configuration with the following topics:
• Serviceguard Configuration
• SGeSAP Configuration
• Global Default Settings
Serviceguard Configuration
Refer to the standard Serviceguard manual Managing Serviceguard to learn about creating and
editing a cluster configuration file and how to apply it to initialize a cluster with cmquerycl(1m)
and cmapplyconf(1m). The following section assumes that a cluster is up and running on the
intended primary node and all failover nodes.
Logon as root on the primary host.
Installation Step: LS400
Create a Serviceguard package directory. This directory will be used by all packages that belong
to the SAP System with a specific SAP System ID <SID>.
mkdir -p /etc/cmcluster/<SID>
Installation Step: LS410
The swinstall process copied relevant files to a staging area at /opt/cmcluster/sap for
reference .
The following files need to be copied from the repository to the SAP package directory:
cp /opt/cmcluster/sap/sap.functions /etc/cmcluster/sap.functions
cp /opt/cmcluster/sap/SID/sap.config /etc/cmcluster/<SID>/sap.config
cp /opt/cmcluster/sap/SID/customer.functions /etc/cmcluster/<SID>/customer.functions
SGeSAP automatically detects the package setup with the desired SAP component configured.
cp /opt/cmcluster/sap/SID/sapwas.cntl/etc/cmcluster/<SID>/sapwas.cntl
Installation Step: LS420
Enter the package directory /etc/cmcluster/<SID> . Create standard package configuration
and control files for each package. The files might already exist, if the SAP System got installed
onto virtual IP addresses.
Decide which package types are needed in the high availability environment depending on the
installed SAP System generate a control and configuration file for each package. These files should
always be created using the standard Serviceguard commands. The package types are
88 Step-by-Step Cluster Conversion