Functions of the CCMS Agents (SAP Library

Functions of the CCMS Agents

Monitoring Segments

The runtime information for the monitoring objects is stored in monitoring segments. A CCMS Agent always uses exactly one monitoring segment, which is either in its local process memory or in the local shared memory. The various CCMS agents behave as follows:

SAPCCMSR

After its installation, the CCMS agent SAPCCMSR attempts to attach itself to a monitoring segment in shared memory when it is started. If this segment does not yet exist, the agent creates it. SAPCCMSR always works in a shared memory segment that is independent of running SAP systems. The central monitoring system requires at least SAP Basis 4.6B.

Note

By default, the size of the shared memory segment is 16,000,000 bytes. You can change the size of the segment by setting profile parameter
alert/MONI_SEGM_SIZE (see also SAP Note 135503).

SAPCCM4X

The CCMS agent SAPCCM4X monitors SAP systems with an SAP R/3 Basis Release 4.0B or higher. The central monitoring system requires at least SAP Basis 4.6C. These systems do not have their own CCMS monitoring architecture runtime environment. This means that they have their own monitoring segment in the shared memory area of the running system.

Note

Access to this monitoring segment is only possible with UNIX using the user <SID>adm , and with Windows NT using the user SAPService<SID>.

After its installation, the CCMS agent SAPCCM4X attempts to attach itself to a monitoring segment in shared memory when it is started, and to work with this segment.

If this segment does not exist (that is, when the monitored system is not running), the agent does not create it, in order to avoid interfering with the shared memory management of the restarting system. In this case, the SAPCCM4X agent works with a monitoring segment that it creates in its process memory and whose contents it synchronizes with the monitored system. SAPCCM4X constantly checks if the monitored system is active again and, when it is, works with the monitoring segment in the shared memory again after synchronization.

SAPCM3X

The CCMS agent SAPCM3X monitors SAP systems with an SAP R/3 Basis Release lower than 4.0B. These systems do not have their own CCMS monitoring architecture runtime environment. The SAPCM3X agent therefore always works with a monitoring segment that it creates in its main memory.

Communication

A CCMS agent communicates with the central, monitoring system using RFC.

As an RFC server, it provides access to the data in the monitoring segment. This access is, for example, used in transaction RZ20. The agent automatically creates the local configuration files and the RFC destination in the central system during its registration. You can set the frequency of the query by the monitoring architecture in the Alert Monitor (see: Frequency of Method Execution):

As an RFC client, it independently sends data to the central, monitoring SAP system. This data is then stored in a cache to allow quick display, or triggers central auto reaction methods.

Features

Agents can perform the same functions (reading and writing) with the monitoring segment that are contained in the ABAP interface of the SALI and SALR function groups in SAP R/3.

The following components are also already integrated into the agents:

Log file agent for generic checking of log files and reporting of problems in the monitoring architecture
Access to remote data of the SAPOSCOL operating system collector (used, for example, by transaction ST06 and OS07); it is no longer necessary to install RFCOSCOL

Note