As a part of Integration Monitoring, Interface and Connection Monitoring (ICMon) in SAP Solution Manager provides you with a powerful tool to monitor various interface technologies within your landscape. This page will provide you with information on the setup and the usage of ICMon.

Interface and Connection Monitoring in Solution Manager 7.1 SP12 comprises now all the metrics from Interface Channel Monitoring, Connection Monitoring and the former Interface Monitoring metrics from Business Process Monitoring in one powerful tool. All metrics are set up as Interface Channels, which allows you to abstract from a concrete technical implementation of an interface and bring together different interfaces that serve the same business purpose. Inside an Interface Channel the separate interfaces can be defined and metrics can be selected which monitor the interface in various aspects, focusing on error or backlog situations during processing. The Interface Channels can be assigned to ICMon scenarios as well as to Business Process Monitoring scenarios. 

In Solution Manager 7.1 Connection Monitoring is still available as standalone application, even though its metrics are already integrated in ICMon. This application will be retired with Solution Manager 7.2. and will no longer be available.

For general information about how to perform the infrastructure configuration for Interface and Connection Monitoring and general functionality when setting up a channel, follow this documentation.

The following Interface Channel types are currently supported with SAP Solution Manager. For information on the specific setup procedure and technical prerequisites for each channel type please follow the documentation for each channel type.

In some cases you might need different settings for the metrics and alerts shipped with the SAP standard templates, for this please check the Template Maintenance for ICMon.

General

• Interface Channel Monitoring is available as of Solution Manager 7.1 SP05
• System Monitoring Setup of the Technical Systems involved is required for Solution Manager Releases 7.1 SP05 - SP08
• For availability measurement via EEM script in EEM Setup step 2 (Configure Infrastructure) the automatic activities 'Create Endpoints for communication' and 'Create Logical Ports' must be executed.
• It is highly recommended to synchronize the times of all application server of the managed systems and SAP Solution Manager with time services. Otherwise it might happen that gaps in collection intervals can occur or in worst case nothing can be selected.

Technical Requirements

• RFC and Web Service Monitoring
  • RFC and Web Service data collectors for ABAP performance metrics in managed systems are available as of ST-PI 2008_1 SP06 for ABAP systems with SAP Basis >= 7.00
    Only SOAP Web Services and no PI WS are instrumented.
  • Web Service data collectors for Non-ABAP performance metrics are available as of Solution Manager 7.10 SP06
  • Data collectors for ABAP Dumps, Web Service Exceptions, AppLog Exceptions are available as of ST-PI 2008_1 SP06 for managed ABAP systems with SAP Basis >= 6.20
  • Data collectors for Exceptions collected via the Exception Management Instrumentation Platform (EM-IPA) are available as of ST-PI 2008_1 SP06 for managed ABAP systems with SAP Basis >= 7.00
• PI Monitoring
  • PI data collectors are available as of Solution Manager 7.10 SP05 for systems with SAP PI >= 7.00
  • PI domain relevant for monitoring has to be known in LMDB
• File Monitoring
  • A diagnostic agent needs to be installed on the host where the relevant files are to be monitored. The agent needs to have proper authorization to access the relevant folder and the file information there in.
• SAP Netweaver Gateway Monitoring
  • Data collectors are available as of ST-PI 2008_1 SP07
• IDoc, qRFC, bgRFC, tRFC Monitoring, BDoc, CRM Middleware, Workflow, Batch Input 
  • Data collectors are available as of ST-PI 2008_1 SP10 and ST-A/PI 01R for managed ABAP systems with SAP Basis >= 7.00
  • You normally monitor the IDocs for your productive client. Therefore you need a SM_<SID>CLNT<CLNT>_TMW destination into your productive client to be able to read IDoc information.
  • See also note 1949245 for further information.
• HTTP
  • Incoming HTTP requests for ABAP systems are available as of ST-PI 2008_1 SP10

Managed Systems (ST-PI)

• 1703352 - No authorization for web service error log (required up to SAP Solution Manager 7.1 SP08)
• 1011229 - ST-PI: Corrections for E2E Diagnostics (required up to ST-PI 2008_1 SP07)
• 1778870 - Support of MAI Data Providers in different namespaces  (required up to ST-PI 2008_1 SP08)
• 1729771 - Collective corrections as of ST-PI 2008_1 SP06 (up to SP09)
• 2062497 - Collective corrections as of ST-PI 2008_1 SP10 (up to SP13) and ST-PI 7.40 (up to SP03)
• 2309642 - Collective corrections as of ST-PI 2008_1 SP14 and ST-PI 7.40 SP04
• 2256716 - Collective note IDoc Monitoring & IDoc Reporting ST-A/PI 01S
• 2533666 - For an Interface Channel with multiple Interfaces some metrics are not collected and stay in status gray
• 2813199 - Some Interface Channel Monitoring or/and Business Process Monitoring Objects remain in Status Gray
• 2941818 - Solution Monitoring: Collected ST-PI Corrections - ST-PI 740 SP13 / ST-PI 2008_1_7* SP23
• 2953854 - Solution Monitoring: Collected ST-A/PI Corrections - ST-A/PI 01U* SP00
• 2983475 - Solution Monitoring: Collected ST-A/PI Corrections - ST-A/PI 01U* SP01

Note: Loss of Configuration in case of Landscape Changes

Some landscape changes, e.g. change of property SystemHome for a technical system in LMDB, trigger notifications which lead to deletion of IF channels which have the technical system as source or target assigned. To avoid this auto-deletion, please implement the following SAP notes:

See Troubleshooting Guide

Read about the benefits of Exception Management Cockpit.