Show TOC

Guidelines for Modeling Process Integration ScenariosLocate this document in the navigation structure

Use

This chapter gives you an overview of what you have to take into consideration when modeling Process Integration scenarios and supports you with designing your Process Integration scenario. In addition to this, you get a background introduction to the modeling concept and to design differences in the Enterprise Services Builder (Enterprise Services Repository).

Modeling Aims

A Process Integration Scenario maps the entire message exchange for a collaborative process completely and gives an overview of the process flow. You have the following advantages when defining Process Integration scenarios in the Enterprise Services Builder (Design Tool):

  • The Process Integration scenario provides an overview of the process and process flow.

  • The Process Integration scenario summarizes all objects that are invovled in the process together: Interface objects, mapping objects and executable integration processes from the Enterprise Services Repository, and product versions from the System Landscape Directory.

    You can access all of these objects from the Process Integration scenario.

  • The Process Integration scenario contains all design time information about the process that is required when configuring the process. If you have defined a Process Integration scenario, you can used it as a configuration template. This then largely automates the creation of the relevant objects. Using Process Integration scenarios for more complex collaborative processes is the only option for making the configuration easier to understand.

These targets are the starting point when defining Process Integration scenarios and have to be taken into consideration in the modeling.

Below you will find more details on what you have to consider when modeling the individual components of Process Integration scenarios: