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

The message server should generally be configured to restart locally by specifying restart in the
SAP (start) profile. If Serviceguard recognizes the SAP Message Server to be unavailable for a
longer period of time, it assumes that the restart doesn’t work or is accidentally not configured.
Serviceguard will switch the package and try to restart on different hardware, usually the active
enqueue replication server. SGeSAP service monitors will be paused within 30 seconds (based
on default value of timer in monitor) if a debug file gets created for the package. For details see
chapter 6 –”SGeSAP Cluster Administration.” The debug file can be used to allow manual SAP
instance shutdowns and startups. Make sure that all packaged SAP components are running
when removing the debug file. Otherwise a failover will occur.
NOTE: The message server monitor works without command line parameters in the service
command string service_cmd. It will configure itself automatically during startup and monitors
all message servers that are clustered within the package.
Example entries for the package configuration file:
service_name scsC11ms
service_cmd “/opt/cmcluster/sap/SID/sapms.mon”
service_restart 2
service_fail_fast_enabled no
service_halt_timeout 300
Optional Step: OS446
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 monitoring resource is provided by SGeSAP within the HP-UX Event
Monitoring System (EMS). It does not need to be created. 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
/applications/sap/enqor/<SID>ascs 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:
resource_name /applications/sap/enqor/C11ers21
resource_polling_interval 30
resource_start automatic
resource_up_value != 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:
resource_name /applications/sap/enqor/C11ers21
resource_polling_interval 30
resource_start automatic
resource_up_value != serving
Subsection for external Application Server handling: OS471
Parameters that can be set to influence non-critical additional instances on cluster nodes or
outside of the cluster ("external Application Servers") if module sgesap/sapextinstance is used.
74 Step-by-Step Cluster Conversion