お問い合わせ

Integration & Exception Monitoring

Scope

Integration & Exception Monitoring in SAP Focused Run provides monitoring of data exchange between different systems within a system landscape or between systems within the landscape and external components (e.g. public cloud services). Data is collected on managed system side (e.g. for IDocs and PI Messages) and transferred to the SAP Focused Run system or is directly pulled from APIs exposed by the public cloud services into the SAP Focused Run system. 

In the Integration & Exception Monitoring application you find the following monitoring areas:

  • Process Integration Monitor: Monitoring for PI messages and integration channels in SAP PO domains
  • Documents Monitor: Monitoring for document-based integrations like IDocs or BDocs
  • Communication Monitor: Monitoring for the availability and performance of RFC destinations, qRFC or tRFC queues and web service messages
  • Cloud Monitor: Monitoring for SAP public cloud components
  • Integration Error Monitor: Monitor and analyze critical exceptions in heterogeneous system landscapes
  • E2E Monitor: Monitoring of end-to-end message flows
  • Data Replication Monitor: Monitoring of SLT data replication and CFin Data Flow Verification
  • Custom pages: Add custom pages to display AIF monitoring or add any of the above monitoring apps to the personalized page

Features

  • Monitoring
    Get a detailed status overview per business system on the incoming/outgoing messages for different interfaces. Drilldown to single messages to check individual issues and message details
  • Analytics
    Get an overview on historical data for the different integration types to identify trends and compare different time periods.
  • Alerting
    Get an overview on scenario related alerts. Use forward navigation to analyze the alerts in the Alert Inbox
  • Tracking
    Search and track single messages based on specific business context attributes like Order Number. 

