Show TOC

Procedure documentationConfiguring an Interface and Connection Monitoring Scenario Locate this document in the navigation structure

 

A guided procedure helps you to set up an Interface and Connection Monitoring scenario. This chapter gives an overview of the process.

Depending on the interface type, you can monitor different metrics, and have to specify parameters.

Prerequisites

  • You have configuration authorization for Interface and Connection Monitoring.

    To create a configuration user, or assign the required roles to an existing user, do the following:

    1. In the SAP Solution Manager Configuration work center, choose the Basic Configuration scenario.

    2. Choose the Create Configuration User step.

    3. Under Users, select the user for the Interface and Connection Monitoring scenario and perform the required steps.

  • You have identified the components and systems whose interfaces you want to monitor.

  • For the technical systems to be included in the scenario, you have executed the following SAP Solution Manager configuration scenarios:

    • Managed system configuration

    • System monitoring setup

Procedure

To configure Interface and Connection Monitoring, perform the following activities.

Starting the guided procedure

In the SAP Solution Manager Configuration work center, choose   Technical Monitoring   Integration Monitoring   Interface Channels  .

Creating an Interface and Connection Monitoring Scenario

An interface channel bundles a set of interfaces of a specific type, between two technical systems. Interface channels can be reused in different scenarios. Interface channel attributes tag an interface channel.

  1. In the Define Scope step, define all technical systems that are either the source or target system of an interface channel in your scenario.

  2. If you want to monitor the availability or performance of Web service interfaces, in the Preparation sub-step of the Monitoring & Alerting step perform one or both of the following activities:

    • Availability: Create End User Experience Monitoring (EEMon) scripts to be executed automatically, every minute.

      Note Note

      Monitoring for interfaces of type RFC is available by default.

      End of the note.

      For more information, see Creating an EEMon Script for SOAP Requests.

    • Performance: Activate Web service monitoring.

      If required, you can configure Web service monitoring to drill down to the users calling Web services. To minimize the impact on the performance, this option is disabled by default.

  3. Optional: To allow filtering in the Interface and Connection Monitoring UI, and identify scenarios and interface channels, in the Preparation sub-step of the Monitoring & Alerting step, assign one or more attributes to the scenario.

    Create attributes according to your business requirements, for example business area, business scenario, company, region. You can reuse attributes in various Interface and Connection Monitoring scenarios, by assigning them to an Interface and Connection Monitoring scenario and the interfaces, in a scenario.

  4. In the Configuration sub-step of the Monitoring & Alerting step, create an interface channel:

    1. Define the interface type.

    2. Define the source and target systems of the interface channel. You can specify the source or target system type in the following ways:

      • If both source and target systems are managed systems which are registered in the LMDB, select the type, for example RFC, host, or technical system.

      • If the source or target system is not registered in the LMDB, select Unspecified Managed Object. Use this option to monitor the following interfaces, for example:

        • Third-party target systems

        • SAP NetWeaver Gateway services (to monitor, for example, mobile devices such as smart-phones)

        • Instances of a web service (you want, for example to monitor how often a web service was called, from where, and by which source systems.

        The data is collected in the managed system. The corresponding non-LMDB object is in the Interface Channel Topology chart of the monitoring UI.

        In the Source or Target field, enter an alias which represents the unspecified managed object in the monitoring UI, or select an existing alias.

    3. On the Interfaces tab page, define the interfaces in the interface channel. Depending on the interface type, specify, for example, the following parameters:

      • RFC: the RFC destination and the RFC-enabled function module.

      • Web service: the web service and Web service method.

      • SAP NetWeaver Gateway service: the Gateway service, operation entity type, and user

      • SAP NetWeaver Process Integration: the sending and receiving PI systems for which you want to monitor the message flow.

      • SAP Public Cloud Communications: the iFlow name, and the sending and receiving systems

      • IDoc: the business partner, message type, and monitoring time frame of an IDoc interface. You can specify a dynamic time frame for data collection.

        Specify one or more of the following key performance indicators (KPI) to be monitored in the specified time frame, for each IDoc interface:

        • Average time to process IDocs: The average time taken to process an IDoc in a system allows you to detect irregularities.

        • Current number of IDocs: The number of IDocs which are currently being processed allows you to estimate the system load.

        • Current number of erroneous IDocs: You identify errors and resolve them.

        To configure at least one key performance indicator (Current number of erroneous IDocs, for example), you assign a status code (an error code, for example). The status codes depend on the configuration of your IDoc system (transaction WE47). If you have, for example, maintained multiple error codes, add a line for each error code monitored, or define a range.

        For more information about the placeholders available, see Specifying a Dynamic Time Frame.

      • BDoc and CRM Middleware: the business partner number and port, message type, and monitoring time frame of a BDoc interface

      • Workflow: the task/workflow, status, agent assigned, maximum age and total/delta mode.

        • To select items without restriction of age at each execution, if the maximum age parameter is not, leave the Total/Delta Mode field empty. The default value TOTAL is used.

        • To select only items that were added between the last and the current execution, enter DELTA.

      • File system: You specify the host, folder (/usr/ftp/incoming, for example), and a file name pattern (*.log, for example).

    4. Select the metrics to monitor and configure the metric-specific parameters as required.

      Example Example

      • To monitor the availability of the interface channel, specify the EEMon script that you have defined.

      • To monitor application log entries for exceptions for the Interface, specify the object/sub-object.

      End of the example.

    5. On the Attributes tab page, select an attribute to filter for an interface channel, and assign a value. For example the attribute Region with the value EMEA.

Activating an Interface and Connection Monitoring Scenario

In the Activation sub-step of the Monitoring & Alerting step, maintain notification/incident settings for specific alerts and threshold for the specific metrics underlying an interface channel.

To display a metric in the Interface and Connection Monitoring dashboard select the Reporting checkbox. For more Information, see Displaying an Interface and Connection Monitoring Scenario.

Assigning Authorizations

To allow an existing user to monitor the scenario, assign the required roles.

  1. Choose the Standard Users step.

  2. Under Users, select a template user (level 1 or level 2) according to the required display user authorization.

    For more information, see the documentation of the template users, and the SAP Solution Manager Security Guide.

  3. Perform the required steps.