Show TOC

 Creating and Changing Monitoring RulesLocate this document in the navigation structure


You can create monitoring rules in the configuration of the availability monitoring with CCMSPING. You define the type of monitoring for the relevant system in these rules. You have the following options:

  • Monitoring the application servers:
    • Ping Monitoring

      With this type of monitoring, the availability agent queries the message server of the corresponding system as to whether the application server is reported as active. It does not perform a check at the monitored server itself to see whether, for example, it is possible to log on. This monitoring is possible for both Java and ABAP application servers, since CCMSPING can communicate with both the ABAP and Java message servers, depending on the communication settings of the system.

      Important performance attributes from the dialog service of the server are also reported in availability monitoring for ABAP application servers (see Availability and Performance Overview Monitor). The prerequisite for this is the existence of logon groups in the corresponding system.

    • Check Logon

      With this monitoring type, the monitoring architecture performs an RFC call in the relevant server. Although no actual logon is performed, you can, however, determine whether it is possible to log on ‑ since the RFC call requires a free dialog work process, in the same way as a user logging on does. This method also checks whether the database of the monitored system is functioning and is connected to the system. This monitoring is only possible for ABAP application servers.


      This type of RFC call is not subject to the quotas that you can set with the various profile parameters with the prefix rdisp/rfc to prevent overloading due to RFC calls.

  • Monitoring the logon groups

    You can check whether it is possible to log on to the currently selected ABAP application server of a logon group (see Logon Load Balancing). This function uses the same technique to do this as Check Logon.


This procedure is part of the Configuring Availability Monitoring process. It is therefore a prerequisite that you have already performed the part of the process that is to be performed before this procedure.


The system is displaying the Configure Availability and Performance Overview screen. To create or change a monitoring rule for one or more systems, follow the procedure below:

  1. Select the desired systems by choosing the folder symbol for the corresponding systems.

    Note that a system is only correctly selected when the entire line is highlighted:

  2. Proceed as follows, depending on whether the desired systems are already monitored:
    • To create an availability rule for a system that has not been monitored until now, choose  Monitoring → Activate System Monitoring in the Unmonitored Systems subscreen. This activates the monitoring for this system; confirm the relevant query.

      To assign an identical monitoring rule to multiple systems that were not previously monitored, select these systems, and choose  Monitoring → Define Uniform Monitoring.

    • To change the availability rule for a monitored system, choose  Monitoring → Change Connection/Options in the Monitored Systems subscreen.

      To assign an identical monitoring rule to multiple monitored systems, select these systems, and choose  Monitoring → Use Uniform System Options.

  3. The Connection Data and Monitoring Options screen appears. The screen has the following structure:

    Make the following entries in this screen:

    Group Box Meaning

    System and Connection Data

    Information about the corresponding system. For more information, see Add Systems to the Availability Monitoring Manually)

    Monitoring Options for Application Servers

    Settings for monitoring application servers (see above); you can choose the following radio buttons:

    • No monitoring of application servers; only the system is monitored for its availability; if a server was previously monitored, this setting is deleted
    • Monitor only selected application servers; with this option, only the servers that you manually select in the Group/Instance View are monitored.
    • Automatically Add New Application Servers to Monitoring; with this option, the servers that currently exist are not monitored (which you can change manually in the Group/Instance View); if the rule is active, newly added servers are automatically monitored
    • Monitor All Application Servers; with this option, all servers, including new servers added later are monitored.

    Monitoring Options for Logon Groups

    You can set whether logon groups are to be monitored; you can specify, in the same way as with the monitoring of application servers, whether newly added groups should automatically be included in the monitoring.

    Destination of Responsible CCMSPING

    If you have installed multiple CCMSPING agents, you can determine here which CCMSPING is responsible for the monitoring of this system (see Using Multiple CCMSPING Agents).

  4. Save your data.

You have created or changed a monitoring rule for the selected systems, on the basis of which the corresponding systems will be monitored. To further refine monitoring, for example, to change the monitoring of individual application servers or logon groups, follow the instructions in Changing Monitoring Settings for Servers and Groups.

 Availability Monitoring with CCMSPING start page