Managing HP Serviceguard Extension for SAP for Linux, December 2013

Table 16 SGeSAP monitors
DescriptionMonitor
To monitor a message service that comes as part of a Central Instance or System
Central Service Instance for ABAP/JAVA usage.
sapms.mon
To monitor an enqueue service that comes as part of a System Central Service
Instance for ABAP/JAVA usage.
sapenq.mon
To monitor an enqueue replication service that comes as part of an Enqueue
Replication Instance.
sapenqr.mon
To monitor a SAP dispatcher that comes as part of a Central Instance or an ABAP
Application Server Instance.
sapdisp.mon
To monitor a SAP Web Dispatcher that is included either as a part of (W-type)
instance installation into a dedicated SID or by unpacking and bootstrapping
into an existing SAP Netweaver SID.
sapwebdisp.mon
To monitor a SAP Gateway (G-type instance).sapgw.mon
To monitor MaxDB, Oracle, DB2, and Sybase ASE database instances.
Additionally, it monitors the xserver processes for MaxDB and listener processes
for Oracle.
sapdatab.mon
To monitor SAP liveCache instances.saplc.mon
To monitor SAP MDM servers.sapmdm.mon
To coordinate package startup in follow-and-push SCS/ERS scenarios. Used
internally by SGeSAP in the enqor MNP (multi node package).
sapenqor.mon
These monitors are located at directory $SGCONF/monitors/sgesap. Each monitor automatically
performs regular checks on the availability and responsiveness of a specific software component
within all the SAP instances that provide this service in the package.
NOTE: Sourcing the Serviceguard cluster configuration file with . /etc/cmcluster.conf
sets the above $SGCONF environment variable, as well as other cluster environment variables.
For Oracle databases, issues with the Oracle listener process and the database are detected and
local restarts of the listener are triggered by the monitor, if required.
For MaxDB databases, issues with the xserver processes and the database are detected and
local restarts are triggered by the monitor, if required. The SAP central service monitors detect
issues with the SAP startup agent of their instances and attempt local restarts of the agent software.
The SAP message service monitor sapms.mon can work in environments that use the
Restart_Program_... setting in the SAP instance (start) profiles of the [A]SCS instances to
achieve local restarts of failing message services without triggering unnecessary instance failovers.
It is recommended to use the SAP restart mechanism only for the message server.
The SAP enqueue replication service monitor sapenqr.mon has built-in software restart functionality.
It locally restarts the replication instance in case the software fails. A related failover is only
triggered, if the instance fails to remain up for more than ten minutes three times in a row.
Momentary instability of the software is reported as an alert message in the Serviceguard Manager.
The SAP enqueue service monitor sapenq.mon and the SAP dispatcher monitor does not provide
built-in software restart and the native SAP instance restart must not be configured either. Configuring
local restarts may lead to serious malfunctions for these software components.
Service monitors that are enabled to react to shutdown notifications from SAP's startup framework
include sapdisp.mon, sapgw.mon, sapms.mon, sapenq.mon, sapenr.mon,
sapwebdisp.mon, and sapmdm.mon. For more information on SAP's startup framework, see
“Performing SAP administration with SAP's startup framework ” (page 25) section.
5.1 Overview 51