Registration

Dear SAP Community Member,
In order to fully benefit from what the SAP Community has to offer, please register at:
http://scn.sap.com
Thank you,
The SAP Community team.
Skip to end of metadata
Go to start of metadata


Purpose

The purpose of this page is to explain how the work processes of an SAP instance can be monitored through the CCMS infrastructure.

Overview

This page provides details about the CCMS monitoring infrastructure, specifically focused in the work process monitoring, providing details about how to find the monitoring functions and how to configure them accordingly.

CCMS Transaction RZ20

The CCMS monitoring infrastructure, a solution within SAP NetWeaver, centrally monitors any IT environments - from individual systems through networked SAP NetWeaver solutions, to complex IT landscapes incorporating several hundred systems. In this section, you learn about the Alert Monitor (transaction RZ20) and its monitoring functionalities.

Most of the work process monitoring functionalities can be found in transaction RZ20, by following the below path.

RZ20 transaction → SAP CCMS Monitor Templates → Entire System → <SID> → Application Server  R3Services.


Monitoring Dialog Work Process Resources

By expanding the Dialog box under the R/3 Services monitoring tree, as per the iniital image, you will have accessed to the dialog work process monitoring structure, as you can see below.
 

The MTEs for dialog work process monitoring shown above, can monitor the following resources.

Utilisation - Average usage of dialog work processes of an application server
PrivMode Utilisation - Percentage of dialog work processes in PRIV mode
NumberOfWpDIA - Number of dialog work processes
ErrorsInWPDIA - Number of errors in dialog work processes
ErrorFreqInWpDIA - Number of errors in dialog work processes per minute
EndedWpDIA - Number of completed dialog work processes
QueueLength - Average usage of dispatcher wait queue for dialog work processes
LongRunners - Average time for long-running dialog work processes

Monitoring Background Work Process Resources

By expanding the Background box under the R/3 Services monitoring tree, as per the initial image, you will have accessed to the background work process monitoring structure, as you can see below.

 

The MTEs for background work process monitoring shown above, can monitor the following resources.

Utilisation - Average usage of background work processes of an application server
NumberOfWpBTC - Number of background work processes
ErrorsInWPBTC - Number of errors in background work processes
ErrorFreqInWpBTC - Number of errors in background work processes per minute
EndedWpBTC - Number of completed background work processes 
ProgramErrors - Program error when executing background jobs
ServerSpecificQueueLength - Number of released jobs that are waiting to be executed
AbortedJobs - Terminated jobs on an application server

Monitoring Spool Work Process Resources

By expanding the Spool box under the R/3 Services monitoring tree, as per the initial image, you will have accessed to the spool work process monitoring structure, as you can see below.

The MTEs for spool work process monitoring shown above, can monitor the following resources.

Utilisation - Spool work process load percentage
NumberOfWpSPO - Number of spool work processes
ErrorsInWpSPO - Number of errors in spool work processes
ErrorFreqInWpSPO - Number of errors in spool work processes
EndedWpSPO - Number of completed spool work processes
QueueLength - Utilized area of dispatcher queue (percentage)
ServiceQueue - Utilized area of spool service queue (percentage)
ServiceQueuePriv - Utilized area of spool request queue for processing in order (in %)
ServiceQueuePages - Number of pages to be output in spool request queue
DeviceCacheUsed - Utilized area of entire device cache (percentage)
DeviceCacheFixed - Utilized area of fixed device cache (percentage)
HostspoolListUsed - Utilized area of host spool request list (percentage)

Monitoring Update and Update 2 Work Process Resources

By expanding the Update box under the R/3 Services monitoring tree, as per the iniital image, you will have accessed to the update V1 and V2 work process monitoring structure, as you can see below.

The MTEs for update V1 and V2 work process monitoring shown above, can monitor the following resources.

Update V1
QueueTime - 
SAP update task V1: Average wait time in dispatcher queue
Utilisation - SAP Update Task V1: Percentage load for update task work process
NumberOfWpUD1 - Number of update1 work processes
ErrorsInWpUD1 - Number of errors in update 1 work processes
ErrorFreqInWpUD1 - Number of errors in update 1 work processes per minute
EndedWpUD1 - Number of completed update 1 work processes
 

