Skip to end of metadata
Go to start of metadata

Setup and Configuration of Interface Channel Monitoring with Solution Manager 7.1 SP10 and SP11

 

Navigation

Application Operations in SAP Solution Manager 7.2 provides System and Application Management capabilities for central monitoring, alerting, analytics, and administration of SAP centric cloud and on-premise solutions.

This wiki content has been move to the SAP Solution Manager 7.2 expert portal.  Any child pages of this wiki are deprecated and no longer maintained.

Technical Support

Application Operations in SAP Solution Manager 7.2 provides System and Application Management capabilities for central monitoring, alerting, analytics, and administration of SAP centric cloud and on-premise solutions.

This wiki content has been moved to the SAP Solution Manager 7.2 expert portal.  Any child pages of this wiki are deprecated and no longer maintained.

The Interface Channel Monitoring Setup is integrated into the Solution Manager Configuration Workcenter below Technical Monitoring. With SolMan 7.1 SP10, Interface Monitoring applications and Process Orchestration Monitoring applications are bundled together below Interface and Process Orchestration . The Setup itself consists of several steps which are executed as a Guided Procedure. Each step contains a help section as well as a logging area.

Depending on your current SP level, the following setup steps might slightly differ from the ones explained here. 

 

Overview

This step is the entry point and the overview page of the Interface Channel Monitoring configuration.

Configure Infrastructure

Check Prerequisites

In this step, you can execute a check whether the prerequisite(s) for the configuration of the Technical Monitoring infrastructure is fullfilled. It usually refers to the status of the Basic Configuration . This step is the same as in the System Monitoring configuration.

Configure Manually (optional)

In this step you have the possibility to customize content for Interface Monitoring specific notifications and incidents, created automatically in case an Alert is generated in the Central Alert Inbox of Solution Manager.

Default Settings

In this step, you have the possibility to enable/disable and configure Auto-Incidents and Auto-Notifications for Interface Channel Monitoring in general, i.e. independent of a specific scope.

For Auto-Notifications, it is recommended to add a specific Recipients List (instead of individual recipients) which can be maintained via Maintain Recipients List. By doing so you avoid re-configuration in case you would simply activate/de-activate notifications for a specifc recipient.

Standard Users (optional)

In this optional step, you can create the standard Level 1 and Level 2 ICMon Template/Demo Users in the SAP Solution Manager system. When you create a template user, the system assigns roles and authorizations automatically.

The level 1 user can distribute problems in the Alert Inbox, to other users.Besides the ICMon UI he is able to access the Alert overview monitor and can create notifications/incidents.

The level 2 user has all authorization of the level 1 user plus additional permissions to act as the second level support for certain problems. He is able to work in the Alert Inbox and performance Root Cause Analysis activities in order to process relevant problems.

Global Settings

In this step you can configure Global Settings which can be used for Interface Channel Monitoring independent of a specific scope.

EEM Script Configuration (Optional)

In order to actively monitor the availability of an Interface Channel of type RFC or Web Service (to be defined later on) you first need to create a script via the End-User-Experience Monitoring Editor, which you can download in this activity.

With SolMan 7.1 SP10 availability monitoring of RFC connections (incl. TCP/IP) does not require the creation of an EEM Script anylonger.

Define Global Attributes

You can define global attributes which can later on be used to tag an Interface Channel. These so-called Interface Channel Attributes are used to identify a bundle of interfaces (which is contained by an Interface Channel) sufficiently. Semantics of interface channel attributes are freely definable and defined once they are shared between all Interface Channel Monitoring scenarios.

Define Scope

In this step you can define, delete and maintain Interface Channel Monitoring scenarios. Without selecting a scenario you cannot proceed to the next setup steps. A scenario is a set of technical systems and/or hosts. The scenario should involve all systems and/or hosts for which you would like to monitor intefaces and communications. Hosts are currently only relevant for File Monitoring.

Prerequisite: Before you can configure Interface Channel Monitoring for a scenario, you have to finish the Managed System Configuration for the technical systems included in the scenario. In addition, for SolMan releases ≤ 7.1 SP8, System Monitoring Setup is a prerequisite for the technical systems included in the scenario.

If you would like to monitor communications from/to components which are not part of the Systems landscape in Solution Manager (e.g. middle ware components or if you like to bundle several front end components), you can create a Technical System of type Unspecific to do so. With SolMan 7.1 SP10 it is also possible to use ICMon internal unspecified components (see below).

