on 10-31-2011 6:58 AM
Hi all
We have a proxy <-> PI <-> WS scenario
We use "Do not use SOAP envelope" in order to create a specific header info for the WS.
The reply from the WS puts the response (xml) in the payload attachment.
Everything is ok in PI
But the generated proxy on the ERP side fails/throws exception because of missing payload (expected as main document and not as attachment).
How can we get this corrected?
I have tried to use the PayloadSwapBean module without luck (but perhaps I'm missing how to fill out the keyname and keyvalue - someone having an example showing how to use this module in this situation?)
Perhaps there is a solution/option when generating the proxy?
All help is very welcome
Thanks
Peter
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks for the input.
We receive the following RAW-format reply from the provider.
Any ideas of the values KeyName and KeyValue in order to get the envelope treated as the main document and not an attachment?
HTTP/1.1 ....
Date: Tue, 01 Nov 2011 06:50:19 GMT
Server: Microsoft-IIS/6.0
X-Powered-By: ASP.NET
RequestTime: 00:00:00.9687438
Cache-Control: no-cache, no-store
Pragma: no-cache
Expires: -1
Content-Type: text/xml; charset=utf-8
Content-Length: 1182
<?xml version="1.0" encoding="utf-8"?><env:Envelope
xmlns:env="http://schemas.xmlsoap.org/soap/envelope/"><env:Header>....</env:Body></env:Envelope>
Thanks
Peter
User | Count |
---|---|
81 | |
10 | |
10 | |
9 | |
7 | |
6 | |
6 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.