Update V2
QueueTime - 
SAP update task V2: Average wait time in dispatcher queue
Utilisation - SAP Update Task V2: Percentage load for update task work process
NumberOfWpUD2 - Number of update 2 work processes
ErrorsInWpUD2 - Number of errors in update 2 work processes
ErrorFreqInWpUD2 - Number of errors in update 2 work processes per minute
EndedWpUD2 - Number of completed update 2 work processes

Monitoring Enqueue Work Process Resources

By expanding the Enqueue box under the R/3 Services monitoring tree, as per the initial image, you will have accessed to the enqueue work process monitoring structure, as you can see below.

The MTEs for enqueue work process monitoring shown above, can monitor the following resources.

QueueLength - Monitoring object enqueue server: Percentage length of the queue
ErrorsInWpENQ - Number of errors in enqueue work processes
ErrorFreqInWpENQ - Number of errors in enqueue work processes per minute
EndedWpENQ - Number of completed enqueue work processes

Monitoring Scenarios Examples

  1. Using the MTEs called QueueLength, monitor the percentage of the dispatcher queue utilisation for that specific work process type. With this, you can proactively detect system bottleneck situations soon enough to prevent a system outage. SAP Note 15606 provides more details about the dispatcher queue overflow situations.
     
     
  2. Using the MTEs called Utilisation, you can proactively monitor whether all the work processes of an specific type are simultaneously occupied in the system, therefore, detecting specific scenarios where a bottleneck situation might occur, leading to requests waiting in the dispatcher queue.
     
  3. Using the MTEs called ErrorsInWp<type> you can proactively monitor whether errors occur in the work processes. These errors might point to other undesired known system misbehaviors, bringing them to your knowledge and allowing you to correct them.

CCMS Auto-Reaction Methods

In the CCMS monitoring infrastructure, you can set up any MTE available in transaction RZ20 to automatically trigger email alerts in case the values reported by them meet the threshould values defined. The next chapters will explain more details about the configuration process to achieve this.

Defining Threshold Values for the Monitored MTEs

The first step is to define which MTEs you want to monitor in transaction RZ20, with this, you can start to set up their thresholds accordingly, so you are alerted in the correct scenario. Follow the Adjusting the Threshold Values chapter from the Configuring Alert Triggering and Alert Reactions SAP online help documentation for a detailed step by step on how to achieve this.
 

Defining and Assigning Auto-Reaction Methods for the Monitored MTEs

The second step to achieve this configuration is to define and assign the auto-reaction methods to the desired MTEs in the CCMS monitoring infrastructure. In order to perform this configuration, follow the steps mentioned in the Defining an Automatic Alert Notification SAP online help documentation.


Alternatively, you can choose to define Central auto-reaction methods, which will trigger the email alert from the central system instead of the local system. For this configuration, refer to the SAP online help Setting Up Central Auto-Reaction Methods for more details.

Displaying MTE Performance Information Graphically

Withing the CCMS transaction RZ20, you can display the performance values shown by an specific MTE as a graphic, allowing you to make faster and more accurate analysis based on the reported data. In order to display the MTE values as a graphic, follow the below steps.

  1. Select the Performance MTE in RZ20.
  2. Click in the Display Details button. 



  3. Select whether you want to display the last 30 minutes or 24 hour value.
  4. Click in the "Display performance values graphically" button.



  5. The graphic is finally shown in the below format.

Related Content

Related Documents

Defining an Automatic Alert Notification

Configuring Alert Triggering and Alert Reactions

Setting Up Central Auto-Reaction Methods 

Related SAP Notes/KBAs

SAP Note 939616 - CCMS auto-reactions: Help with troubleshooting

SAP Note 176492 - Automatic email when an alert occurs (RZ20)

SAP Note 15606 - Overflow of dispatcher request queue



  • No labels