PI Messages

PI Messages

The message flow via SAP PI can be very complex, passing different components (such as adapter engines with the module processor and messaging system, integration engines with their pipeline processing including Java & ABAP proxies, business process engine etc.) and using different adapter types (such as File-, JMS-, IDoc-, RNIF-adapters etc.).

This complexity makes it difficult to track and monitor the flow of a specific message across SAP PI. Automated monitoring of messages is essential to ensure the error-free operation of SAP Process Integration (SAP PI) and each integration scenario.

 

PI Channels

In order to define the communication details for a SAP PI message so-called communication channels are used in SAP PI. Both the inbound and outbound communication is maintained in the channel definition, including the adapter used for the particular interface. This way the right sender and receiver components are available during runtime of a message. Communication channels can have different statuses which influences the runtime of the PI message, too. If a J2SE adapter engine is used, J2SE adapters are used instead of communication channels to define the inbound and outbound processing.

If a communication channel or J2SE adapter is in an inactive or erroneous state the PI messages of the particular interface cannot be processed (as the sender or receiver components cannot be determined). Thus it is essential to monitor the involved communication channels or J2SE adapters of a SAP PI interface with high frequency, to be notified about failures or unavailability in time.

 

Cloud Integration Content

It is possible to deploy, execute, and operate cloud integration content from the SAP Integration Content Catalog in the Advanced Adapter Engine.

The Integration Gateway component as well as messages related to the deployment of cloud integration content must be monitored.

 

Component Based Message Alerts (CBMA)

SAP Process Integration provides an infrastructure for alerting administrators and users in case a technical problem occurs.

  • Central configuration for each PI domain where users create alert rules.

    Users first need to create and configure the alert rules and their consumers in a dedicated configuration tool. This configuration information is stored and distributed using the Integration Directory.
  • A local Alert Engine that evaluates the alert rules and creates alerts.

    There is a local Alert Engine in each PI runtime component, the Integration Engine and the Advanced Adapter Engine. The local Alert Engine receives events from the runtime component. For each event, it evaluates the alert rules to determine whether an alert should be created. In case the Alert Engine generates an alert, it puts the alert in a local alert store. This local alert store contains one section for each configured consumer of the alerts.
  • Alert consumers receive the alerts, display them, and generate notifications via SMS, e-mail, or other methods.

    An alert consumer fetches the alerts from their respective store, processes them, and sends notifications as needed.

    Users can SAP Focused Run as one of the alert consumer. SAP Focused Run can process the raw alerts, aggregate them, and push them to an Alert Inbox, from which an administrator notified.

     

Technical Prerequisites

The following technical prerequisites have to be met in order to monitor messages in the ABAP system via ABAP proxy:

  • The managed system has SAP Basis release 7.00 or higher

The following technical prerequisites have to be met in order to monitor Component Based Message Alerts (CBMA):

  • Managed ABAP system has SAP Basis 7.31 SP04 and above
  • Managed Java system has XI ADAPTER FRAMEWORK 7.31 SP04 and above.

The following technical prerequisites have to be met in order to monitor the integration gateway component and cloud integration content in SAP PI:

  • SAP Focused Run 3.0 FP01

The following technical prerequisites have to be met in order to monitor PI messages in the SAP PI system:

  • Managed system has PI Basis release 7.11 SP06 or higher

For PI Java message monitoring the following prerequisites have to be met:

  • MESSAGING SYSTEM SERVICE 7.31 SP21
  • MESSAGING SYSTEM SERVICE 7.40 SP16
  • MESSAGING SYSTEM SERVICE 7.50 SP08

For older support packages you can implement the following patches to enable PI Java message monitoring: 

 

Software Component Support PackagePatch Level 
MESSAGING SYSTEM SERVICE 7.31SP 17 54 
SP 18 34 
SP 19 14 
SP 20 01 
MESSAGING SYSTEM SERVICE 7.40SP 12 53 
SP 13 34 
SP 14 14 
SP 15 01 
MESSAGING SYSTEM SERVICE 7.50SP 05 14 
SP 06 08 
SP 07 03 
SP 08 00 

Integration Monitoring Setup

Available Monitoring Categories

For Process Integration Monitoring, different monitoring categories are available:

  • PI Messages (ABAP): Collected from the ABAP business system (monitoring transaction SXMB_MONI)
  • PI Messages (Java): Collected for PI Java systems (PI message monitor)
  • PI Communication Channels: Collected for PI Java systems (PI channel monitor)
  • Cloud Integration Content: Collected for PI Java systems (PI Message Monitor and PI Component Monitor)
  • Component Based Message Alerts: Collected for PI Java and ABAP systems

For the category 'PI Messages (Java)' you can collect payload information via UDS attributes from the PI message and display this payload in the Integration & Exception Monitoring application in SAP Focused Run. You can then use this information to search for related messages in PI or CPI, related IDocs, or related web service calls. Find out how to set up the collection of payload information under Collecting Business Context for Integration & Exception Monitoring.

