Show TOC

SAP System Agents 

Use

Release 4.6C of the SAP System is delivered with an agent system that enables you to check the availability of and access data on inactive instances.

There are three new agents:

This agent makes it possible to monitor SAP Release 3.0 and 3.1 Systems with the monitoring architecture in R/3 Release 4.x. You can monitor basic information on Release 3.x Systems from the alert monitor (Transaction RZ20) in a Release 4.x System, such as
This is a read agent that is used to access SAP Release 4.x instances externally. It is the second communication path in a monitored instance. The agent provides access to data when the SAP System or instance cannot be accessed directly.
The instance supplies exclusively the shared memory area that is relevant for alerts. This means that performance and alert data can be accessed, even if the instance is down and, therefore, the monitoring architecture is not available.
This agent checks the availability of SAP Systems at system level as well as at instance level by pinging the mesage server in the relevant system. The agent is responsible for the display and maintenance of the monitored system (by specifying the relevant message server and possibly the route as well). This occurs centrally in the CCMS of the central system. The ccmsping agent needs to be running on only one server in the system group.

Effects on System Administration

There is no special maintenance transaction for the ccmsping agent. Instead you maintain it using Transaction SE16.

The three agents are only available for the NT and UNIX operating systems, and not for AS400 or OS390.

See also

For more information on how to monitor Release 3.x Systems, see the 4.6C online documentation and the read-me text at the following address: ftp://sapservx/general/misc/ccms-ma/3x-monitoring/readme.txt.