Show TOC

ActionLocate this document in the navigation structure

Definition

An action represents a function of an application component that is not subdivided further. Actions are divided into the process flow of a Process Integration scenario.

Note

Actions are represented as white squares in the Process Integration Scenario Editor . The vertical line from the top to bottom corresponds to the logical process flow.

An action is a standlone design object of the Enterprise Services Repository, this means actions are defined independently from Process Integration scenarios. In this way it is possible to reuse actions in different Process Integration scenarios.

Use

Type of Use of Actions

Name

Type of Use

Internal Actions

Defined for an "own" software component version.

Internal actions can be used in application components (of type Product Version or Main Instance ) which (using the product version) contain the same software component version where the action is also implemented.

External Actions

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

External actions can be used in application components (of type Template or Product Version ) which (using the product version) contain the same software component version where the Process Integration scenario is also implemented.
Recommendation

Use an internal action if you want to map a function that is already installed in the product of the application component with an action.

Use an external action if you want to map a function that is not (yet) provided by the product of the application component with an action.

In this way it is possible to map functions (for example, for communication partners) in a Process Integration scenario that are not yet provided by the product version of the application component.

For more information on this distinction, see Modeling Actions .

All the interfaces that are connected with the function of the action are assigned to an action in the Enterprise Services Builder.

The cross-component exchange of messages takes place between two actions from the different application components. The interfaces used for the message exchange must be assigned to both of the actions involved.