https://help.sap.com/doc/saphelp_nw74/7.4.16/en-US/2c/f0a3d4540c4c9a9af65139801ef826/frameset.htmAvailable Filter Options

You can collect all PI messages and channels or you can use a filter to restrict the data collection. The available filter options depend on the category selected:

PI Messages (ABAP)

  • Status Group: The status group of the message. Please use the input help to select a status group
  • Sender namespace: The namespace of the source of the message
  • Sender interface: The interface of the source of the message
  • Sender party: The communication party of the source of the message
  • Sender component: The component of the source of the message
  • Receiver namespace: The namespace of the target of the message
  • Receiver interface: The interface of the target of the message
  • Receiver party: The communication party of the target of the message
  • Receiver component: The component of the target of the message

PI Messages (Java)

  • Status Group: Status group of the message
    • Cancelled
    • Errors
    • Scheduled
    • Processed Successfully
  • Interface namespace: The namespace of the message
  • Interface name: The interface name of the message
  • Sender party: The communication party of the source of the message
  • Sender component: The component of the source of the message
  • Receiver party: The communication party of the target of the message
  • Receiver component: The component of the target of the message
  • UDS Attribute Name: User Defined Search criteria defined for these messages (syntax: Parameter Name=Parameter Value)

PI Communication Channels

  • Channel Name: The name of the channel
  • Party: If a party is maintained for the channel you can use it as a filter here
  • Service: The communication component of the channel

Cloud Integration Content

  • Status: Status of the message.  Use the input help to select a status.

Component Based Message Alerts

  • Consumer ID: A Consumer ID is generated for the SAP Focused Run system to read alerts. This Consumer ID will be added as a consumer for an alert in Message Alert Configuration in the PI system.
  • Collect UDS Attributes: If set to TRUE, user defined attributes values will be collected. If set to FALSE, user defined attributes will not be collected.

https://help.sap.com/doc/saphelp_nw74/7.4.16/en-US/2c/f0a3d4540c4c9a9af65139801ef826/frameset.htmAvailable Metrics

The following metrics are collected for the different Process Integration categories:

PI Messages (ABAP)

  • PI Messages in status ERROR for longer than N minutes: Indicates new PI messages in the status Error were found during the collection interval
    Metric parameters:
    • STATUS_GROUP (not changeable) = ERROR
    • OLDER_THAN_MINUTES = Only consider PI Messages older than [minutes]
  • PI Messages in status SCHEDULED for longer than N minutes: The number of new PI messages in the status Scheduled found during the collection interval
    Metric parameters:
    • STATUS_GROUP (not changeable) = SCHEDULED
    • OLDER_THAN_MINUTES = Only consider PI Messages older than [minutes]

PI Messages (Java)

  • PI Messages in status ERROR for longer than N minutes: Indicates new PI messages in the status Error were found during the collection interval
    Metric parameters:
    • STATUS_GROUP (not changeable) = ERROR
    • OLDER_THAN_MINUTES = Only consider PI Messages older than [minutes]
  • PI Messages in status SCHEDULED for longer than N minutes: The number of new PI messages in the status Scheduled found during the collection interval
    Metric parameters:
    • STATUS_GROUP (not changeable) = SCHEDULED
    • OLDER_THAN_MINUTES = Only consider PI Messages older than [minutes]

PI Communication Channels

  • Number of PI Channels in status ERROR: Indicates PI channels went into status ERROR during the last collection interval
    Metric parameters:
    • LAST_N_MEASUREMENTS = Only consider a channel if the last N measurements returned ERROR

Cloud Integration Content

  • Erroneous Messages Detected: Indicates new messages in the status Error were found during the collection interval
    • STATUS_GROUP (not changeable) = ERROR
    • OLDER_THAN_MINUTES = Only consider messages older than [minutes]

Component Based Message Alerts

  • Alerts detected for Component Based Message Rules: Indicate is alerts are detected and collected in the PI component

    Metric parameters:
    Status group(not changeable) =ERROR

Steps to be executed in PI System for Component Based Message Alerts

  • Configure Alert Rules in SAP NetWeaver Administrator. https://help.sap.com/doc/saphelp_nw74/7.4.16/en-US/2c/f0a3d4540c4c9a9af65139801ef826/frameset.htm
  • Add SAP Focused Run system as a consumer.
    • Open a browser and go to http://[host]:[port]/nwa to access SAP NetWeaver Administrator. Then choose: SOA → Monitoring → Message Alert Configuration. 
    • Select the relevant rule in Message Alert Configuration → General Tab → Consumers
    • Add SAP Focused Run as a Consumer. Click on “Add” button and add the Consumer ID which was generated in SAP Focused Run Configuration UI