Show TOC

Procedure documentationWorking with Process Integration Scenario Locate this document in the navigation structure

 

You use this procedure to generate one or more integration flows that contain configuration objects obtained from the definition of process integration scenarios. The process integration scenario is a design object in ES Repository that defines the message exchange and process flow required to realize an end-to-end business. It represents a chain of interaction between two units within the landscape or business partners across landscape and contains definition of interfaces, mappings and channel templates. The process integration scenario comprises of component views and their corresponding application components.

Component View

It provides a view based on the process flow that shows logical interaction between application components.

Application Component

It is a logical representation of a participant in a process integration scenario. It is described by roles such as vendor or customers and have corresponding range of business tasks. In the Integration Directory, you assign business systems to handle the tasks of the application component.

Modifying and Regenerating Integration Flows from Process Integration Scenario

You can also use this procedure to generate new integration flows or modify existing integration flows from the process integration scenarios that are updated in the ES Repository. You want to modify the configurations of a process integration scenario when:

  • A new component view is added to the process flow of the process integration scenario in ES Repository

  • New connections have to be configured for an existing component view

  • The existing connections of a component view have to be updated

Prerequisites

You have defined a Process Integration Scenario in ES Repository.

For more information, see   http://help.sap.com/nw731/   Application Help   Function-Oriented View (English)   Process Integration   Enterprise Services Repository & Registry   Managing Services in the Enterprise Services Repository   Defining Design Objects for Mediated Communication   Defining Process Integration Scenarios  .

Procedure

  1. In the main menu, choose   Process Integration   Generate Integration Flows  .

  2. In the Generate Integration Flows from Process Integration Scenario wizard, select a process integration scenario and choose Next.

  3. Select a component view of the process integration scenario to view the participating application components.

  4. Assign one or more communication components to each of the application components.

  5. If a sender system of one landscape communicates with multiple receiver systems of another landscape, select the option to allow a Recipient List element in the integration flow.

    Note Note

    If you do not select this option although a sender system of one landscape communicates with multiple receiver systems of another landscape, integration flows with Point-to-Point pattern is generated that represent individual connection of the sender system with each receiver system.

    End of the note.
  6. Choose Next.

  7. Enter names for all the connections between the systems you have assigned in the previous step.

    Note Note

    The names that you provide to each connection is the integration flow name that is generated with all the configurations defined in process integration scenario.

    End of the note.
  8. If the integration flows connect two systems across landscapes, and you want to assign header mapping or virtual receiver at this stage, choose Next else choose Finish to assign it in the Model Configurator.

  9. Choose Finish to initiate integration flow generation.

  10. If you want to modify the generated integration flow, follow the steps below:

    1. Identify the folder that maintains the integration flows generated from a process integration scenario.

    2. Right-click on the folder and choose Modify and Regenerate Integration Flowsfrom the context menu.

    3. Repeat step 2 to step 6.

    4. Choose Finish to regenerate integration flows with updated configurations.