SAP Library - Find your answers

You can use this monitor to monitor the communication within an SAP system, between different systems, or to external applications. The monitor consists of the following six subtrees:

Features

To obtain information about a particular monitoring tree element, select the MTE and choose F1. The system displays a short description of the node. To see a detailed description of the node, choose Long Text.

Activities

To start the monitor, follow the procedure below:

...

1. Start the Alert Monitor using transaction RZ20 or choose CCMS ®Control/Monitoring ® Alert Monitor.

2. On the CCMS Monitor Sets screen, expand the SAP CCMS Monitor Templates set.

3. Start the Communications monitor from the list by double-clicking it.

Displaying Report Properties

Use

You can use Central Performance History Reports (CPH) to display selected performance values of the CPH directly or as a job. When you do this, the report itself (for example, when executed on the screen) does not contain the complete header data of the report ‑ such as the settings of the Report Definition or the execution time of the report.

You can find this information in the report properties. You can also edit the report properties to add your own remarks, and save the properties as a local file. No changes to the text have any effect on any function of the CPH.

Procedure

...

1. You can display the report properties from several functions:

¡ In the Report Browser, choose the desired report by double clicking it, and choose the Report Details pushbutton.

¡ Execute a report directly on the screen (see Scheduling and Executing a Report), and choose the Report Detailspushbutton.

2. In both cases, a screen appears on which the report properties are displayed. The screen has the following structure:

3. To save the report properties as a local file, choose Save as a Local File ().

Central Performance History of the Monitoring Architecture start page

A report displays Central Performance History (CPH) data. The prerequisite for the execution of a report is that a suitable report definition exists (see Creating a Report Definition). You can execute a report on the basis of a definition of this type; either directly or scheduled as a periodic job.

When you execute a report, you define the report properties that are not determined by the report definition. You define the following properties when you execute the report:

· Period to which the report should refer

· File format in which the report should be output (file type, direct output to the screen or to the database)

· Layout of the report

· Settings that allow the report to be executed regularly as a job

Procedure

Executing and Scheduling a Report

...

1. You can execute a report from several functions:

¡ In the overview screen of the CPH (transaction RZ23N), choose, in the Data Output and Reporting group box, the Execute Reports pushbutton.

¡ Choose CCMS ® Configuration ® Alert Monitor, or call transaction RZ21. The Monitoring: Properties and Methods screen appears. Choose Technical Infrastructure ® Central Perf. History ® Execute Reports.

¡ You can display a standard report for the selected MTE classes directly in the Detail Data for Monitoring Attributes screen of the Alert Monitor (see Display Detail Data and Tailor Display). When you do this, daily data with an hourly resolution is used. To do this, choose Central Perf. History ® Display as Report.

2. In all cases, the Central Performance History Report Execution screen appears. The screen consists of two parts. In the left part of the screen, you define all settings for a manual or automatic report execution. This part of the screen has the following structure:

3. Enter the desired definition in the input field Report Definition to be Executed.

4. In the Time Interval of the Report group box, enter the period to which the report should relate. The indicators have the following meaning:

5. In the Report Output Target group box, enter the format in which the report is to be displayed. The indicators have the following meaning:

6. Enter the desired display mode. The two possible values have the following meaning:

7. If you want to save the report as a file, specify where and under which name you want to save the file in the Filename and Path of the ASCII/Excel File/Name of the DB Entry group box.

If you want to save the report to the report database, specify in this group box the name under which the report is to be saved in the report database. If you do not specify a name, the name of the report definition used is used as the name.

8. If you want to execute the report directly, you can choose whether the file is to be saved on the local computer or on the current application server. If the report is scheduled as a job, the file can only be saved on an application server.

Choose the Job Settings pushbutton to specify the application server on which the job is to run for automatic report execution. Use an application server with as high availability as possible for this. If the report is saved as a file, the report is saved on this application server. If you do not specify a path, the file is saved in the home directory of the application server (profile parameter DIR_HOME).

To avoid the files for older reports being overwritten if the report is executed repeatedly, enter a question mark (?) (such as Report?.xls). When the file is saved, the question mark is replaced by the current date (such as Report20021031.xls).

9. If the report is to be regularly executed as a job, choose the Execute Periodically pushbutton. The Schedule Report group box is now available. You can specify the first execution and the period for job execution in this group box. To schedule the job, choose Schedule ().

