A scenario in Integration & Cloud Monitoring of SAP Focused Run allows you to group point-to-point interfaces that belong to a more complex interface scenario. All connections that are part of a scenario can then be displayed together in a scenario topology. By adding filters to the connections you can define which messages and exceptions are in scope for a scenario and isolate their status information in the monitoring application.
By naming the filter group of a connection between components appropriately, you can add business-related information to your scenario. Knowing what exactly is sent via this connection will support the readability and understandability of the scenario for monitoring. This will simplify the communication between the business, functional support and technical support teams.
Before you can set up a scenario you first have to activate the monitoring for the components and integration categories in scope. Then you can create a scenario:
In the 'Topology' step you create the topology for your scenario.
After adding a component to a scenario you need to add filters to include messages in the scenario.
Filters allow you to filter which messages collected for a component are taken into account in the context of this AIM scenario. For example if you create a scenario for "Invoicing" you would only want to consider IDocs that are actually related to the Invoicing process in this scenario. However, outside of the scenario you might collect all IDocs for the technical component. With a filter you can restrict the considered IDocs.
You can create filters on component or on path level.
The alerts and filters can only be created for monitoring categories that are already set up for the technical component.
On component level you can add either filters or alerts. To learn more about the available filter fields and the available metrics for alerts for the single monitoring categories please check here.
Add a 'Filter' to the component
Add 'Alerts' to a Component
To create a real landscape topology you have to create connections between the technical components.
To include messages into this link, you have to add a filter:
When creating a scenario in Advanced Integration Monitoring it can be necessary to create a path from a component to itself, e.g. if IDocs are used for company internal invoicing and the sender and the target system are subsequently the same.
With SAP Focused Run 3.0 FP 02 it is now possible to create such a self-loop and add a filter to it to only include relevant messages.
To remove a self link:
The filters can only be created for monitoring categories that are already set up for the selected technical component.
Flows allow you to describe end-to-end message flows that run over several technical components. This is useful integrations consisting out of more than one point-to-point interface.
Currently supported end-to-end flows:
|PI → PI||PI Messages (ABAP), PI Messages (Java)||Split and Merge scenarios are not supported yet|
|IDoc → IDoc||IDoc|
|PI → IDoc||PI Messages (ABAP), PI Messages (Java), IDoc||IDoc sent from ABAP to PI are not supported as part of a flow|
|Cloud Integration → C4C / C4C → Cloud Integration||SAP Integration Suite, SAP C4C Messages||Split and Merge scenarios are not supported yet|
|ABAP WS → Cloud Integration / Cloud Integration → ABAP WS||SAP Integration Suite, Web Service Messages (ABAP)|
|ABAP WS → C4C / C4C → ABAP WS||SAP C4C Messages, Web Service Messages (ABAP)|
For these end-to-end flows, you can see a status summary and the average duration and status over time for the whole flow in the E2E Monitor of the Advanced Integration Monitoring application.
It is optional to create end-to-end flows for a scenario.
To be able to maintain flows you have to change the mode for the UI from 'Basic' to 'Expert'. This is done using the drop-down field in the upper right corner of the configuration screen. After switching to 'Expert' mode you will now see the step 'Flows (Optional)'.
To create a flow go to the step 'Flows (Optional)' in the scenario configuration:
For each component enter a filter that identifies the messages of this message flow: