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

To remove an SAP infrastructure software component from this list, click on the radio button adjacent
to the SAP infrastructure software component you want to remove, then click Remove.
To edit a configured SAP infrastructure software component, click on the radio button adjacent to
the SAP infrastructure software component you want to edit, then click Edit>>. The SAP infrastructure
software component information will move to the Type, Start/Stop, and Parameters input
fields—where you can make changes. Click Update and the edited SAP infrastructure software
component information will be returned to the Configured SAP Infrastructure Software Components
list.
GI070 Service Monitoring considerations (sg/service module)
The following SGeSAP software monitors are available for SAP instances and their databases.
(Additional monitors provided for MDM and Livecache are described in separate sections of the
manual). Depending on the preceding configuration steps, one or more of the SGeSAP software
monitors might already be preselected for inclusion in the package:
• sapms.mon to monitor a message service that comes as part of a Central Instance or System
Central Service Instance for ABAP/JAVA usage.
• sapenq.mon to monitor an enqueue service that comes as part of a System Central Service
Instance for ABAP/JAVA usage.
• sapenqr.mon to monitor an enqueue replication service that comes as part of a Enqueue
Replication Instance.
• sapdisp.mon to monitor a SAP dispatcher that comes as part of a Central Instance or an
ABAP Application Server Instance.
• sapwebdisp.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.
• sapgw.mon to monitor a SAP Gateway (G-type instance)
• sapdatab.mon to monitor MaxDB, Oracle, DB2, and Sybase ASE database instances. In
addition it monitors xserver processes for MaxDB and listener processes for Oracle.
These monitors are located in /opt/cmcluster/sap/SID. Each monitor automatically performs
regular checks of the availability and responsiveness of a specific software service within all the
SAP instances that provide this service in the package.
For Oracle databases, issues with the Oracle listener process are detected and local restarts of
the listener are triggered by the monitor, if required.
To continue proper monitoring, 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_...
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.
If the WLM application toolkit for SAP is installed, sapdisp.mon service will also regularly create
(g)WLM input files for the (g)WLM procmap functionality. This functionality allows to distinguish
the work process types and create different process groups for each work process type (for example
to provide different computing resource limits to dialog and batch processing). The WLM application
78 Step-by-Step Cluster Conversion