10. If you want to execute the report directly, choose Execute Directly.

11. If you want to execute the report immediately in the background, choose Execute in Background.

Displaying and Editing the Report Settings that Are Automatically Executed

Reports that are executed in the background (see above) are displayed in the right part of the screen in the Active Automatic Report Executions in the Background table. All settings that you specified during the scheduling of this report are displayed in the columns of this table.

To change the settings, choose the desired scheduling by double clicking it, make the desired changes, and reschedule it by choosing Schedule ().

Note that the report definition is entered twice if you follow this procedure. If you do not want this, select the scheduling that you want to delete and choose Delete Selected Reporting Jobs ().

Central Performance History of the Monitoring Architecture start page

Purpose

If background dispatching is activated on the corresponding system, the local SCR is automatically updated at every system start. You can also update an SCR at any time. You have the following options:

• You can update the local SCR (see
Updating the Local Repository).
• You can update the data for the local system in the central repository (see
Updating the Central Repository).
• You can update the data for a subordinate system from the system of the central repository (see
Requesting an Update of the Repository).

In the monitoring architecture, you can react automatically to an alert using auto-reaction methods. These methods are automatically started in the case of an alert and by default are executed in the system in which the alert occurs. Almost no assignments are made in the standard SAP system; however, there are several predefined auto-reaction methods in the monitoring architecture that you can assign to any MTE classes.

As of SAP Web Application Server 6.10, you can also define central auto-reaction methods. The auto-reaction methods are not started in the system, in which the alert occurs, but rather in the central monitoring system. In this way, it is possible for reactions to events that occur in monitored components to be performed immediately in a central location.

If problems occur during the execution of auto-reaction methods, it can be useful to check the status of the auto-reaction methods. You can find out the definition and runtime status of an MTE by choosing Display Details (). This method is very time-consuming for obtaining an overview of the auto-reaction methods for the MTEs of an entire monitor. The technical view Status Autoreaction exists as an alternative for this purpose.

In this technical view, you can also manually start the auto-reaction method for any MTE to which an auto-reaction method is assigned. To do this, choose the relevant MTE by double clicking it. This is especially useful during test phases.

Note that when you start an auto-reaction method manually, it runs under your user name and therefore also under your authorizations. As the method runs under the SAPSYS user when it is started automatically, and this user has only very few authorizations, you can assume from a successful test with a manual start that the method will also run without problems during normal operation.

Procedure

To activate the Status Autoreaction technical view, follow the procedure below:

...

1. Choose CCMS ® Control/Monitoring ® Alert Monitor, or call transaction RZ20.

2. Expand the monitor set that contains the monitor that you require, and choose Load Monitor.

3. Choose Views ® Status Autoreaction. The alert tree now no longer displays the alert status and reported values, but information about the auto-reaction methods of the MTEs of the monitor.

Result

The view displays the following information for the active monitor about the auto-reaction methods that are assigned to the individual MTEs:

· Assigned auto-reaction method

· Type of the auto-reaction method; depending on the definition of the method, the following types are possible:

· Definition status of the method:

· Runtime status of the method:

· The time specification after the runtime status shows the time since which the method has been in this status.

· The color of the nodes is not passed upward in the alert monitoring tree. Monitoring objects and summary nodes therefore always have the color Green.

Data suppliers deliver values that are displayed in the Alert Monitor. They each belong to the individual system components and create monitoring objects that report values to the monitoring architecture. These values are displayed in the monitor sets.

It can be useful to check the status of the data collection methods if problems occur in the monitoring architecture. You can find out the most important information about the assigned data collection methods on one hand by choosing Properties, if you choose the data collection method in the Methods tab page by double clicking it. On the other hand, you can find out the definition and runtime status of the data collection method of an MTE by choosing Display Details ()

This method is very time-consuming for obtaining an overview of the data collection methods and their status for the MTEs of an entire monitor. The technical view Status Data Collector exists as an alternative for this purpose.

In this technical view, you can also manually start the data collection method for any MTE to which a data collection method is assigned. To do this, choose the relevant MTE by double clicking it. This is useful, for example during test phases or for MTEs for which you require the current value, even if it is not yet time for the next start of the method.

Note that when you start a data collection method manually, it runs under your user name and therefore also under your authorizations. As the method runs under the SAPSYS user when it is started automatically, and this user has only very few authorizations, you can assume from a successful test with a manual start that the method will also run without problems during normal operation.

