(is) configuring a bpm scenario using fork and correlation

8/10/2019 (is) Configuring a BPM Scenario Using Fork and Correlation

1/26

XI - BPM Scenario using Fork and correlation

By M.Leela Ratnam, Satyam Computer Services

INTRODUCTION

We will design and configure a BPM scenario-using Fork, i.e. we will send messages to XI and XI will in turnmerge the two messages to a single message. In our scenario both sender and receiver are Asynchronousapplications. BPM was required for merging of two files. By this scenario you will know how to use Fork andcorrelation in BPM.

Process Flow of the scenario is given below.

We will send two files as input. These two files get merged into a single output. In the below diagram, File 1and File2 are separate files. These two files got merged into a single file.

INTEGRATION REPOSITORY

Create the software component in SLD and import the software component in the Integration Repository.

Create the new namespace.

DATA TYPES

Create data type for File1.


2/26

Create data type for File2.

Create the output data type.

MESSAGE TYPES

Create the message types for the corresponding data types you have created above.


3/26


4/26

MESSAGE INTERFACES

Create outbound Asynchronous interface for File1.

Create outbound Asynchronous interface for File2


5/26

Click here to continue...
http://www.saptechnical.com/Tutorials/XI/BPM/Fork2.htmhttp://www.saptechnical.com/Tutorials/XI/BPM/Fork2.htmhttp://www.saptechnical.com/Tutorials/XI/BPM/Fork2.htm


6/26


...Previous

Create the Inbound Asynchronous interface for the output file.

As we are using BPM, we need to create the abstract interfaces for the messages which we will use in BPM.It is so because Integration Process will not understand outbound/inbound interfaces. It will onlyunderstand Abstract Interfaces. The Abstract Interface is nothing but any other interface but it does not haveany direction.

Create the abstract interface for the File1.


7/26

Create the abstract interface for File2.

Create the abstract interface for the output file.


8/26

MESSAGE MAPPINGS

Create N: 1 message mapping as the source is having 2 messages and the target is having 1 message.

The signature tab should be like below screenshot. (in 7.0, it is Message tab)


9/26

INTERFACE MAPPINGS

Interface mapping is created based on the outbound asynchronous abstract interfaces and inbound

asynchronous abstract interface.

INTEGRATION PROCESS

Create the integration process as below.

GRAPHICAL WORK FLOW DIAGRAM


10/26



11/26


...Previous

CONTAINER ELEMENTS

The container elements are the variables used in BPM. We cannot use directly the abstract interfaces. Sowe need container elements.

Properties:

The Receive step is used to receive messages. Here we are having two input messages, so we need to

have two receive steps. We will two receive steps in Fork. You use a fork ) when you want to continue aprocess in branches that are independent of each other, for example, to communicate with two systems thatare independent of each other. The branches of the forkjoin in a union operator.

You can specify the required number of branches and then define whether the process must run through allbranches, or just a particular number of branches. Furthermore, you can define an end condition forthe fork.

CORRELATION

A correlation enables you to identify objects that belong together, for example, a quotation and the relevantsales order. This involves correlating the objects by using one or more common elements, for example, thequotation number. When you define a Workflow, you can specify the object that the Workflow must wait for,without having to enter the ID of the object.

You define a correlation with the correlation editor. In the correlation editor, first you need to define thecorrelation name. Then Mention the container elements under correlation container. There you have to givethe common field which is having in both the input files. Select the input messages interfaces in the involvedmessages. In the properties you need to mention the value. Select the value from the expression editor.

Defining a Correlation


12/26


13/26

Receive Step2

Transformation Step

If you want to collect messages, split messages you need to use Transformation step after the receive stepthat refers to N: 1 Interface Mapping or 1: N Interface Mapping created.

Send Step

Once messages are received and processed, these processed messages are to send by the BPM usingSend Step.


14/26

Save all the objects and activate it. Integration Repository part completed.



15/26


...Previous

INTEGRATION DIRECTORY

CONFIGURATION SCENARIO

Create the Configuration Scenario.

BUSINESS SERVICES

Create the Business Component. In that select the Sender interfaces and receiver interface.

Import the Integration process which you have created in the Integration Repository.


16/26

COMMUNICATION CHANNELS

Create the sender communication channel for File1.


17/26

Create the sender communication channel for File2.


18/26

Create the Receiver communication channel for Output File.


19/26

SENDER AGREEMENT

We need to have two sender agreements as we are giving two input files as input.

Create the sender agreement for file 1.

Create the sender agreement for file 2.


20/26



21/26


22/26

Create Receiver determination for the Integration Process to the target. Here select the sender service as

Integration Process and the receiver service as business service.

INTERFACE DETERMINATIONS


23/26

We need to have three Interface determinations. Two for the source to the BPM and the other for BPM to the

target

Create Interface determination for the source to the Integration Process. Here select the sender service as

business service and the receiver service as Integration Process

Create the Interface determination from the sender service to the Integration Process.

Here no interface mapping is specified since the BPM itself will contain the mapped data.

Create the Interface determination from the sender service to the Integration Process.

Create Interface determination for the Integration Process to the target. Here select the sender service asIntegration Process and the receiver service as business service

Create the interface determination from the Integration process to the receiver service.


24/26

RECEIVER AGREEMENT

Create the Receiver Agreement for the Target.

Activate all the objects.

TESTING

INPUT FILE

File1


25/26

File2

OUTPUT FILE

SXMB_MONI


26/26

Graphical workflow log

(is) configuring a bpm scenario using fork and correlation

Documents