Monitoring CCMS Agents in the Topology Display (SAP Library

Monitoring CCMS Agents in the Topology Display

Use

Use this function to obtain an overview of the CCMS Agents that are registered for your local system. CCMS agents are independent processes with an interface through RFC to a central monitoring system and an interface to the shared memory. They provide a connection method, in addition to a defined ABAP interface, between the monitored and monitoring systems.

The advantages of CCMS agents lie in their universal usability, as agents allow the inclusion of both SAP components without ABAP interfaces and non-SAP components. The method of access for monitoring is also independent of any error status of the monitored system, and is better from a performance point of view due to the use of push technology.

There are different CCMS agents, which are listed in the three tab pages.

Tab Page	Agent	Description
Agents for SAP System <SID>	SAPCCMSR	Monitors components on which there is not an active SAP instance
Agents for Remote SAP Systems	SAPCCM4X	Monitors SAP systems with SAP Basis 4.X
Agents for Remote SAP Systems	SAPCCMSR –j2ee	Monitors J2EE Engines
Agents for 3.x SAP Systems	SAPCM3X	Monitors SAP systems with SAP Basis 3.X using the CCMS monitoring architecture

For more information about how you can start the topology display, see Structure link Calling the Technical Topology Display.

Features

By default, the system displays the following columns in the tab pages for the CCMS agents:

Column	Description
System	System ID of the monitored system (this column is only displayed for agents for remote SAP systems)
Segment Name	Name of the monitoring segment with which the agent connects; it has the name structure SAP_CCMS_<Name of the SAP Instance> or SAP_CCMS_<Host Name> for agents for the local system. If you are monitoring J2EE Engines using SAPCCMSR with Option j2ee, the normal naming convention would be for both the ABAP and the Java segment of the instance of a SAP Web Application Server to have the same segment name. To avoid this, the Java segment has the suffix _X, such as SAP_CCMS_HostA_ABC_33_X.
Destination	RFC destination of the monitoring segment
Comm.Status or Segment Status	Status of the monitoring segment or communication status from the point of view of the local system. The possibilities for status are: · ONLINE · OFFLINE · SHUTDOWN · COMM.FAIL If an RFC call fails (for example, in the case of the Test Connection command), the system displays COMM.FAIL. After a successful RFC call, the system sets the status to ONLINE again.
Responsible Server	Instance that performs the internal administration tasks to control the CCMS agent. It is first the instance with which the agent registered. In running operation, another instance automatically takes over this task if the original instance is no longer available. This column can also have the entry REMOTE SYSTEM for a Registration with Multiple Central Monitoring Systems. This shows that the CCMS agent is registered with the local system, but another system is the primary monitoring system. Note that directly after the registration of a CCMS agent, the entry REMOTE SYSTEM is only displayed after the first run of a synchronization job after a maximum of an hour. With the CCMS agent SAPCCM4X (tab page Agents for Remote SAP Systems), these administrative tasks are performed instance-independently by jobs. Therefore, the column title is Responsible System in this case.
Changed By Changed On Changed At	This columns have identical meanings as those with the same names when Displaying Monitored Systems in the Topology Display.
J2EE Customizing Destination	This column contains an RFC destination to the J2EE Engine that the agent is monitoring. This destination is used to transfer property changes for nodes of this agent from the Alert Monitor directly to the J2EE Engine (see Creating a Customizing Destination for SAPCCMSR -j2ee). This column is only relevant for the agent SAPCCMSR with the j2ee Option; for all other agents, n/a is entered here.

You can also show the following columns by choosing the Change Layout... button for the Structure link ALV Grid Control:

Column	Description
Comm.Prio Comm.Type Version	This columns have identical meanings as those with the same names when Displaying Monitored Systems in the Topology Display.

Activities

In addition to the purely display functions, the following commands are also available to you as pushbuttons in the ALV Grid Control. These commands are only available for the local system.

Command	Explanation
Test Connection	This command performs an RFC call to the selected agent and displays the result. If the RFC call is not successful, the system sets the status to SHUTDOWN; if the call is successful, the system sets the status to ONLINE.
Working Directory of the Agent	You can display all files in the working directory of the agent. To do this, select the desired agent and then choose this pushbutton. The system displays an ALV Grid Control with the files from the directory. To display the contents of a file, choose the file by double clicking it.
Deregister Agent	Deletes all entries for the selected CCMS agent in the relevant tables, such as the RFC destinations and the entries in the System Component Repository. This function should not replace the deregistration using the agent itself (see Controlling CCMS Agents), since, for example, Deregister Agent does not stop the agent. Instead, use this function primarily to remove incorrect entries and inconsistencies after changes to the system landscape. This command is only available in change mode, which you start by choosing the Display « Change button ().
Self-monitoring of the Agents	Switches directly to the Self-Monitoring CCMS Agents Monitor; this monitor contains the most important data for monitoring the CCMS agents in your IT landscape
Agent Registration	Specifies the central monitoring system with which the CCMS agent is registered
Adopt Agent (only in change mode)	Defines the local system as the primary monitoring system for the selected CCMS agent; the previous primary system then becomes the secondary system
Adopt All Agents (only in change mode)	Defines the local system as the primary monitoring system for all CCMS agents that are registered with the local system. The previous primary systems then become secondary systems (the button is in the toolbar at the top of the screen, since this command applies for all agents, irrespective of the selected tab page)
Change Communication Status/ Segment Status (only in change mode)	If you no longer want to display the data from the agent in the monitoring architecture, choose OFFLINE. It remains in this status until you set it to ONLINE again. Do not set COMM.FAIL or SHUTDOWN manually.

Note

The buttons Agent Registration, Adopt Agent, and Adopt All Agents are only displayed if there are agents that are registered with multiple central monitoring systems.

You should also ensure that the functions to switch the primary system are performed in the agent itself. This can take a few seconds. Then refresh the display until the changes are visible in the display.