Show TOC

Procedure documentationAdapting Process Integration Scenarios Locate this document in the navigation structure

 

A process integration scenario generally contains references to different target objects that are subject to versioning.

  • Application components modelled within a process integration scenario can be based on product versions or product instances (“main instances”) defined in the System Landscape Directory (SLD).

  • A process integration scenario can refer to design objects from the Enterprise Services Repository (actions, service interfaces, operation mappings, integration processes and communication channel templates). These objects in general are assigned to different software component versions than the process integration scenario.

There are two different kinds of object references in a process integration scenario:

  • Relative object reference – target object is assigned to the same software component version as source object.

  • Absolute object reference – target object is assigned to another same software component version than source object

Further information: Object References in Process Integration Scenarios

If you perform a release transfer of a process integration scenario, the product versions of the application components involved, as well as all absolute object references, are not adapted. Therefore, a release transfer of a process integration scenario implies considerable manual rework of the same.

To overcome this issue, you can adapt a Component View of a process integration scenario and all included application components and object references using a wizard. The wizard allows you to adapt all application components of a process integration scenario interactively with regard to new product versions. Those elements that can be adapted based on the new settings are adapted by the wizard automatically. Those elements that cannot be adapted automatically can be specified interactively in manual steps.

Note Note

This function is also referred to as Process Integration Scenario Adaptation wizard.

End of the note.

Note Note

Note that adapting a process integration scenario, respectively, a Component View, has no impact on configured process integration scenarios. That means: when you have configured a process integration scenario in Integration Directory (for example, by using the model configurator), and you adapt the process integration scenario thereafter, you then also have to re-do configuration in Integration Directory.

End of the note.

This function supports the following use cases:

  • Adapting a Component View after a release transfer

    This is the standard use case.

  • Replacing product versions or product instances that do not exist any more in the SLD by those that are defined therein.

  • Transforming a template application component into an application component that is based on a product versions or product instance.

Procedure

  1. Open the process integration scenario, choose the Component View you like to adapt and choose change mode.

  2. In the object menu choose   Component View   Adapt  .

    The system checks if all referred objects exist in the Enterprise Services Repository.

    If a target object does not exist, an error message is displayed, and the wizard is stopped.

    In this case, you need to import the missing object into the Enterprise Services Repository first and start the wizard again.

  3. Choose Continue.

  4. Adapt the application components.

    To do that, specify the target version for each application component.

    The procedure depends on the application component type.

    • Application components is based on product version:

      By default, the input help offers all versions of products that “fit” to the original product version. The fitting product versions are determined from associations defined in the SLD. In case you don’t find a suitable target product (version) that way, choose All Product Versions. Then you can choose among all product versions that are defined in the SLD.

    • Application component is based on product instance:

      By default, the input help offers all product instances that “fit” to the original product instance. In case you don’t find a suitable target product instance (version) that way, choose All Product Instance Versions. Then you can choose among all product instance versions that are defined in the SLD.

    • Template application component:

      You have the following options:

      • External template application components cannot be changed.

        Note that, however, you can change the name of the template application component.

      • For internal template application components, the following applies:

        You can transform an internal template application component into an application component that is based on either a product version or a product instance. The input help offers all product versions, however, you can change the selection criteria so that all product instance versions can be selected (in case, you like to transform the application component into an application component that is based on a product instance).

  5. Choose Continue.

  6. Adapt the internal actions.

    In case you have changed the product version or product instance of the application component that contains the internal action, all object references to service interfaces are adapted automatically (with regard to the software component version that corresponds to the target product version). You need to perform no additional steps then.

  7. Adapt the external actions.

    For each external action you have to adapt the object references (to service interfaces) manually (in a separate dialog for each action).

    Note that external actions might be changed by this step and therefore also be put into the change list.

    Note Note

    The wizard uses the software component version you have chosen first as proposal for the following assignments.

    End of the note.
  8. Adapt the operation mappings.

  9. Adapt the channel templates.

    In general, for operation mappings and channel templates you need to manually adapt the software component version, because these are absolute object references.

    Note the following regarding the adaptation of design objects:

    If possible, the wizard offers suitable software component versions for the design objects to adapt. This is possible if the software component version of the design object is associated to the product version of the application component.

    However, for operation mappings, channel templates and service interfaces of external actions, in general the software component version might not be associated with the product version of the application component. In that case, you need to manually select the suitable software component version by using the value help.

  10. Adapt the integration processes.

    Integration processes that are assigned to a template application component are adapted automatically (relative object reference).

  11. Choose Finish.

    The assigned design objects are automatically saved and the process integration scenario is refreshed.

  12. A new status page opens where the success message and – if applicable – the relevant error messages are displayed.

  13. Activate your change list which contains all relevant objects.

Note that the wizard allows you to adapt objects modeled in the Component View, also in case the object does not exist in the Enterprise Services Repository. When a related error will be displayed at the end of your adaptation activities when you choose Finish.