Functional Principle of the CCMS Agents 

The runtime information for the monitoring objects is stored in monitoring segments. A CCMS agent always uses exactly one monitoring segment that is either in its local process memory or in the local shared memory.

·        SAPCCMSR

This agent monitors components on which there is no active SAP instance (such as log files, TREX, stand-alone databases, or operating system components). SAPCCMSRis closely connected with the monitoring central monitoring system.

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 must have a release status of at least SAP Basis 4.6B.

With SAPCCMSR with the Option j2ee, you can monitor Java instances as of SAP Web AS 6.30.

 

·        SAPCCM4X

This agent improves the monitoring of ABAP instances with SAP Basis 4.X or higher. The central monitoring system must have a release status of at least SAP Basis 4.6C. This agent provides an alternative connection route to the monitoring information in the shared memory of an ABAP instance. As this alternative connection method does not require a free work process, the access method is independent of error states of the SAP instance and is therefore more robust.

Systems as of SAP Basis 4.0 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. After its installation, the SAPCCM4X agent attempts to attach itself to and to work with this monitoring segment in shared memory when it is started.

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

The central monitoring system automatically first attempts to read data from the monitored system through the RFC destination of the CCMS agent. If the agent is not active, the system reads the monitoring data from the monitored SAP instance using the standard RFC, as previously (for more information, see SAP Note 322075).

·        SAPCM3X

This agent allows the monitoring of SAP instances with SAP Basis 3.X through the CCMS monitoring architecture. These systems do not have their own CCMS monitoring architecture runtime environment. SAPCM3X therefore works always works with a monitoring segment that it creates in its main memory (for more information, see SAP Note 308061).

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. To do this, call transaction RZ20, select a node in the desired monitor, choose Properties and, on the Methods tab page, correct the value for Start the data collection method every.

The maximum frequency of this query depends on whether the underlying program is an ABAP program or a C program. In the case of ABAP programs, the maximum frequency is five minutes, while the maximum frequency for C programs (and therefore for CCMS agents) is one minute.

·        As an RFC client, it independently sends alerts and values for the monitoring attributes to the central monitoring SAP System (push technology). This data is then stored in a cache there to allow the system to display it more quickly or triggers central auto-reaction methods there. This improves performance as the central monitoring system then no longer needs to periodically query the agents.

The central monitoring system must have a release status of at least SAP Web AS 6.10 for automatic reporting of alerts. As of this release, activation of the push technology is mandatory. As of SAP Web AS 6.20, the agents also automatically report monitoring attribute values.

All CCMS agents can process several tasks simultaneously (multi-thread procedure). This means that they can simultaneously:

·        Automatically collect data

·        Process requests as an RFC server

·        Send data to the central system as an RFC client

 CCMS Agents start page