-
Request for existing cases, user IDs, Portal navigation support and more
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.