Async-Sync Bridge (Request-Reply) in HCI

[#1]

Hi HCI Experts,

We're trying to build an iFlow in HCI that looks something like the Async-Sync bridge in PI. I understand that there's the Request-Reply pattern in HCI that could accomplish this, as discussed here . However, I'm getting no luck so far when trying to deploy the iFlow.

So the scenario is:

ECC IDoc (Async) -> HCI -> C4CWebService_Request (Sync) -> C4CWebService_Response -> HCI -> Custom Web Service in ECC

1. ECC sends an IDoc to HCI.

2. HCI takes care of the mapping and sending of the request message to the standard Web Service (WS) in C4C. The standard WS in C4C is Synchronous.

3. Now, the response of the standard WS in C4C must be sent back to ECC thru a Custom web service created in SOAMANAGER.

4. Response of WS from C4C is sent back to HCI where message mapping will take place and send it to the web service in ECC.

During deploy, I'm getting an error that says 'Receiver Channel cannot be configured for synchronous WSDL configuration.' Is it because the custom web service in ECC is synchronous and HCI cannot handle that?

Has anyone ever done this scenario with success?

Appreciate any inputs.

Thanks in advance.

Mark

[bhavesh_kantilal]

This is what my iFlow for the same requirement looks like,

- Instead of mappings, I have Content Modifiers to set my Payload.

- 1st Request Reply  ==> Equivalent to making a call to C4C in your case.

- 2nd Request Reply ==> Equivalent to making a call to ECC Webservice

- While the 2nd Request Reply makes the call to the Original System, it still has to be a Receiver System as Request Reply only works with Receiver System.

[markbernabe]

Thanks Bhavesh! It works. I just had to do some minor tweak in your iFlow and remove the connector from End back to the Sender. Otherwise, I'm getting an error 'Cannot model response back to the sender for asynchronous WSDL Configuration' perhaps because I'm using IDoc as the sender interface.

This is my final iFlow:

Thanks again!

[bhavesh_kantilal]

Yes indeed., As your IDoc WSDL does not contain  a response type it will not let you connect your request reply to the Send Step. Logically as well - If your Idoc did get an XML response it wouldnt know what to do with.

Have you also looked at the fact that the Idoc goes into error mode if your iFlow goes into error?

As the Idoc is sent over SOAP XML Port, until the iFlow does not complete processing and return a HTTP 200 OK, the IDoc continues to wait. So from ECC you can directly tell if the Iflow was successful or not. Its not the classical way and a learning in itself

Regards

Bhavesh

[markbernabe]

Hi Bhavesh,

Right, I've observed that as well. The IDoc going into status 02 when there's an error. Great stuff -thanks for all the additional info!

[bhavesh_kantilal]

Just a FYI, the flipside to this is the connection from ECC to HCI remains open till the Integration Flow is completed. So if your Integration Flow is a long running one, you might end up with Timeout issues! Just some food for thought!

Regards

Bhavesh