Powered By

Free XML Skins for Blogger

Powered by Blogger

Thursday, July 10, 2008

Designing Integration Scenarios Action

Definition

An action represents a function within an application component that is not subdivided further. Actions subdivide the process flow of an integration scenario.

Actions are shown as white triangles in the integration scenario editor. The vertical progression of actions from top to bottom corresponds to the logical process flow.

An action is an independent design object of the Integration Builder. This means that actions are defined independently of integration scenarios. Thus you have the option of reusing actions in different integration scenarios.

Use

Usage Type for Actions

Label

Usage Type

Internal Actions

Defined for a ‘separate’ software component version.

You can use internal actions in application components (of type Product Version or Main Instance) that (by using the product version) contain the same software component version in which the action is implemented.

External Actions

Defined for a software component version of a partner or for templates.

You can use external actions in application components (of type Template or Product Version) that (by using the product version) contain the same software component version in which the integration scenario is implemented.

If you want to use an action to represent a function that is already installed in the product of the application component, use an internal action.

If you want to use an action to represent a function that is not yet provided by the product of the application component, use an external action.

In this way, you can enter functions in the integration scenario (for example, for communication parties) that are not yet provided by the product version of the application component.

For more information, see the modeling actions section.

All interfaces associated with an action are assigned to that action in the Integration Builder.

The exchange of messages between components takes places between two actions from different application components. The interfaces used in the exchange of messages are assigned to the two actions involved.

No comments:

Archives