Guidelines for Modeling Integration Scenarios

This section gives you an overview of what you should note when modeling integration scenarios and supports you when designing them. Furthermore, it provides you with background knowledge about the modeling concept and design decisions in the Integration Builder (Integration Repository).

Targets of Modeling

An integration scenario completely models the exchange of messages for a collaborative process and provides an overview of the process flow. The advantages of defining integration scenarios in the Integration Builder (design tool) are as follows:

· The integration scenario provides you with an overview of the process and the process flow.

· The integration scenario groups together all objects that are involved in this process: interface objects, mapping objects, and executable integration processes from the Integration Repository, and product versions from the System Landscape Directory.

You can access all of these objects from the integration scenario.

· The integration scenario contains all design time information about the process that is required for its configuration. If you have defined an integration scenario, you can use it as a template for configuration. This enables you to automate the creation of the relevant objects as much as possible. In the case of very complex collaborative processes, integration scenarios are the only way of retaining an overview over the configuration.

Use the above as your starting point when defining and modeling integration scenarios.

The sections below contain detailed information about what you must note when modeling the individual components of the integration scenarios:

· General Modeling Concept

· Modeling Integration Scenarios

· Modeling Application Components

· Modeling Actions

· Modeling Connections

· Modeling Process Variants of an Integration Scenario