Start of Content Area

Function documentation Central Monitoring with SAP NetWeaver Management Agents  Locate the document in its SAP Library structure


The SAP NetWeaver management agent sapstartsrv (more information: Administration/Monitoring of SAP Components with sapstartsrv) contains the functionality for different central monitoring functions. The functions of the CCMS agents are integrated into sapstartsrv as a static library for this purpose; the CCMS agents therefore no longer exist as standalone executables as of SAP NetWeaver 7.0 EhP2.

The monitoring functions are started in a separate thread within sapstartsrv. This thread connects to the monitoring segment in the shared memory of the monitored instance. Applications can access the monitoring functions of sapstartsrv through a Web service interface. This interface replaces the RFC server part of the CCMS agent.

An application (usually an ABAP or dual-stack system) can register as a central monitoring system (CEN). The registration is performed using a protected Web service. During the registration, the caller sends sapstartsrv information about the CEN and the logon data for the CSMREG user.

Types of Agents

Depending on the type of monitored component, there are different types of SAP NetWeaver management agents or CCMS agents:

Monitored Component


      AS ABAP

      AS Java



(as of SAP NetWeaver 7.0 EhP2 in each case)

Instance agent; an instance agent runs for each monitored instance


      Non-SAP components

      J2EE Engine SAP Web AS 6.20

Host agent; one host agent runs for each monitored hosts (including hosts on which one or more instance agent is running)

      AS ABAP up to SAP NetWeaver 7.0 EhP1


      AS Java up to SAP NetWeaver 7.0 EhP1

CCMS agent SAPCCMSR -j2ee


For more information about when you still need to use CCMS agents, see CCMS Agents: Central Monitoring for Components up to SAP NetWeaver 7.0..


An SAP NetWeaver management agent communicates with CEN in the following way:

      As a Web service, it provides access to the data in the monitoring segment. This access is, for example, used in transaction RZ20 or in the NetWeaver Administrator.

      As an RFC client, it independently sends alerts and values for the monitoring attributes to the CEN (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, since CEN then no longer needs to periodically query the agents.

This graphic is explained in the accompanying text


You do not need to install the host and instance agents separately with SAP NetWeaver components of the current release, since these are already installed as part of the installation of the component.

You only need to download and install the host agent yourself in the case of hosts with no SAP NetWeaver components (see Downloading and Installing Package SAPHOSTAGENT).


The monitored component must be registered with CEN (see Registering SAP NetWeaver Components and Hosts in CEN).

This graphic is explained in the accompanying text Infrastructure of the SAP NetWeaver Management Agents Start Page


End of Content Area