CCMS Monitor for Self-Monitoring of the Process Monitoring 

Definition

The CCMS Alert Monitor is used by Process Monitoring for self-monitoring. If internal errors occur in Process Monitoring, these trigger alerts in the CCMS. Serious error messages are also displayed on the tab page ’Error Messages’, so that users do not have to jump to the CCMS. This is the recommended procedure. You can display this tab page by choosing Settings →Error Messages, or by clicking the information icon on the Process Monitoring initial screen.

You can find technical details in the CCMS Alert Monitor (transaction RZ20) in the monitor PMI Self-Monitoring in the monitor collection SAP Process Monitoring Infrastructure. This monitor is delivered as standard to be used for self-monitoring of Process Monitoring. To be able to use the information contained within this data as much as possible, however, you should have some knowledge of how to use the CCMS Alert Monitor, as well as knowledge of the Process Monitoring Infrastructure (PMI), which forms the basis of Process Monitoring. In contrast to the Process Monitoring administration user interface, the CCMS also displays alerts for processes that are no longer monitored actively. The following describes the structure of the CCMS monitor for Process Monitoring. You are also informed about which alerts are of particular importance.

 

Structure

The CCMS monitor tree for Process Monitoring is structured as follows:

The most important points concerning the monitor are described below:

●      Under PMI Transport, particular attention must be paid to exceptions and destinations that cannot be reached. The latter may actually be normal for PI, because a PI adapter was shut down, for example.

●      Under Reorganization you can find technical information about the reorganization activities together with potential problems. The reorganization entries are automatically scheduled and descheduled by the PMI.

●      Under PMI Assembler, no assembler jobs should run if monitoring has been deactivated for the process type. Otherwise the job must be descheduled using transaction SM37.

You must only deschedule jobs after consulting SAP Support, or if you have previous experience in such things.

●      Under PMI Storage you can find the application tables of the Process Monitoring. This is where you can observe the table growth and check whether it is too much.

●      Make sure under PMI Agents that the signatures, that is the configurations, are correct and that the destinations can be reached. 

●      PMI Java Service displays the availability of the PMI Service in the J2EE Engine. The PMI Service is responsible for sending data from the PMI Java agents in the J2EE Engine to the ABAP system. Details about the way in which this data reaches the PMI central system is described in the section How PMI Works. The availability is measured using the Generic Request and Message Generator (GRMG), which requests the PMI Service status at regular intervals. For the node to be activated, GRMG Customizing for the PMI Service must be performed in the J2EE Engine. For more information about this, refer to Enabling the Availability Monitoring of the PMI Service.

 

 Process Monitoring Display and Administration