Show TOC

Component documentationConnection Monitoring

 

You can use connection monitoring to monitor the status of RFC connections and therefore the connections between technical systems. In this way, you can monitor the prerequisites for the correct functioning of many applications that are distributed on different technical systems, and which require precisely these RFC connections to work.

In the context of connection monitoring, you monitor scenarios that you created in the SAP Solution Manager Configuration (transcation SOLMAN_SETUP). A scenario of this type consists of multiple technical systems and selected RFC connections between them.

Implementation Considerations

To use connection monitoring, you must have previously set it up. You do this in the SAP Solution Manager Configuration (transaction SOLMAN_SETUP). You can find the relevant configuration steps under Start of the navigation path Application Operations Next navigation step System & Application Monitoring Next navigation step Integration Next navigation step Interface & Connections End of the navigation path.

Integration

Connection monitoring is part of the System Monitoring work center in SAP Solution Manager.

Features

To displays the current status of the connections of the monitored scenarios, proceed as follows:

  1. To start the connection monitoring, in the System & Application Monitoring work center choose Start of the navigation path Interface Monitoring Next navigation step Connection Monitoring End of the navigation path.

  2. The system displays a list of all of the scenarios that you have created in the SAP Solution Manager configuration. First select the scenarios that you want to display in connection monitoring. You can select multiple elements or all scenarios at once. Choose the Connection Monitoring button and the desired display. You can choose between the window already open or a new window.

  3. The selected scenarios are displayed in a table in a three-level hierarchy. This table consists of the following parts:

    Type

    Description

    Scenario

    All checked connections are grouped by scenario. In addition to these connections, a scenario also contains the technical systems that are connected by the connections. The descriptions and statuses of the selected scenarios are displayed. The status of a scenario depends on the status of the associated connection checks. This status is propagated over the connections for the scenario; alerts, however, are always reported at the level of the connection checks.

    Example Example

    A scenario for which a connection check failed will therefore always have the status red.

    End of the example.

    Connection

    The RFC connections that you have selected for the relevant scenario are displayed in the next level. In addition to the name and status, the technical systems that are linked by this connection are also displayed.

    Connection check

    Up to three different connection checks can exist for an RFC connection, if you have activated the relevant checks in the configuration of the monitoring. These are:

    • ABAP RFC Ping

      In this metric, the availability of the RFC connection is displayed; the connection is regarded as available if the ping is answered with a response time of no more than 2 seconds. Possible statuses are green (available) or red (not available).

    • ABAP RFC Logon

      Logon check for an RFC connection; that is, unlike the purely technical availability, in this case, you check whether it is possible to logon to the target system, that is, whether a free work process is available. This check is only available for RFC connections for which corresponding authorizations are stored in their definition (such as user and password). The connection is regarded as available if the logon is possible with a maximum wait time of 2 seconds. Possible statuses are green (available) or red (not available).

    • ABAP RFC Wait Time

      Wait time of the RFC connection. In the configuration for the check, you specify the relevant threshold values of what wait times are to be assigned to which status (green, yellow, or red)

    There can also be up to three different connection checks can for an HTTP connection, if you have activated the relevant checks in the configuration of the monitoring. These are:

    • HTTP Ping

      In this metric, the availability of the HTTP connection is displayed; the connection is regarded as available if the ping is answered with a response time of no more than 2 seconds. Possible statuses are green (available) or red (not available).

    • HTTP Authentication

      Authorization check for an HTTP connection; that is, unlike the purely technical availability, in this case, you check whether the authorizations stored in the HTTP connection are valid on the target host.

    • HTTP Latency

      Wait time of the HTTP connection. In the configuration for the check, you specify the relevant threshold values of what wait times are to be assigned to which status (green, yellow, or red)

    Note Note

    Choose one of the connection checks to display the measurement availability or performance values in detail in the Metric Monitor, in a separate window.

    End of the note.

    You can also call the following functions:

    • Generate Notification button

      You can manually generate a notification by choosing the specified button; for more information about sending notifications, see Notification Administration.

    • Generate Message button

      You can manually generate a support message by choosing the specified button; for more information about creating and processing support messages, see IT Service Management.

    • Start of the navigation path Goto Next navigation step Alert Inbox End of the navigation path dropdown list

      You can display existing alerts for the selected scenario in the Alert Inbox.

    • Start of the navigation path Goto Next navigation step Landscape Browser End of the navigation path dropdown list

      You can display the technical systems that exist in the selected scenario.