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

This monitor displays a section of the Operating System Monitor, which displays all of the values collected by the operating system collector SAPOSCOL. You can use this monitor to monitor application servers and host systems of your choice and to check whether there is still enough free disk space available. The values are collected by the operating system collector SAPOSCOL. You can also monitor this data with the operating system monitor, which is assigned as the analysis method for most of the nodes of this monitor.

Prerequisites

To be able to display operating system data for a particular server with this monitor, the operating system collector SAPOSCOL must be installed on that server (see Installing the Operating System Collector SAPOSCOL).

Features

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

You can explicitly exclude file systems from the operating system collector monitoring. For more information, see Monitoring Operating System Data with CCMS Agents.

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 Filesystems monitor from the list by double clicking it.

You can use the monitoring architecture to monitor selected jobs and to display problems as alerts (see Monitoring Jobs with the Alert Monitor). This job monitoring is deactivated by default; activation is described in Activating Monitoring of Jobs with the Alert Monitor.

After activation, the data is available in the context Background, Background Job Monitoring subtree. For the monitoring, it is useful to define your own monitor or to extend a monitor definition of your own to display the data. The monitor definition and the monitor produced from it are described here.

Prerequisites

You can define a rule-based or a static monitor to display data. For basic information about this, see Creating and Changing Monitors. For a rule-based monitor, the definition must contain a rule CCMS_GET_MTE_BY_CLASS with Job_Monitoring as the MTE class:

If you are using a static monitor, choose the context Background ® Background Job Monitoring for the desired system:

Features

With the definition above, the monitor created has the following structure. Here, the job SCHEDULED_JOB1 and all jobs whose names begin with JOB_EXAMPLE are to be monitored. A subtree is created for every name pattern for a monitored job (job chain):

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

Customizing Alert Generation

· Runtime, Delay and Delay + Runtime

Threshold values are already assigned to these performance attributes by default, so that an alert is generated as of a defined runtime or delay. To change the threshold value, select the desired performance attribute and choose Properties (see Changing Properties and Method Assignments). Ensure that you choose Edit ® Properties ® Use for individual MTE so that you do not change the threshold values for the other monitored jobs.

· History and Log of Current Job

By default, these log attributes always have the color green. However, you can also assign a yellow or red alert to particular messages of the attribute. To do this, choose Properties and specify the class and ID of the desired message on the Filter tab page.

To determine this data for a message of the log attribute, follow the procedure below:

i. Select the desired log attribute and choose the Display Details button ().

ii. The Monitoring Attributes - Detail Data screen appears. To do this, select any row from the list of messages and choose Current Display Variant ().

iii. The Change Layout screen appears. Ensure that the fields for message class (MsgKlasse) and the message ID (MsgId) are displayed, and accept the changes.

iv. The class and ID of the message are now displayed in the list.

Use

You can customize the availability monitoring with CCMSPING for ABAP and Java systems in a number of ways. The following functions are available:

· You can activate and deactivate availability monitoring for particular systems

· You can define the type of availability monitoring for application servers and logon groups of an SAP system. When doing so, you can both create and change monitoring rules, in accordance with which the servers and groups of the system are monitored, and change the monitoring settings of servers and groups individually.

Logon groups exist only for ABAP application servers.

· You can activate and deactivate availability monitoring for systems groups. You can also decide whether these settings should also automatically apply for systems that are later added to the relevant system group (see Monitoring System Groups with CCMSPING).

· If you have installed multiple CCMSPING agents, you can decide which CCMSPING is responsible for the monitoring of a system. This is, for example, useful for the monitoring of distributed system landscapes (see Using Multiple CCMSPING Agents).

· You can select time periods in which the availability of selected systems is not checked (see Creating and Changing a Monitoring Pause)

· You can add new systems to the list of systems that can be checked using availability monitoring.

Prerequisites

You have performed the Installation of the Availability Agent CCMSPING.

Process Flow

...

1. Choose CCMS ® Configuration ® Alert Monitor, or call transaction RZ21.

2. The Monitoring: Properties and Methods screen appears. Choose Technical Infrastructure ® Availability Monitoring ® Configure CCMSPING Monitoring.

3. The Configure Availability and Performance Overview screen appears. The screen shows monitored and unmonitored systems in two lists, where you can display for the monitoring of the monitoring systems by expanding the subtree for the corresponding system:

The configuration of the availability and performance overview is also set as the analysis method for the nodes of the Availability and Performance Overview Monitor. This means that you can display this screen by double-clicking a node in this monitor.

Displaying the Monitoring and System Data

There are various views available on the Configure Availability and Performance Overview screen, with which you can display information about the monitored systems and their application servers and logon groups. To activate a view, choose the Views button, and then one of the following buttons:

Activities

Changing the Monitoring of Systems

To change the monitoring of systems, select the desired systems on the Configure Availability and Performance Overview screen by selecting the folder icon of the relevant systems. The following functions are then available to you:

You can also activate and deactivate system monitoring by moving selected systems to the desired list by Drag&Drop.

Monitoring System Groups

You can combine systems into system groups (see System Groups in the Alert Monitor), where one system can belong to multiple system groups. In this way, you can, for example, organize systems into system groups by their function (development, quality assurance, production), their release status, or their geographic location.

In large IT environments, it can greatly simplify the configuration of availability monitoring, if you can, for example, monitor all systems in a system group with one command. You can also set up the monitoring so that changes to the systems that belong to a system group automatically cause a change in the availability monitoring of the relevant systems.

For more information about monitoring system groups, see Monitoring System Groups with CCMSPING.

Changing the Monitoring of Application Servers and Logon Groups

You can change the monitoring settings for servers and groups on the Configure Availability and Performance Overview by selecting the relevant indicator in the ALV Tree Control.

Add New Systems to the List of ABAP Systems that Can Be Monitored

On the Configure Availability and Performance Overview screen, choose Load System List (). If the desired ABAP system does not appear on the list, add the system to it manually (see Add Systems to the Availability Monitoring Manually).

The SAPMSG.INI file, which is also used for functions of SAPLOGON, is uploaded from the front end for the system list. It does not contain any standalone Java systems.

Changing Technical Settings of the Availability Agent CCMSPING

You can also change technical settings of the registered CCMSPING availability agents, such as the frequency of the monitoring, or the timeouts that define how long CCMSPING waits for a response from the message servers and the application servers (see Changing the Monitoring Frequency and Timeouts of CCMSPING).

Result

You have customized the availability monitoring to your requirements. Use the Availability and Performance Overview Monitor from the SAP CCMS Monitor Templates monitor set to perform availability monitoring.

Availability Monitoring with CCMSPING start page