0% found this document useful (0 votes)
2K views9 pages

Multicast - CPI

The document discusses the multicast pattern in SAP Cloud Platform Integration. It describes multicast as sending copies of the same message to multiple routes either in parallel using a parallel gateway or sequentially using a sequence gateway. It provides two examples of how multicast can be used - to send a message to multiple receivers or to provide the same message to different branches of an integration flow that require the same message contents. Join and gather steps are used to collect the messages from different branches into a single message.

Uploaded by

Rajesh Kumar
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
2K views9 pages

Multicast - CPI

The document discusses the multicast pattern in SAP Cloud Platform Integration. It describes multicast as sending copies of the same message to multiple routes either in parallel using a parallel gateway or sequentially using a sequence gateway. It provides two examples of how multicast can be used - to send a message to multiple receivers or to provide the same message to different branches of an integration flow that require the same message contents. Join and gather steps are used to collect the messages from different branches into a single message.

Uploaded by

Rajesh Kumar
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 9

OM

Defining Multicast
You can use the Multicast step to send copies of the same message to multiple routes. You can
send copies to all routes at once using Parallel Multicast or in an order of your choice
using Sequential Multicast. This allows you to perform multiple operations on the same message in
a single integration process. Without Multicast, you needed multiple integration processes to
perform this task.

1. In the palette, choose    Multicast.

1) https://blogs.sap.com/2015/01/06/blog-3-multicast-pattern-in-integration-flows-hci-pi/

The Multicast pattern allows to route the same message to a number of endpoints and process them
in a different way.

How to Use the Multicast Pattern in SAP Cloud Platform Integration?


There are two variants of the Multicast:

1. Parallel Gateway: All branches of the gateway are executed in parallel.


2. Sequence Gateway: Branches are executed in the order specified in the Properties tab.

To understand the multicast pattern better, I shall take the example an Integration Flow and insert a
Content Modifier step with a sample XML Payload in its body (shown below). In addition, I shall use
a simple mapping step that converts the price and currency from Dollars to Euros.
What ways can I use the Multicast pattern?

In Integration projects so far, we have seen its usage in the following two ways:

Use case 1: Send the message to multiple receivers. A simplified integration flow is shown below.
Use case 2: Multiple branches of the integration flow requires the same message contents

There are cases when you require the same message in different branches of the integration flow.
This is a pattern also observed in the SuccessFactors scenario integration with 3rd party systems. In
this case, you have to use the Join and Gather step. This shall collect all messages from different
branches into one message.Example below:
Note: You have to use the Join + Gather step together. A Gather step alone shall not work.
The Gather step enables you to merge messages from more than one route in an integration
process. You define conditions based on the type of messages that you are gathering using the
Gather step. You can choose to gather:

1. XML messages of different format


2. XML messages of the same format
3. Plain text messages

Based on this, you choose the strategy to combine the two messages:

1. XML messages of the same format, you can combine or specify the XPath to the node at
which the messages have to be combined.
2. XML messages of different formats, you can only combine the messages
3. Plain text messages, you can only specify concatenation as the combine strategy

So, here I want to combine all the “<part>”nodes and group it under the main “Mobile_menu” node.

Understanding the aggregation strategy can get a little tricky. I would recommend playing around it
with different values to get a hand on it.

You might also like