PI 7.3 EHP1 Async-sync bridge using IDOC_AAE

Hi,

I have a requirement to send Purchase Order idocs from ECC 6 to a third party Vendor. This has to be implemented using an Idoc (ORDERS05) at the ECC end and a synchronous web service at the Vendor. We are running PI 7.3 EHP 1 on single stack and the idoc's are being processed by the IDOC_AAE adapter. The response from the webservice should be routed to a File Adapter Receiver.

I have followed the instructions in the blog by Sreenivas Veldanda.

http://scn.sap.com/community/pi-and-soa-middleware/blog/2013/03/25/requestresponse-bean-for-idocaae-adapter

I first configured the scenario using the async ORDERS05 idoc in the operation mapping. Once the directory configuration was complete I then amended the Operation Mapping to use a synchronous Service Interface for the idoc as per the instructions in the blog. All interface objects are active and the Sendor Idoc Communication Channel has been configured using the parameters below.

The idoc adapter functions correctly in other non-synchronous scenarios.

When the idoc is sent from ECC it is correctly routed through the correct synchronous operation mapping. However an error occurs at the receiver SOAP adapter where the Vendor web service returns a HTTP 403 forbidden.

This has been successfully tested using a test rig from SOAP UI. The testrig uses the same operation mapping as the ECC and the same Receiver Communication Channel. The only difference is that the sender is a SOAP Communication Channel. The same idoc has been used to test this both from ECC and the SOAP UI test rig so the error is not data related.

Unfortunately the third party Vendor is not able to provide any diagnostic information as they do not persist messages in error. The only clue they were able to give me is that the error below.

Causedby:
com.wm.lang.xml.WMDocumentException:InvalidValue:html
expected, 'Envelope'

I'm not sure what would cause this as we have successfully sent messages through this operation mapping and receiver SOAP Communication Channel using SOAP UI.

If anybody has successfully set up a similar scenario it would be useful to know exactly how they configured the sender and receiver communication channels. Any other thoughts would be gratefully received.

Thanks

Ian