Show TOC

Monitoring Agents in the Topology DisplayLocate this document in the navigation structure

Use

Use this function to obtain an overview of the SAP NetWeaver management agents and the CCMS agents that are registered for your local system. There are different SAP NetWeaver management agents, which are listed in the three tab pages.

Tab Page Agent Type Meaning

Agents for SAP System <SID>

Host Agent

Monitors components on which there is not an active SAP instance

Agents for Remote SAP Systems

Instance Agent

Monitors SAP instances (ABAP, Java, or TREX)

CCMSPING Destinations

CCMSPING

Monitors the availability of systems and instances (more information: Availability Monitoring with CCMSPING)

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

Features

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

Column Meaning

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.

Note

Up to SAP NetWeaver 2004s, the ABAP and Java stacks of an instance use different monitoring segments. To differentiate between these segments, the Java segment has the suffix _X, such as SAP_CCMS_HostA_ABC_33_X. In the case of a dual-stack system with the current release, on the other hand, the ABAP and Java stacks of a system use the same segment.

Destination

Destination of the monitoring segment; in the case of CCMS agents, this is an RFC destination (highlighted in blue), in the case of SAP NetWeaver management agents, this is a logical Web service port (highlighted in yellow)

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 a call fails (for example, in the case of the Test Connection command), the system displays COMM.FAIL. After a successful call, the system sets the status to ONLINE again.

Responsible Server

Instance that performs the internal administration tasks to control the 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 Two Central Monitoring Systems. This shows that the agent is registered with the local system, but another system is the primary monitoring system. Note that directly after the registration of an agent, the entry REMOTE SYSTEM is only displayed after the first run of a synchronization job, after a maximum of an hour.

Changed By Changed On Changed At

These columns have identical meanings to those with the same names when Displaying Monitored Systems in the Topology Display.

J2EE Customizing Destination

This column contains an RFC destination to the Java instance 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 Java instance. This column is therefore only relevant for instance agents that monitor Java instances; for all other agents, n/a is entered here.

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

Column Meaning

Comm. Prio/Comm.Type/Version

These columns have identical meanings to those with the same names when Displaying Monitored Systems in the Topology Display.

Note

On the CCMSPING Destinations tab page, the system shows only the column Destination. This column contains the RFC destinations of the CCMSPING availability agents that are registered with the local system. The destination has the naming convention CCMSPING.<CCMSPING host>.<CCMSPING instance number> (see Installing CCMSPING Availability Agent).

Activities

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

Command Explanation

Test Connection

This command performs a call to the selected agent and displays the result. If the 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 agent in the relevant tables, such as the destinations and the entries in the System Component Repository. The relevant remote system is therefore no longer monitored by the local system.

Note

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 agents in your IT landscape

Agent Registration

Specifies the central monitoring system with which the agent is registered

Adopt Agent (only in change mode)

Defines the local system as the primary monitoring system for the selected 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 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.

Note

The following functions are available to you on the CCMSPING Destinations tab page:

  • Test Connection
  • Working Directory of the Agent
  • Deregister Agent
  • Agent Self-Monitoring