Use
You can define multiple component views for an integration scenario.
This is recommended if you want to have multiple combinations of product releases in an integration scenario, or want to permit multiple variants of an integration scenario.
The application components of the various component views are linked to each other by the uniqueness of the assigned roles. This means that you can trace the history of particular application components when using various different release combinations. You can also give the different component views different names.
Prerequisites
You have opened an integration scenario (see: Integration Scenario Editor).
Activities
Adding an Additional Component View to an Integration Scenario
You can add an additional component view to an integration scenario that is already based on a component view. For this purpose, you can copy the existing component view and use this copy for the new component view.
...
1. From the integration scenario editor toolbar, choose Component View ® Copy.
To define more than one component view for an integration scenario, you must have specified a role name for every application component in the existing component view.
2. The preview screen area on the left of the graphical editor displays all the existing component views. To display and edit a component view in the graphical editor, select a component view from this preview area.
3. You can enter a name for the component view in the Component View Name field.
Display all Component Views of the Integration Scenario
To display all existing component views in the preview area, from the integration scenario editor toolbar, choose View ® Show/Hide All Component Views. To select a component view and then display and edit it in the graphical editor, select a component view from this preview area.
Deleting a Component View
To delete a component view of an integration scenario, from the integration scenario editor toolbar, choose Component View ® Delete.
No comments:
Post a Comment