Use
You use the integration scenario editor to display and edit integration scenarios. In the interactive graphical work area, you can visualize the integration scenario as a Component View. In a component view, you can display the process flow of an integration scenario and assign other objects, which define how messages are exchanged.
You can define multiple component views for an integration scenario.
Prerequisites
You have created a new integration scenario or have opened an existing one.
If multiple component views are defined for one integration scenario, you can select one component view after you have opened the integration scenario editor (see: Defining Multiple Component Views for an Integration Scenario).
Features
In the work area of the integration scenario editor, the name of the selected component view is displayed in the Component View Name field. At the bottom of the screen area there is an interactive graphical interface that you can use to visualize the process flow of the integration scenario and to assign all the required objects (component view). The structure of the component view is shown schematically in the following graphic. It also includes the various context-sensitive areas and the most important functions that can be called from the context menu.
Component View and Context-Sensitive Areas
The integration scenario objects are represented in the integration scenario editor as follows:
· Application components are portrayed as colored vertical columns. The colors of the columns are defined according to color conventions.
· The application component column has a header where the role, the name of the product with its release identifier (product version), and the extended name are displayed.
· Actions are portrayed as white rectangles within an application component. The vertical progression of actions from top to bottom corresponds to the logical process flow.
· Sequences are shown as vertical lines with an arrowhead beside the subsequent action. The sequence determines the order in which the actions are executed (see Connection).
· Synchronous connections are shown as horizontal lines with an arrowhead at each end. The two actions involved are on the same level in the graphic. This shows that the actions that are connected by such a connection are synchronized chronologically.
· Asynchronous connections are shown as bent lines with an arrowhead beside the subsequent action. The two actions involved here are not on the same level in the graphic. The subsequent action must be beneath the source action. This shows that the actions that are connected by such a connection are independent of each other and are not synchronized chronologically.
Functions for Assigning Objects and Defining a Connection
To assign objects to an integration scenario, call the functions specified below from the context menu. To call a function, position the cursor on a particular area within the integration scenario. The individual context-sensitive areas are represented in the integration scenario (see above). To call the editor to display or change an object, double click the object in question in the integration scenario.
Functions for Application Components
· Context: Graphical area is empty
¡ Insert Application Component
· Context: Application component (colored column):
¡ Display/Edit Application Component
¡ Remove Application Component
Functions in Actions
· Context: Application component (colored column)
¡ Insert Action
· Context: A selected action
¡ Display/Edit Action
¡ Remove Action
· Context: Multiple selected actions:
¡ Remove Actions
Functions for Connections
· Context: Two selected actions
¡ Create Connection Between Selected Actions
¡ Display/Edit Connection Between Selected Actions
¡ Remove Connection Between Selected Actions
Functions of the Graphical Editor
· See Functions of the Graphical Editor
Additional Functions
· Define Multiple Component Views
· Check the Configurability of a Component View
· Print and Export the Component View
No comments:
Post a Comment