In order to avoid known problems in the Monitoring UI, please do not use scenario names longer than 30 characters.

Monitoring & Alerting

Perform Automatic Prerequisites

In this step several prerequisite activities are executed, e.g. scheduling of extractors to retrieve RFC destinations from the managed systems. Data collection is triggered on a daily basis. After data are collected, the RFC destinations are available as a value help in the Interface Channel Configuration. Initial data collection of RFC destinations might take some time. In addition, meta data information for the ICMon Configuration UI are retrieved.

Perform Manual Prerequisites

Select Scenario attributes

If you want to attach filter attributes to the interface channels, you have to select them from the global attribute pool (defined in Step Global Settings). The selected attributes are valid for the whole scenario and can be used to tag an Interface Channel. They can be used as a filter in the Monitoring UI.

Activate Web Service Monitoring

If you want to monitor synchronous web service calls regarding performance and number of executions of your ABAP system, you first need to activate local Web Service Monitoring in the managed system. The URL attached to this activity provides a jump-in to the relevant SAP note which describes how to do this. For further information, please refer to the activity documentation.

Interface Channel Monitoring Configuration

This step contains the configuration of the selected scenario. Here you define Interface Channels for different Interface Types.

Currently, the following interface types are supported:

  • (a)Synchronous Remote Function Call (RFC)
  • Web Service (WS)
  • SAP Process Integration (PI)
  • SAP Netweaver Gateway Services (GW) 1
  • Flat File (File) 1
  • Intermediate Document (IDoc) 1
  • Queued Remote Function Call (qRFC) 1
  • Transactional Remote Function Call (tRFC) 1
  • Background Remote Function Call (bgRFC) 1
A list of available metrics dependend on your Solution Manager release can be found here.

Creating and Configuring an Interface Channel

You can create a new Interface Channel, add an already existing Interface Channel to the current scenario or delete an Interface Channel from the current scenario.

When creating an Interface Channel you first need to specify a unique technical name, a display name and the interface type.

 

Depending on the Interface type the following configuration may vary: 

RFC

You specify the Source and the Target System. If you choose type Technical System the corresponding object has to be part of the Scope (Technical Scenario) for which the setup is running. In addition, you can choose for either source or target the type Unspecific Managed Object for which you can specify a free defined name. This can be useful, e.g., in case you would like to monitor RFC communication from/to a third party system.

Usage of type Unspecific Managed Object is available for Solution Manager SP10 and higher. For lower releases you can create a Technical System of type Unspecific instead.

Metrics for Interface Channels of type RFC are always retrieved from the target system, if the target system is of type ABAP. Elsewise they will be retrieved from the source system.

Once you created an Interface Channel, you need to maintain the interface detail information (below tab Interfaces). Every line represents an interface within the selected interface channel. For type RFC the interface is characterized by Destination and Remote enabled Function Module. Leaving a parameter empty will result in an aggregation over this parameter. You also have the possibility to use wildcards, which will result in single metrics reported for each match during data collection.

Via the tab additional configuration you can:

  • Choose the availability script (created in Step 3) in case you also want to monitor the availability of the Interface Channel

    With Solution Manager SP10, it's possible to monitor RFC Availability via RFC Ping without assigning a specific script. In order to check the availabilty via RFC Ping, the RFC Destination needs to be fully specified. 
  • Monitor specific application log entries regarding exceptions for the selected Interface Channel. If you would like to do so, you have to (fully) specify the relevant object/subobject.

    Monitoring of Application Log Settings are not specific to the definied Interfaces but to the specified object/subobject.
  • Specify that Performance Metrics shall be collected per instance (elsewise they will be aggregated over all instances)

    Because of potentially high data volume instance specific data collection is turned off by default.

WS

You specify the Source and the Target System. If you choose type Technical System the corresponding object has to be part of the Scope (Technical Scenario) for which the setup is running. In addition, you can choose for either source or target the type Unspecific Managed Object for which you can specify a free defined name. This can be useful, e.g., in case you would like to monitor WS communication from/to a third party system or in case you just would like to monitor, e.g., all incomming requests for a specifc Web Service.

Usage of type Unspecific Managed Object is available for Solution Manager SP10 and higher. For lower releases you can create a Technical System of type Unspecific instead.

