You can use the CCMSPING agent to monitor the availability of your SAP system landscape (see Availability Monitoring with CCMSPING). Normally, you only require one CCMSPING agent to monitor your entire system landscape. However, you can also use multiple CCMSPING agents. This can have the following advantages, for example:
· You can extend the availability monitoring to include accessibility monitoring. In this way, you can monitor the connections to the systems in addition to the actual monitoring of the systems.
In this scenario, it can be useful that one system is monitored by multiple CCMSPING agents, to check the accessibility of the system from various points. You can do this by combining these CCMSPING agents into an agent group, and assigning this agent group the system as the responsible CCMSPING.
· You can configure various CCMSPING agents different (such as setting the frequency of the availability monitoring differently; see Changing Technical Settings of CCMSPING), to fulfill different requirements for availability monitoring of different systems.
· In distributed landscapes, it is possible that the response times of the RFC calls, with which the logon checks for an instance are performed, become too large. In this case, assign CCMSPING agents for which the connection to the systems to be monitored is sufficiently quick in each case.
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.
You can only use multiple CCMSPING agents, if you install all CCMSPING agents with the –push option (see Installing Availability Agent CCMSPING). Without this option, the registration of an additional CCMSPING might overwrite existing registrations in CEN.
If you want to monitor the availability of certain systems using multiple CCMSPING agents, you need to combine the different CCMSPING agents into an agent group and then assign this group to the relevant systems as the responsible CCMSPING.
To combine multiple CCMSPING agents into an agent group, proceed as follows:
1. The system is displaying the Configure Availability and Performance Overview screen. Choose CCMSPING → Manage CCMSPING Groups.
2. To assign a CCMSPING agent to an agent group, choose the (Add Group Entry) button, and specify the name of the desired group on the Add Entry for Agent Group screen in the Group Name field (you can also create a new agent group in this way). Then enter the destination of the desired agent in the CCMSPING Agent field, and choose (Continue).
3. To delete the assignment of an agent to an agent group, select the desired assignment and choose (Delete Group Entry).
If you want to delete the last assignment of an agent to a particular agent group that is still assigned to systems as the Responsible CCMSPING, the system displays a corresponding warning.
The system is displaying the Configure Availability and Performance Overview screen. To display the CCMSPING agent or agent group responsible for your monitored systems, proceed as follows:
Choose the button Views → System Info View. The RFC destination of the responsible CCMSPING or the responsible agent group in each case is shown in the corresponding row. The destination has the following naming convention:
By default, <instance number> is 00.
To change the CCMSPING agent responsible for monitored systems, proceed as follows:
1. The system is displaying the Configure Availability and Performance Overview screen. 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. Choose CCMSPING → Change Responsible CCMSPING.
3. Choose the desired CCMSPING for the selected systems. The list of CCMSPING agents displayed in the input help contains the RFC destinations of all CCMSPING agents that are registered with this system, and also all agent groups that you have created.
4. Confirm your selection and save your changes.
You can also change the responsible CCMSPING on the Connection Data and Monitoring Options screen (see Creating and Changing Monitoring Rules).
Availability Monitoring with CCMSPING start page