Powered By

Free XML Skins for Blogger

Powered by Blogger

Thursday, July 10, 2008

Designing Integration Scenarios Developing Business Logic

Purpose

You use an integration scenario to define the message exchange and message flow for collaborative processes. Normally, these are processes between different business partners that are generally coupled by the exchange of messages.

The integration scenario provides you with a central point of access for all objects that you require for semantic and technical integration, for example interfaces, mappings, and software components.

You can integrate an executable integration process into an integration scenario.

The information entered in an integration scenario during the design phase is used as follows:

· During the configuration phase to map the collaborative process to the current productive system landscape.

In this phase you specify the business systems of the business partners on which the application components are installed. In this phase the integration scenario provides you with a central point of entry for the definition of all receiver determinations. These routing relations define the flow of messages in the productive system landscape.
For more information, see Configuration.

You can configure an integration scenario easily and concisely by using the integration scenario configurator. In particular, the configuration of business-to-business scenarios is supported.

· In productive operation to simplify the execution and administration of collaborative processes.

Integration scenarios make the dependencies between the business partners and the separation of concerns transparent. As a result, the entire collaborative process is easier to maintain, more reliable and more stable.

Features

The Integration Builder constitutes an integrated development environment for the design of integration scenarios. You can do the following with the Integration Builder:

· Define the business partners involved in the integration scenario and their application components

· Model all interactions for which messages are exchanged between different application components

· Specify each individual message exchange by assigning them interfaces and mappings

The development environment for integration scenarios comprises two editors:

· Integration scenario editor

The integration scenario editor provides an interactive graphical work area that enables you to visualize the integration scenario process and how the objects used are related to each other. From the context within this editor you can navigate to the object editors of all objects used. The top-down and bottom-up design of integration scenarios is supported.

· Action editor

The action editor enables you to display and edit actions. Actions are activities within the integration scenario process that are not subdivided further.

This section is structured around the following questions:

· What is an integration scenario and how do the various components work together? For more information, see Integration Scenario.

· How do I develop an integration scenario with the Integration Builder? For more information, see Integration Scenario Design Environment.

· How do I model an integration scenario? For more information, see Guidelines for Modeling Integration Scenarios.

No comments:

Archives