Copy synchronous response to separate asynchronous mapping

[#1]

Hi Folks

I have a integration scenario challenge, that I was sure could be implemented technically. But after searching the communicty and google in general, I still havent found a solution. Therefore I would like to hear if any of you have any input to this challenge..

The requirement is pretty simple: System A make a synchronous request to System B. Response should be synchronous returned to System A, but System C should get a asynchronous copy of the response.

Illustrated like this:

However I cant find any way of copying the response and forward it to the asynchronous integration.

Anyone having any suggestions to how this can be achieved.. (Or if it is possible at all)

Thanks a lot for your input.

/Chris

[Muniyappan]

You can also split it into two interfaces, instead of one. this can save the System A's waiting time.

System A to System B ====> sync scenario

and create one more async scenario

System A to System C =====> Async Scenario

In the sender proxy coding(A), once you get the response from system B, trigger 2nd asynchronous interface.

[Cortex2k]

Thanks Muni

So is it possible to use the response data exactly as is when triggering the async call from system A to System C?

Thanks

Chris

[Muniyappan]

Yes. It is possible to do that.

[apu_das2]

This will add additional failover points apart from connectivity issue. Like Supoose your first scenario is successful and you second scenario is failed. So data mismatch in system A and C.

If you handle that in the response message then if mapping will be successful means if system C will be updated then there are very less chances to fail updation of system A with the response as it is single sync scenario. Though there are chances of failure here as well but definitely failover points and pipeline steps will be less.