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

toolkit documentation describes where the input files need to be referenced in the (g)WLM setup
in order to activate this functionality. The sapdisp.mon for modular packages creates files called
/var/adm/cmcluster/wlmprocmap.<SID>_<INSTNAME><INSTNR>_<hostname>.
The <hostname> parameter might be a virtual hostname, if the SAP instance runs on a virtual
hostname.
GI080 Package Resource considerations (sg/resource module)
If the enqueue service of the SAP System Central Services should also be handled, the automated
Replicated Enqueue handling including follow-and-push failover semantics needs to be activated
for a [A]SCS/ERS package pair:
The SGeSAP ENQueue Operation Resource (ENQOR) needs to be specified for each SCS, ASCS
or ERS instance. The Serviceguard Manager package configuration dialog will correctly preconfigure
this resource for inclusion in the package, if it is required.
The monitoring resource as such is realized by SGeSAP within the HP-UX Event Monitoring System
(EMS). It is available, if the system has an SAP system installed, that uses [A]SCS/ERS instance
pairs. Available resources can be checked with the command:
resls /applications/sap/enqor
The required resource has the name /applications/sap/enqor/<SID>ers<instnr> for
applications based on SAP kernel SAP 7.x.
NOTE: The required resource has the name /applications/sap/enqor/<SID>scs or for
SAP applications based on kernel 4.x or 6.x.
Example entries for a package that clusters a [A]SCS instance that is replicated within instance
ERS21:
• EMS Resource /applications/sap/enqor/C11ers21
• Polling Interval 30
• Start Type automatic
• Resource Up Values != IDLE
NOTE: If the package clusters SCS and ASCS instance, two enqor resources need to be defined.
Example entries for a package that clusters the replication instance ERS21:
• EMS Resource /applications/sap/enqor/C11ers21
• Polling Interval 60
• Start Type automatic
• Resource Up Values != SERVING
GI090 Apply package configuration.
After you complete all of the Create a Modular Package configuration screens, the Verify and
submit configuration change screen will be displayed. Use the Check Configuration and Apply
Configuration buttons at the bottom of the screen to confirm and apply your changes.
Command line interface for modular package creation
This section describes the cluster software 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 any cluster host.
Installation Step: MS400
Modular Package Configuration 79