The current blog is part of a blog series where I describe how to implement different asynchronous integration scenarios using the pipeline concept on Cloud Integration. In the previous blog post, I described an interface split scenario resulting in ...
The current blog is part of a blog series where I describe how to implement different asynchronous integration scenarios using the pipeline concept on Cloud Integration. In this blog, I like to describe how to apply the pipeline concept for an integr...
The current blog is part of a blog series where I describe how to implement different asynchronous integration scenarios using the pipeline concept on Cloud Integration. In the previous blog post, I described a point-to-point scenario. In this blog p...
The current blog is part of a blog series where I describe how to implement different asynchronous integration scenarios using the pipeline concept on Cloud Integration. In the previous blog post, I described a multicast scenario. In this blog post, ...
The current blog is part of a blog series where I describe how to implement different asynchronous integration scenarios using the pipeline concept on Cloud Integration. In the previous blog post, I described a generic use case with multiple receiver...
if you can't sort out the xpath, you may only define one condition for the first receiver, the one containing the string, and then use default receiver option for the second receiver if receiver can't be determinedAlex
We do not provide a regression test tool in Cloud Integration, for the migration use case we have an agreement with two partners that allows you to use either of their tools for a time period of 12 months for free, see https://community.sap.com/t5/te...
try this groovy script assuming that the complete file name path is stored in the exchange property completePathimport com.sap.gateway.ip.core.customdev.util.Message;import java.util.HashMap;def Message processData(Message message) {//Bodydef body = ...