Procedure

To activate the Status Data Collector technical view, follow the procedure below:

...

1. Choose CCMS ® Control/Monitoring ® Alert Monitor, or call transaction RZ20.

2. Expand the monitor set that contains the monitor that you require, and choose Load Monitor.

3. Choose Views ® Status Data Collector. The alert tree now no longer displays the alert status and reported values, but information about the data collection methods of the MTEs of the monitor.

Result

The view displays the following information about the data collection methods that are assigned to the individual MTEs of the monitor:

· Assigned data collection method: If the MTE is assigned an active data supplier, the system will display in the corresponding column, as the active data suppliers are not defined in the monitoring architecture

· Type of the data collection method; depending on the definition of the method, the following types are possible:

· Definition status of the method:

· Runtime status of the method:

The time specification after the runtime status shows the time since which the method has been in this status.

· Frequency of the method call in seconds (Cycle):

The color of the nodes is not passed upward in the alert monitoring tree. Monitoring objects and summary nodes therefore always have the color Green.

Use

The individual monitoring tree elements (MTEs) of the Alert Monitor are assigned methods. These methods determine the data collection of the MTEs (data collection methods) and the possible reactions to an alert in the MTE (auto-reaction and analysis methods). You can find out the assigned methods by selecting an MTE and choosing Properties. This method is very time-consuming for obtaining an overview of the assigned methods for the MTEs of an entire monitor. The technical view Method Allocation exists as an alternative for this purpose. This view displays the method assignments for the MTEs of the entire monitor:

· Assigned data collection method: If the MTE is assigned an active data supplier, the system will display in the corresponding column, as the active data suppliers are not defined in the monitoring architecture

· Assigned auto-reaction method

· Assigned analysis method

· The nodes are always colored green in the technical view Method Allocation; as it contains no alert information.

· Summary nodes or monitoring objects can always be assigned methods; these assignments only take effect for the subordinate monitoring attributes, which can inherit their method assignment from the superordinate nodes.

· If no analysis or auto-reaction method is assigned to the MTE, is displayed in the corresponding column here.

Procedure

To activate the Central Method Allocation technical view, follow the procedure below:

...

1. Choose CCMS ® Control/Monitoring ® Alert Monitor, or call transaction RZ20.

2. Expand the monitor set that contains the monitor that you require, and choose Load Monitor.

3. Choose Views ® Method Allocation. The alert tree now no longer displays the alert status and reported values, but information about the methods assigned to the MTEs of the monitor.

The enqueue service allows ABAP applications to lock data so that only they can use it. The locking of the data avoids parallel changes to the data, which would lead to data inconsistency. For more information, see The SAP Lock Concept (BC-CST-EQ).

There are two different trees in the monitoring infrastructure for monitoring the enqueue service:

· Enqueue monitor in the SAP CCMS Monitor Templates monitor set

This monitor includes a large number (see below) of monitoring values for the enqueue service. Since the monitor is supplied with values by an ABAP data collection method, the values are updated every five minutes.

· Enqueue subtree in the R3Services subtree of the Entire System Monitor (SAP CCMS Monitor Templates monitor set)

This subtree includes only the most important monitoring values for the enqueue service. Since the data is supplied by an active data supplier directly from the kernel, current data is reported immediately in the monitoring infrastructure.

Enqueue Monitor

Features

The monitor contains the following monitoring tree elements (MTEs):

Activities

To start the monitor, follow the procedure below:

...

1. Start the Alert Monitor using transaction RZ20 or choose CCMS ® Control/Monitoring ® Alert Monitor.

2. On the CCMS Monitor Sets screen, expand the SAP CCMS Monitor Templates set.

3. Start the Enqueue Server monitor from the list by double-clicking it.

Enqueue Subtree in R3Services

Features

The subtree contains the following MTEs:

Activities

To display the subtree, proceed as follows:

...

1. Start the Alert Monitor using transaction RZ20 or choose CCMS ® Control/Monitoring ® Alert Monitor.

2. On the CCMS Monitor Sets screen, expand the SAP CCMS Monitor Templates set.

3. Start the Entire System monitor from the list by double-clicking it, and expand the monitoring tree along the path ® ApplicationServer ® ® R3Services ® Enqueue.