Scenario Configuration

How you can contact us:

Technical Assistance

Request product support from SAP
Non-Technical Assistance

Request non-product support or provide feedback on SAP Support Portal site

Advanced Integration Monitoring Scenarios

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.

Create Scenario

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:

Open the Advanced Monitoring Application by clicking on the 'Integration & Cloud Monitoring' tile in transaction FRUN
Click on the configuration icon in the upper right corner of the Integration & Cloud Monitoring' application
In the configuration panel expand the 'Scenarios' tray and click on the pen icon in the upper right corner. This will open the 'Scenario Overview' view.
If your scenario is not on the list yet, click the 'Add' button to add it. If it is on the list, click on the scenario ID. The 'Details' view opens.
Enter the technical name and a description for your scenario.

Maintain Topology

Add Technical Components

In the 'Topology' step you create the topology for your scenario.

Click on the 'Node Selection' drop down
Check all technical components that are part of your scenario
Click the '+' button next to the drop-down
The select technical components will appear on the topology screen
You can add more nodes by repeating the steps 1 to 3
To remove a node: Click on the technical component and select 'Main Actions' → 'Delete Node'

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.

Add Alerts and Filters to Components

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

Click on the technical component
Click on 'Filter for Component'
You can copy filters already existing on component level via the button 'Copy Filter'
To create a new filter press the '+' button
Enter a filter name and select the monitoring category
Enter the required filters in the filter fields
Save your changes.

Add 'Alerts' to a Component

Click on the technical component
Click on 'Alert for Component'
Select the '+' button in the screen to the right the add a new alert
On 'General'
1. Select the alert category
2. Select the metric for the alert
3. Enter a sensible alert name
Click on 'Filter'
1. You can copy an existing alert filter for this component via the button 'Copy Filter' or create a new one
Click on 'Description'
1. On this tab you can change the standard settings for the alert, set up the notifications and adjust the alert description
Save your changes.

Create Paths for Messages between Components

To create a real landscape topology you have to create connections between the technical components.

Click on the technical component
Select 'Main Actions' → 'Add Link to...' → Select target component
To delete a link: click on the link and select 'Delete Link'

To include messages into this link, you have to add a filter:

Click in the link
Select 'Add Line Filter'
Enter a 'Filter Group Name' in the screen to the right
Click the '+' button to add a filter
Enter the filter name
Select the component (source or target of the link) for which categories the filter should be created
Select the monitoring category for the filter
Enter the required filters in the filter fields
Save your changes.

Create Paths for local Messages (Self-Links)

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.

Click on the technical component
Select 'Self Loop' → 'Self Link and Filter'
Click the '+' button in the screen to the right to create a filter
Enter a 'Filter Group Name'
Enter the 'Filter Name'
The component will be preselected
Select the monitoring category for the filter
Enter the required filters in the filter fields
Save your changes.

To remove a self link:

Click on the technical component
Select 'Self Loop' → 'Remove Self Link and Filter'

The filters can only be created for monitoring categories that are already set up for the selected technical component.

Flow Configuration

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:

Supported Patterns	Categories	Limitations
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.

Maintain Flows

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:

Click the 'Add' button to add a new flow
Enter a name and a description
Select the start component of the message flow from the 'Node Selection' drop-down and click the '+' button
Select the next component in the message flow from the 'Node Selection' drop-down and click the '+' button
Repeat step 4 until all component of the flow are added
Lines between the components are created automatically

For each component enter a filter that identifies the messages of this message flow:

Click on the component
Select 'Filter for Node'
Set up the filter in the screen to the right
You can only create a filter for monitoring categories that are already set up for the component.