Release Notes

  • New Monitoring Content
    • SAP Batch Release Hub
      • Support category Replication Messages
    • Integration Hub for Life Sciences
      • Support category Replication Messages
    • Support of Log File Content (EXM category)
    • Enable SAP Focused Run to centrally collect any error logged by your SAP BTP CF Java Applications, by subscribing to the Data Collection Instrumentation Libraries
  • New Features   
    • Terminology Change
      • a. Templates are now known as Variants.
      • b. Filter Templates are now known as Reusable Filter Variants
    • Define Configuration Variant
      • Define Configuration variants as a set of monitoring and alerting filters that you can apply to one or more managed components.
    • Define reusable filter variants of type data collection which can be used to define monitoring filters in configuration variants.
  • Enhancements
    • SAP Integration Suite
      • Enable alerting and scenario filters with parameters “Custom Status” and “Custom Headers”.
    • IDoc
      • Enable alerting and scenario filters with parameters “Extension”
    • All Ariba Products – Ariba Procurement, Ariba Sourcing, Ariba CIG, Ariba Network.
      • Enable alerting and scenario filters with more parameters.
    • EXM categories
      • Enable alerting and scenario filters with new operator “Contains Not” 

  • New Monitoring Content
    • Component Based Message Alerts (CBMA)
      • Support for Component Based Message Alerts (CBMA) for PI systems
    • Additional filter criteria for ABAP Dumps, System Log, Aborted Jobs, Update Errors
    • Additional Alert filter criteria for SAP SuccessFactors Data Replication Monitor
  • New Features
    • Templates for scenario setup
      • Option to define templates that can be used to configure monitoring filters and alerting filters for scenarios.
    • A new advanced search page
      • The new search page to search for PI messages across components and view its details
  • Enhancements
    • tRFC Connections:
      • Enhancements to the alert details page to display single connection details
    • PI channels
      • Enhancements to the alert details page to display single connection details
    • PI Messages
      • Enable alerting based on UDS (User-Defined Search) attributes for Process Integration (PI) ABAP systems
    • IT Calendar integration: Exceptions are no longer collected during planned downtimes and maintenance windows
    • Template Management: Filter templates can be created and used for scenarios and alerts

  • New Monitoring Content
    • Web Service Messages
      • Enhancements to the alert details page to display single message level details in the metric details section
      • Enhancements to alerting and scenario filters, to enable alerting on payload values
    • qRFC
      • "Queue State" added as a filter option for alerting and scenario filters
      • Enhancements to the UI to display the threshold unit (seconds)
      • New metric "Age of oldest qRFC entries per queue" and "Number of qRFC entries" (per queue)
    • tRFC
      • "State" added as a filter option for alerting and scenario filters
      • Additional metric parameter to include age metric “Only consider entries older than []” for both existing  tRFC metrics
      • Enhancements to the UI to display the threshold unit (milliseconds)
    • IDoc
      • New metrics "IDocs in specific status code for longer than N minutes" and "IDocs in specific status group for longer than N minutes"
    • SAP BTP Cloud Foundry environment and SAP BTP Neo environment
      • A new category "SAP Mobile Services" allows the monitoring of messages in the SAP Mobile Services SaaS application
    • SAP Integration Suite (Cloud Integration)
      • Artifact deployment failures
    • SAP ABAP Dump
      • Alerting on high number per variant
    • SAP NetWeaver Java
      • Log collection with severity warning
    • SAP BTP Alert Notification
      • Support of tags with large content
  • Enhancements
    • Alert Handling Enhancements
      • We enhanced the alerting to provide a green rating if the threshold is greater than or equal to the mentioned threshold parameter in the alert definition page
      • We have enhanced the alert definition page to include a checkbox “Automatic alert confirmation on green rating”. It allows the user to decide if he wants to confirm the alert automatically on a green rating or not
      • Supported categories: qRFC, tRFC, bgRFC (Type Q), bgRFC (Type T), Connection Monitoring (SM59), PI Communication Channels
    • Enhancements to the Mass Maintenance of Alerts
      • We have enhanced the application to export all alerts and alert details for all systems for a specific category. This is cross-metric and available for Technical Systems and Cloud Services.
    • Housekeeping extension to handle SAP NetWeaver Java log high volume stores
    • Enhancement of SAP NetWeaver Java logs collector (in Simple Diagnostics Agent), to handle high volumes (transfer in chunks & exceptional volume clipping)
    • Collection of ABAP Aborted Job logs for Job Monitoring

  • The application has been renamed "Integration & Exception Monitoring"
  • New Monitoring Content
    • Enable PUSH based data collection for AIF messages in S/4HANA Cloud Public Edition.
    • New category "Concur Objects" for the monitoring of messages in the SAP Concur Integration add-on in SAP S/4HANA Cloud Public Edition and SAP S/4HANA.
    • New category "SAP SuccessFactors HXM Suite" for the monitoring of messages in SAP SuccessFactors for the integration with SAP S/4HANA Cloud Public Edition and SAP Master Data Integration.
    • Enable the monitoring of AIF messages for SAP Business Suite
  • Enhancements
    • Timeframe for the embedded analytics dashboards has been changed to "Inherited" to inherit dates from the global time frame selected for the application
    • Additional filter fields for the filtering of PI messages for alerting and scenarios
    • Additional filter fields for the filtering of IDocs for alerting and scenarios
    • Aggregated analytics data can be stored for 9999 days instead of 999
    • Additional information from selected IDoc segments is displayed on the "Data Records" tab for the IDoc details (to define the collected segments please follow Collecting Business Context for AIM)
    • Option to "Ungroup" alert groups and create an alert for every single occurrence of an alert via the checkbox "Atomic Alerts"
    • Option to adjust the data collection frequency for active Integration Monitoring categories for on-premise technical systems (This functionality doesn't yet exist for exception categories and cloud services)

  • New monitoring and analytics content in Cloud Monitoring for
    • SAP Ariba CIG
    • SAP Ariba Procurement
    • SAP Ariba Sourcing
    • SAP Ariba Network
  • New alerting content for SAP ABAP systems
    • qRFC - Number of qRFC entries
  • New analytics content for
    • Integration Gateway component in SAP Process Integration
    • SAP Marketing Cloud
    • SAP Fieldglass
    • SAP Integration Suite - Cloud Integration
      • Summary per Artifact
    • SAP Process Integration - PI Messages 
      • Summary per Sender Interface
      • Summary per Receiver Interface
  • Improvements to the alerting and scenario setup

  • New monitoring content in Cloud Monitoring for
    • SAP Marketing Cloud
    • SAP Fieldglass
  • New monitoring content in Process Integration Monitoring for
    • Integration Gateway component in SAP Process Integration
    • Messages related to the deployment of cloud integration content from the SAP Integration Content Catalog in the Advanced Adapter Engine
  • New content in Analytics for
    • Web Service messages
    • BDocs
  • Improvements to the alerting and scenario setup
    • New filter operators for the categories SAP Integration Suite and qRFC
    • Use multiple values for the same parameter in the same filter
  • Enhanced email content for IDoc alerts

  • Non-SAP Monitoring is now available 
    • Sending monitoring data from a 3rd party system to Integration and Cloud Monitoring application
  • Analytics is now part of Integration and Cloud Monitoring
    • Creation of dashboards possible with historical data (up to 12 months) for IDocs, PI Messages and CPI Messages
  • Improvements to the E-Mail content
    • Jump-in URL is now available
    • Customer can define more content via a BAdI implementation
  • Alert creation enabled for all AIF categories

  • Enhanced monitoring content for S4HANA on-premise & CE (new AIF message type SYNC_LOG, relevant for Cost Center Replication)
  • Improvements in Alert Configuration (support for alert per variant)
  • Improvements in AIM application
    • Support for non-SAP systems and unspecific cloud services in AIM topology (more information)
    • UI unification

  • Support of Data Flow Verification for SAP Central Finance (CFin)
  • Support for Monitoring and Alerting for MII Queues
  • New monitoring category for the monitoring of SAP Ariba Cloud Integration Gateway related document processing failures
  • Improvements in the Integration Monitoring setup, like:
    • Filters created for scenarios can be reused in alerts and vice versa
    • User-dependent visibility of Integration Monitoring scenarios
    • Creation of alerts per variant for connection monitoring

  • Support of Monitoring and Alerting for new categories (message data) like MII, SAP S/4HANA (AIF Messages) and SAP S/4HANA Cloud (AIF Messages)
  • Support of Monitoring and Alerting for new category (replication data) like SLT

  • Support of single message flows processed by SAP PI/PO or SAP Cloud Platform Integration Capability
  • Support of peer-to-peer interface technologies as IDOC, RFC, Rest and Web Service
  • Dashboard based visualization with Systems / Cloud Services or Integration Scenarios as entry point
  • Monitoring of exceptions for Cloud and On Premise products based on advanced dashboard capabilities
  • Message and document search to identify integration artifacts related certain business context
  • End-to-End Monitoring to follow single message flows and interface cross components and technologies
  • Integration in Event & Alert Management

Focused Run 2.0 FP02

  • Support of Data Flow Verification for SAP Central Finance (CFin)
  • Support for Monitoring and Alerting for MII Queues
  • New monitoring category for the monitoring of SAP Ariba Cloud Integration Gateway related document processing failures
  • Improvements in the Integration Monitoring setup, like:
    • Filters created for scenarios can be reused in alerts and vice versa
    • User-dependent visibility of Integration Monitoring scenarios
    • Creation of alerts per variant for connection monitoring

Prerequisites

Prerequisites

  • Install SAP Focused Run 1.0 FP01 or higher
  • Enable the Use Case Integration & Exception Monitoring as described in the SAP Focused Run Master Guide
  • Implement release dependent relevant notes 

Relevant Notes for the SAP Focused Run System

  • SAP Focused Run 2.0 SP00
    2712403 - Composite Note for Advanced Integration Monitoring in Focused Run for SAP Solution Manager Release 2.0 SP00
    2732826 - Corrections for Exception Management (FRun 2.00)
  • SAP Focused Run 2.0 FP01
    2800509 - Composite Note for Advanced Integration Monitoring in Focused Run for SAP Solution Manager Release 2.0 FP01
    2732826 - Corrections for Exception Management (FRun 2.00)
  • SAP Focused Run 2.0 FP02
    2860641 - Composite Note for Advanced Integration Monitoring in Focused Run for SAP Solution Manager Release 2.0 FP02
    2899694 - Collective corrections for FRUN UI5 applications 2.0 FP02
    2732826 - Corrections for Exception Management (FRun 2.00)
  • SAP Focused Run 2.0 FP03
    2926064 - Composite Note for Advanced Integration Monitoring in Focused Run 2.0 FP03
    2732826 - Corrections for Exception Management (FRun 2.00)
  • SAP Focused Run 3.0 SP00
    2996034 - Composite Note for Advanced Integration Monitoring in Focused Run 3.0 SP00
    3004640 - Corrections for Exception Management (FRun 3.00)
  • SAP Focused Run 3.0 FP01
    3062288 - Composite Note for Advanced Integration Monitoring in Focused Run 3.0 FP01
    3004640 - Corrections for Exception Management (FRun 3.00)
  • SAP Focused Run 3.0 FP02
    3116253 - Composite Note for Advanced Integration Monitoring in Focused Run 3.0 FP02
    3004640 - Corrections for Exception Management (FRun 3.00)
  • SAP Focused Run 3.0 FP03
    3205465     - Composite Note for Advanced Integration Monitoring in Focused Run 3.0 FP03
    3004640 - Corrections for Exception Management (FRun 3.00)
  • SAP Focused Run 4.0 SP00
    3269817 - Composite Note for Integration Monitoring in Focused Run 4.0 SP00
    3273282 - Corrections for Exception Monitoring (FRun 4.00)
  • SAP Focused Run 4.0 FP01
    3318020 - Composite Note for Integration and User Monitoring in SAP Focused Run 4.0 FP01
  • SAP Focused Run 4.0 FP02
    3393382 - Composite Note for Integration and User Monitoring in SAP Focused Run 4.0 FP02

Relevant Notes for the Managed System

  • 2738914 - IDoc: Saving of passport ID at IDoc runtime
  • 2309642 - Collective corrections as of ST-PI 2008_1 SP14 and ST-PI 7.40 SP04
  • 2820901 - Corrections for FRUN Data collectors in ST-PI
  • 2450740 - Roles to authorize access in managed systems to collect data for FRUN

 

 

Content & Monitoring Setup

To setup Integration & Exception Monitoring please follow the monitoring setup guide provided for each of the supported categories.

Monitoring capabilities for on-premise systems

Monitoring capabilities for SAP public cloud services

Integration Scenarios & Flows

In Integration & Exception Monitoring, integration monitoring information is collected on the technical component level. This makes the setup much easier and less error-prone because SAP Focused Run can suggest monitoring categories based on the installed software components. For most of the categories SAP Focused Run also offers default filters, which collect all communication for this monitoring category, no matter where they came from or where they are sent to. These capabilities speed up the initial setup of Integration & Exception Monitoring, as it is no longer necessary to maintain a specific source-target combination for an interface. 

However, this new setup approach also means that the landscape topology, which shows the connections between the systems in the landscape, is no longer created automatically. Instead, the landscape topology can be created in a scenario, if it is required. Creating the landscape topology will usually not be necessary for all interfaces in a landscape. For most of them, the technical component-based view will be sufficient. But if you want to group different point-to-point connections that belong to a more complex interface scenario together, you can do this by setting up a scenario.

For some monitoring categories SAP Focused Run can further more correlate messages sent, via the SAP passport. For these monitoring categories you can set up end-to-end flows that describe messages flows that run over several technical components. You can monitor where in the flow a message is located and how long the overall flow took.

For more information, please check the Scenario Configuration.