Hard Coded Message Respone for Asynchronous webservice interface

[vishal_javalkar]

Hi PI Experts,

We want to design a asynchronous web service interface in PI, however we want to send a hard coded response message to the caller of the web serviceas soon as the message is received in PI soap adapter and continue the further PI message processing as a asynchronous interface.

Does anyone have idea on how to achieve the above requirement without sync-async bridge ?

Is there a way we can achieve it by using any standard or custom adapter modules ?

Regards,

Vishal

[iaki_vila]

Hi Vishal,

I think, i am not sure, the acknolewdgments only works for the SOAP receiver and not for SOAP sender (check these notes : 856597 - FAQ: XI 3.0 / PI 7.0/7.1/7.3 SOAP Adapter, the question about Acknowledgment 1821649 - XMBWS.GenerateSysAck is set to false by default.)

However, when the sender system calls async, it will receive a HTTP 200, you can debug the call with SOAPui, i think they can catch this value as SOAPui does.

If you want to send your own response, i think you should do your own module to add to the sender SOAP.

Regards.

[vishal_javalkar]

Hi Inaki,

Can you please provide more details on implementing it via module ? I am not sure how can we respond back using the same caller thread.

Regards,

Vishal

[iaki_vila]

Hi Vishal,

If you develop you own module you can place it in the SOAP module processing sequence. Inside the module you can hardcode an asynchronous call to the sender.

For own module development, you have an example in this wiki: Custom Adapter Module Development - SAP PI 7.1 - Netweaver Technology - SCN Wiki

From google you can find some examples to do a simple http call, even from scn with a bit more complicate structure http://scn.sap.com/community/pi-and-soa-middleware/blog/2006/11/20/webservice-calls-from-a-user-defi...

If you don't find any better idea, from my point of view the http 200 proposed by Praveen and me seems to be the easiest way, you can try first to do the http call from an UDF and later do your own module adapter because this can be a bit more tedious

Regards.

[former_member181985]

Hi Vishal,

In general, the SOAP calling application system will receive a HTTP status code 200 OK, though SOAP sender channel in PI is asynchronous in nature.

Is there any reason, calling application not considering this 200 OK status code?

Best Regards,

Praveen Gujjeti

Message was edited by: Praveen Gujjeti

[vishal_javalkar]

Hi Praveen,

We are migrating to PI from other middleware , where with old middleware they send a response tag and we want to continue the same without causing any change at the caller end.

Regards,

Vishal

[Former Member]

Any specific reason that you dont want to use sync-async bridge?

Regards

Osman

[vishal_javalkar]

Hi Osman,

The interface is performance intensive so we want to avoid any delay while sending the response back. Also, as it will a hard coded message it doesn't technically add any value too.

Regards,

Vishal