When monitoring availability with CCMSPING, you can have the connections between CCMSPING and the message servers of the monitored systems created using SAProuter. This is useful, for example, if CCMSPING and the monitored systems are in different areas of your network.
To allow the processing of the communication between CCMSPING and the message server, you need to perform two configuration steps:
You must have performed the installation of SAProuter.
The connection from the CCMSPING agent through SAProuter works for monitored ABAP systems as of the creation of this availability monitoring. For monitored Java systems, you require an agent as of Patch Collection 2005/7.
/H/<host name>/S/<port>
<host name> is the name of the host on which SAProuter is running, <port> is the number of the SAProuter port (by default, 3299)
CCMSPING calls the message servers of the correspondingly configured monitored systems using SAProuter. So that a route of this type is allowed by SAProuter, there needs to be a corresponding entry in the Router Permission Table saprouttab. To set this authorization, proceed as follows:
Allow a connection with the following entry:
S <CCMSPING host> <message server host> <message server port>
The connection is performed using RFC; since this is an SAP protocol, you can, for example, allow all connections with S * * *.
Allow a connection with the following entry:
P <CCMSPING host> <message server host> <message server port>
Since the Java message server communicates using an HTTP connection, you need to permit the connections with the option P. In contrast to connections using an SAP protocol (see above), you cannot use the wildcard character (*) for a port in this case. This means that you need to explicitly release every message server port used (by default, 8100 + <instance number of the message server>). The wildcard character is permitted for the message server host.
Availability Monitoring with CCMSPING start page