Webservice to proxy - response back to webservice

[Former Member]

Hello expert,

I am working on webservice to proxy scenario. When request to create purchase order received by PI thru webservice, PI will do proxy call to create purchase order in ECC and send response back.

We don't want to send ECC response back to Webservice, but we would like to send positive response back as soon as PI recieve the message irrespective of what happens in ECC.

Need some advise.

thanks.

[baskar_gopalakrishnan2]

>We don't want to send ECC response back to Webservice, but we would like to send positive response back as soon as PI recieve the message irrespective of what happens in ECC.

One way of doing is after sending request to ecc, you can code in proxy as response in the same interface with single field element like mesg receiveed and map that response to soap response on the sender side. (in this case you dont really process the soap request in ecc directly. you do it at later or convenient time or after sending success transfer message). Basically you handle logic in abap proxy side.

Mapping 1 soap request to proxy request (Per business requirement)

Mapping 2 proxy response (status : messg received ) to soap response

Rest are all same. Basically you do SOAP (sender) to PRoxy (receiver) synchronous mode

If you dont want to pass the soap request message directly to ECC and within that timeframe want to send successful mesg from pI itself then you have to design to store the mesg temporarily. What will happen if your ecc is down? How do you handle that situation.

[Former Member]

Hi Bhaskar,

Thanks for the reply.

But we are using Standard ES and we don't want to change the implementation of that Enterprise Services.

Sending Application wants the response right away as soon as message was received by PI.

thanks,

[Former Member]

Not possible using the standard PI objects configuration. This is required because if any issue occurs during the processing of the message by the PI system (missing configuration objects, failing mapping, etc), the adapter will return an error 500 (internal error). If the WS returned a 200 or 202 CODE only for correct receiving of the message, this would be inaccurate.

You can try using ccBPM, triggering the send of a SOAP message to the caller application as soon as the process is started.