Show TOC

Integration VisibilityLocate this document in the navigation structure


In a typical SAP landscape, lots of SAP and non-SAP applications are integrated and exchange information via different message-based middleware technologies. If an error occurs during the message processing, the message results in an error state and can be reprocessed once the issue for the error has been resolved. Such an issue could be a technical one, for example, the receiver system is not responding. In many cases it is actually an application-related issue - for example, the payload of the message is incorrect, a mapping value is not maintained correctly, and so on - and the issue needs to be resolved manually.

To be aware of the error situation, integration administrators typically use monitoring and alerting frameworks provided by the middleware itself. Once they identify the problem, they might need to contact some application support team to help with the application-related errors. Every middleware technology provides its own monitoring and alerting framework, and most of them are non-central ones, which costs a lot of effort on the administration side. Moreover, if a message goes through multiple middleware technologies, an administrator might have to look into multiple monitoring tools in order to be able to identify the root cause of the issue.

Integration Visibility is a technical foundation that discovers message flows and enables consumer applications to subscribe and consume monitoring events for a selected set of discovered message flows. This includes all A2A and B2B scenarios in the monitored landscape.

The diagram below illustrates the main components in Integration Visibility:

When an asynchronous message is sent from one system to another, this message is persisted in a message storage in the middleware component to guarantee the necessary quality of service. Integration Visibility is built on top of the existing message storage, and provides an abstract view on messages going through middleware technologies like PI, ALE, BPM, and Web services. It reads the message storage to gain details on a message, such as its status, payload attributes, and so on. This information is gathered by Integration Visibility consumers, which correlate it to recognize instances of message flows. Then the consumers process the information for these instances for monitoring, reporting, alerting, and other purposes, and present it to the users.