Metrics for Interface Channels of type WS are always retrieved from the target system, if the target system is of type ABAP. Elsewise they will be retrieved from the source system.

Once you created an Interface Channel, you need to maintain the interface detail information (below tab Interfaces). Every line represents an interface within the selected interface channel. The interface is characterized by Web Service / Web Service Method / Logical Port (if you monitor on client side) and/or Web Service User (if you monitor on server side). Leaving a parameter empty will result in an aggregation over this parameter. You also have the possibility to use wildcards, which will result in single metrics reported for each match during data collection.

Via the tab additional configuration you can:

  • Choose the availability script (created in Step 3) in case you also want to monitor the availability of the Interface Channel

     

    Monitor specific application log entries regarding exceptions for the selected Interface Channel. If you would like to do so, you have to (fully) specify the relevant object/subobject.

    Monitoring of Application Log Settings are not specific to the definied Interfaces but to the specified object/subobject.
  • Specify that Performance Metrics shall be collected per instance (elsewise they will be aggregated over all instances)

    Because of potentially high data volume instance specific data collection is turned off by default.


     

GW

You specify the Source and the Target System. Since GW monitors the communications between the SAP Netweaver Gateway and the ABAP backend, specification of Unspecific Managed Object is only possible for the Source system. For Unspecific Managed Object a free defined name can be specified. The target system has to be a Technical System of type ABAP and has to be part of the Scope (Technical Scenario) for which the setup is running. 

Metrics for Interface Channels of type GW are always retrieved from the target system.


Once you created an Interface Channel, you need to maintain the interface detail information (below tab Interfaces). Every line represents an interface within the selected interface channel. The interface is characterized by Service / Operation / Entity / User. Leaving a parameter empty will result in an aggregation over this parameter. You also have the possibility to use wildcards, which will result in single metrics reported for each match during data collection.

 

PI

You first need to select the relevant PI domain. The list of available PI domains is determined by the Technical Systems in scope. Afterwards you need to specify the source and the target systems in between which the message communication is to be monitored.

As a prerequisite the PI domain needs to be known in LMDB. Details regarding the Landscape Synchronization of PI domain data can be found here. Setup of PI Monitoring is not mandatory.

Metrics for Interface Channels of type PI are always retrieved from the source system, the target system and the integration server in-between (if possible).


Once you created an Interface Channel, you need to maintain the interface detail information (below tab Interfaces). Every line represents an interface within the selected interface channel. The interface is characterized by the different Sender and Receiver attributes. Leaving a parameter empty will result in an aggregation over this parameter. You also have the possibility to use wildcards, which will result in single metrics reported for each match during data collection.

File

File Monitoring is done for files on a specific host. Therefore, you usually specify the host as a target system and select an Unspecific Managed Object as source. The Channel than refers to file access from the specified source object.

Metric Collection is done via the Diagnostic Agent installed on the target (source) host. It needs to be ensured that the agent has the proper rights to access the relevant folder and the file informations there in. 

Metrics for Interface Channels of type File are always retrieved from the target host if the target is of type host. Elsewise they will be retrieved from the source host.


Once you created an Interface Channel, you need to maintain the interface detail information (below tab Interfaces). Every line represents an interface within the selected interface channel. You need to specify a File Name and a Folder. For the file name you have the possibility to use wildcards. This will influence the result of the retrieved metrics in the following way:

  • Size: Overall Size of all Files which match the specified pattern
  • Age: Age since last modify operation on a file which matches the specified pattern
  • Availability: Total Number of files which matches the specified pattern

IDoc

You specify the Source and the Target System. If you choose type Technical System the corresponding object has to be part of the Scope (Technical Scenario) for which the setup is running. In addition, you can choose for either source or target the type Unspecific Managed Object for which you can specify a free defined name.

Depending on you selection, you need to specify whether the metrics shall be retrieved from source or target system and you need to specify the relevant client.

Once you created an Interface Channel, you need to maintain the interface detail information (below tab Interfaces). Every line represents an interface within the selected interface channel. The interface is characterized bypartner information / message type etc. Leaving a parameter empty will result in an aggregation over this parameter. You also have the possibility to use wildcards, which will result in aggregated metrics reported for the matched pattern.

Per default, for IDocs a limited set of the most often used Interface parameters is displayed. Via Expert Mode you can display/maintain even more configuration parameter if necessary.


In addition, you need to maintain parameter configuration on Key Figure level. In order to do so, please choose the relevant key figure and maintain the necessary key figure parameter. Mandatory fields are marked with a red asterix.

 

Input values for the Selected Time Frame filed are described here.

 

qRFC

You specify the Source and the Target System. If you choose type Technical System the corresponding object has to be part of the Scope (Technical Scenario) for which the setup is running. In addition, you can choose for either source or target the type Unspecific Managed Object for which you can specify a free defined name.

Depending on you selection, you need to specify whether the metrics shall be retrieved from source or target system and you need to specify the relevant client.

Once you created an Interface Channel, you need to maintain the interface detail information (below tab Interfaces). Every line represents an interface within the selected interface channel. The interface is characterized by RFC Destination / Queue Group. Leaving a parameter empty will result in an aggregation over this parameter. You also have the possibility to use wildcards, which will result in aggregated metrics reported for the matched pattern.

Per default, for qRFC a limited set of the most often used Interface parameters is displayed. Via Expert Mode you can display/maintain even more configuration parameter if necessary.

 

tRFC

You specify the Source and the Target System. If you choose type Technical System the corresponding object has to be part of the Scope (Technical Scenario) for which the setup is running. In addition, you can choose for target the type Unspecific Managed Object for which you can specify a free defined name.

For tRFC monitoring only outgoing requests are collected. Therefore measurement is always done in the source ABAP system.

Once you created an Interface Channel, you need to maintain the interface detail information (below tab Interfaces). Every line represents an interface within the selected interface channel. The interface is characterized by RFC Destination / Function Module. Leaving a parameter empty will result in an aggregation over this parameter. You also have the possibility to use wildcards, which will result in aggregated metrics reported for the matched pattern.

Per default, for tRFC a limited set of the most often used Interface parameters is displayed. Via Expert Mode you can display/maintain even more configuration parameter if necessary.

 

bgRFC

You specify the Source and the Target System. If you choose type Technical System the corresponding object has to be part of the Scope (Technical Scenario) for which the setup is running. In addition, you can choose for either source or target the type Unspecific Managed Object for which you can specify a free defined name.

Depending on you selection, you need to specify whether the metrics shall be retrieved from source or target system and you need to specify the relevant client.

Once you created an Interface Channel, you need to maintain the interface detail information (below tab Interfaces). Every line represents an interface within the selected interface channel. The interface is characterized by Type / Destination / Queue Name etc. Leaving a parameter empty will result in an aggregation over this parameter. You also have the possibility to use wildcards, which will result in aggregated metrics reported for the matched pattern.

In addition, for each Interface Channel you can add and specify the so-alled Interface Channel attributes. These attributes are then available as tags and filter attributes in the Monitoring UI.

Once you finished the configuration, please press the Save button and proceed to the activation step.

Interface Channel Monitoring Activation

In this step you see the overview of metrics which can be collected for the selected scenario based on the configuration you made before.

When entering this step, the configuration settings made in the previous step is mixed with template information available in the Monitoring and Alerting Repository. Thus, it might take a while until all information is retrieved. In case the metrics are not shown in the tree structure, please have a look in the Troubleshooting section .

You have the possibility to enable/disbale the metric sonsumption, i.e you can specify which metrics shall be relevant for Alerting (Alerts visible in Alert Inbox) and which for Monitoring (Metrics to be shown in the IC Mon UI). You can deactivate or activate the alert generation on all three levels.

Disabling metrics for Alerting will not only suppress the alert generation in the Alert Inbox but will also remove the metric for display in the Metric Detail View of the Interface Channel Monitoring UI.

Disabling metrics for Monitoring will suppress writing of the metrics into BW. These metrics will than be not available in the Dashboard View of the of the Interface Channel Monitoring UI.

You have the possibility to define/modify thresholds  for various metrics belonging to an Interface Channel.

Via the link Thresholds, you can jump to a Mass Maintenance UI for Thresholds. Here you can maintain thresholds and comparethe settings with already retrieved historical data.

 

In addition, you can modify the settings for Notification/Incident Management (triggered upon alert generation) on Interface Channel level.

 

Saving your activities will trigger the content activation; changes are distributed to the run-time components.

Complete

This step contains the summarizes the status of the previous steps.

 


  1 available with Solution Manager 7.10 SP10

This page is part of the Application Operations Wiki. Notice that Application Operations itself is a use-case of SAP Solution Manager

 

 

  • No labels