SOAP Adapter XI 3.0 - HTTP 200 response fails

We have a scenario where a request message is sent successfully to a URL by the SOAP Adapter.
However, the response message has an HTTP response of 200 (meaning ok) which is not handled correctly by the
SOAP Adapter.
The error text shown in SXMB_MONI is:
com.sap.aii.af.ra.ms.api.DeliveryException: Failed to call the endpoint HTTP 200 OK
Is there something I am missing in the configuration to allow HTTP responses in the SOAP Adapter ? It is very odd that the SOAP Request works fine, but the SOAP Response does not.
Any ideas anyone ?
Kind regards
Colin.

Hi Bill
1. synchronous out / in
2. yes
3. working fine
following the way out to the elocateserver system is working fine.
The soap is working and the responce from the elocteserver is fine . But when the message is pick put the Timeout show up.
below is the Responce from elocateserver to xi
Hope this will help you
thanks olaf
Help
!http://sapnt09:50200/sap/public/icman/img/theme.jpg|alt=SAP|width=122 height=61 border=0 |src=http://sapnt09:50200/sap/public/icman/img/theme.jpg!
500 Connection timed out
Connection timed out (-5)
Error:
-5
Version:
6040
Component:
ICM
Date/Time:
Sat Oct 16 06:13:25 2004
Module:
icxxthr.c
Line:
2556
Server:
sapnt09_M64_02
Detail:
Connection to partner timed out
© 2001-2003, SAP AG

Similar Messages

No SOAP Envelope but 1 {'}Values; HTTP 200 OK

Hi Experts,
I am configuring a scneario IDOC to SOAP , Asynchronous call to an https url that is available through internet.
When I try to post message to this url. I am getting following error:
SOAP: call failed: java.io.IOException: No SOAP Envelope but 1 {'}Values; HTTP 200 OK
in SOAP Adapter Log. Due to this error the message is set to NDLV.
I am using PI7.1
My Receiver Channel configurations are as contain
the third party url https://target with username password authentication. I have also imported client certificates.
Webservice host says its a problem with PI system and SAP says that its issue with Webservice.
Please let me know how can I resolve this issue. Am I missing something in my configuration. This is kind of a burning issue currently any help will be appreciated.
Regards,
Raj

Hi Raj,
This looks strange. If the error text is telling the truth, your SSL connection was working and you could even reach some service that returned HTTP 200 OK. But this service didn't return a SOAP response. I don't know what 1 {*} Values means. It sounds broken to me. You can open a ticket.
But the reason why you didn't get a valid SOAP response (either a good one or a fault) is probably that your target URL is incorrect. Verify the URL and run the scenario with the relevant components (refer to the SOAP adapter FAQ note) on DEBUG. The default trace file should give you more information about this apparently corrupted response.
Best regards, Yza

SOAP adapter: port, logging/tracing, http/https

Hi,
several questions concerning SOAP adapter:
SAP XI 3.0 SP19 used.
Scenario 1:
SOAP request adressing J2EE port
http://host:8000/XISOAPAdapter/MessageServlet?channel=Partner:Service:SOAPSenderChannel
Scenario 2:
SOAP request adressing ABAP port
http://host:50000/XISOAPAdapter/MessageServlet?channel=Partner:Service:SOAPSenderChannel
Question 1:
What happens with a SOAP request adressed to the ABAP port?
Obviously it is forwarded to the J2EE port but where is this forwarding function documented
and is it allowed in every case to send SOAP messages to ABAP port?
Question 2:
What logging and tracing functionalities do i have in both scenarios before the message enters (before RWB)?
E.g. where can i see unsuccessful requests (e.g. if there is mistyping in SenderChannel).
Then it not visible in Runtime Workbench but whereelse?
If the ABAP port is adressed i see something in SMICM trace file, but very cryptic and not conclusive.
Do you know further trace/log files for both scenarios (Visual Admin?) ?
Question 3:
What is the difference if https is used concerning logs and traces?
Do i have more or less possibilities?
Thank you very much in advance for comments.
Michael

Hi
The URL sent to the ABAP port and the J2EE port are different.
The URL to the ABAP port is documented in this blog by Stefan,
/people/stefan.grube/blog/2006/09/21/using-the-soap-inbound-channel-of-the-integration-engine
http://<server>:<ABAP-port>/sap/xi/engine?type=entry&version=3.0&Sender.Service=<YourService>&Interface=<YourNamespace>%5E<YourInterface>
Answering question 1 --> As the URL are different, the Request in case of the ABAP stack hits the Integration Engine directly - into the pipeline of XI and bypassed the Adapter Engine competely.
As stefan's blog states - you cannot post multipart SOAP request to the IE directly.
Question 2 - If the URL is incorrect, if the request hits XI then you will have the log in XI ( in MONI in case of ABAP port ) and in RWB -Message Monitroing ( in case of J2EE port)
Regards
Bhavesh

SOAP Adapter with Security Levels - HTTP & HTTPS

We have a successfully working interface scenario where SAP XI is hosting a web service and the partner systems calling it using SOAP Adapter URL http://host:port/XISOAPAdapter/MessageServlet?channel=:service:channel with Security Level HTTP on the SOAP Sender Communication channel.
Going forward, for other similar interfaces (SAP XI hosting Web Service and partner systems calling it), we would like to use HTTPS and/or certificates.
If we enable HTTPS on XI J2EE server as per the guide How to configure the [SAP J2EE Engine for using SSL - Notes - PDF|https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/964f67ec-0701-0010-bd88-f995abf4e1fc]....
can partner systems still use the URL http://host:port/XISOAPAdapter/MessageServlet?channel=:service:channel or should they switch to https://host:port/XISOAPAdapter/MessageServlet?channel=:service:channel?
can we continue to have the existing interface working using HTTP Security Level i.e. partners not having to send the certificate with each message?
If we use HTTPS security level, is it mandatory for the partner system need to send the certificate? Is it possible to have an HTTPS scenario w/o certificates?
What is the difference between Security Levels 'HTTPS Without Client Authentication' & 'HTTPS with Client Authentication'?
I appreciate your inputs on this.
thx in adv
praveen
PS: We are currently on SAP PI 7.0 SP17

Hi Praveen,
There is no need to change the interface and It is manditory for the partners to send certificates in order to validate each other. Use the https in url.
HTTPS With Client authentication:
The HTTPS client identifies itself with a certificate that is to be verified by the server. To validate the HTTPS clientu2019s certificate, the HTTPS server must have a corresponding CA certificate that validates this certificate. After validation of the clientu2019s certificate, the server maps the certificate to an actual system user executing the HTTP request.
and check this link.
http://help.sap.com/saphelp_nw04/helpdata/en/14/ef2940cbf2195de10000000a1550b0/frameset.htm
Regards,
Prasanna

Adding ClientCertLoginModule into SOAP adapter causes problem for HTTP

Hi there,
We are configuring SOAP adapter to use HTTPS with client authentication
for a B2B project. We followed note 891877 to add ClientCertLoginModule
into service sap.com/com.sap.aii.af.soapadapter*XIOAPAdapter in the
security provider service,
ClientCertLoginModule, SUFFICIENT
BasicPasswordLoginModule, SUFFICIENT
The interface for the B2B project works fine after the change.
But other interfaces which are using HTTP to connect to SOAP adapter
are all failing with HTTP code 302. Because all these interfaces are
using HTTP protocal with username/password for authentication, we
expect they should still work because the BasicPasswordLoginModule is
listed in the login module stack.
Any help is much appreciated..

Hi there,
We are configuring SOAP adapter to use HTTPS with client authentication
for a B2B project. We followed note 891877 to add ClientCertLoginModule
into service sap.com/com.sap.aii.af.soapadapter*XIOAPAdapter in the
security provider service,
ClientCertLoginModule, SUFFICIENT
BasicPasswordLoginModule, SUFFICIENT
The interface for the B2B project works fine after the change.
But other interfaces which are using HTTP to connect to SOAP adapter
are all failing with HTTP code 302. Because all these interfaces are
using HTTP protocal with username/password for authentication, we
expect they should still work because the BasicPasswordLoginModule is
listed in the login module stack.
Any help is much appreciated..

SOAP Adapter recvr.CC unable to call, call failed

Hi,
i'm doing the IDoc to SOAP Scenario for Vendor Master. Sender CC is IDoc Adapter & Receiver CC is SOAP Adapter. Sending the vendor data(SAP ECC) to third party(through WebService) system. In the recv.CC,
in the Connection Parameters>Target URL->i've given the URL given by third party (which is working fine when i open in explorer), & below in Conversion Parameters>SOAP Action also i've given. After sending the vendor from ECC by BD14, it is not received in Webservice.
In the Runtime Workbench,
Component Monitoring-->Communication Channel Monitoring
--> for my recv.SOAP CC, it is showing the error as:
MsgID:----
Explanation
98719886-dbc5-194c-9da7-0cfe8d77082c call failed
98719886-dbc5-194c-9da7-0cfe8d77082c request entering
URL is working fine in the browser.
SOAP Action is rightly given.
Webservice not requires any logon data, so not configured User Authentication.
No Proxy settings we are using.
How to verify about firewall and ports to send SOAP message out of XI Box or network
Any other settings or configurations i've to do in XI system?
what might be the reason for this error. Experts pls help in resolving the same.
rgds,
balu

hi,
thanks for the quick reply..
It is showing:
Status:red symbol
Adapter Type: SOAP
Direction: Receiver
In cluster Node tab,
Processing Errors: in the last 20 hours
Short Log: active
MsgID:----
Explanation
98719886-dbc5-194c-9da7-0cfe8d77082c----- call failed
98719886-dbc5-194c-9da7-0cfe8d77082c----- request entering
Above already i've given the in recvr.CC what & all entered. pls do the needful.
tnx n rgds,
balu

HTTP 200 response - Connection Failure - CF10 local Tomcat

Hello,
I am invoking a webService, FirstData to be exact. It's SSL. I am invoking properly, and FirstData is seeing my request as valid and successful, but the response comes back with a 200 and the filecontent is "Connection Failure". No SOAP structure in the response. I found that this was a bug with CF8 which I'd expect to be cleared up in CF10. Is there a workaround? I've attempted passing headers in various ways but it continues to fail.
<cfhttp url="XXX" method="POST" username="XXX" password="XXX" path="XXX" file="XXX" resolveurl="false" clientCert="XXX" clientCertPassword="XXX">
 <cfhttpparam type="XML" value="#myXML#">
 <cfhttpparam type="header" name="Accept-Encoding" value="deflate;q=0" />
 <cfhttpparam type="header" name="TE" value="deflate;q=0" />
 </cfhttp>
Response
struct
Charset
utf-8
ErrorDetail
[empty string]
Filecontent
Connection Failure
Header
HTTP/1.1 200 OK Date: Fri, 22 Mar 2013 19:25:10 GMT Server: Apache/2.4.2 X-Powered-By: Servlet 2.5; JBoss-5.0/JBossWeb-2.1 Accept: text/xml, text/html, image/gif, image/jpeg, *; q=.2, */*; q=.2 Content-Length: 852 Connection: close Content-Type: text/xml;charset=utf-8
Mimetype
text/xml
Responseheader
struct
Accept
text/xml, text/html, image/gif, image/jpeg, *; q=.2, */*; q=.2
Connection
close
Content-Length
852
Content-Type
text/xml;charset=utf-8
Date
Fri, 22 Mar 2013 19:25:10 GMT
Explanation
OK
Http_Version
HTTP/1.1
Server
Apache/2.4.2
Status_Code
200
X-Powered-By
Servlet 2.5; JBoss-5.0/JBossWeb-2.1
Statuscode
200 OK
Text
YES

Hi
Might be you are processing huge data because of this you are getting this error.
Regards
Dheeraj Kumar

XI SOAP adapter

Hi, guys.
I find the SAP doc that when SOAP receiver adapter send a SOAP message, it requires a HTTP 200 response with empty SOAP envelope.
However, the customer system only gave back a HTTP200 response without empty SOAP envelope. XI considered the remote server didn't receive the message successfully.
How to deal with these if the remote server really did not provide the empty SOAP envelope.
looking forward your ideas.
Thanks in advance.
Alex.

Hi,
Refer,
SAP Note 856597 6. Receiver Asynchronous Calls
In this note lookout what response XI expects from SOAP receiver. Also check out the use of no-soap mode.
Regards,
Prateek

How to catch the sender SOAP adapter http response?

Hi eXperts,
I've a sender soap adapter opened to customer as webservice. When customers call this webservice, data is coming into XI and works fine. But the customer is complaining that the expected HTTP 200 response is not sent back to the calling SOAP client.
So my question is: Is there a way to catch the http 200 response from sender adapter, or at least get to know if the sender adapter has sent the response?
Thanks in advance.
Regards
Luis

Hi,
If I understood it correcly... Sender is a Async SOAP call and the sender system is expcting a status back of HTTP 200. Are you sure you had set the quality of effort to Exactly Once? If not please try setting it.
You can also go to Adapter monitoring or Communication channel monitoring in the Runtime workbench and see if the Sender SOAP adapter is fine.
http://help.sap.com/saphelp_nw04/helpdata/en/5e/164442c1a1c353e10000000a1550b0/content.htm
Thanks,
Prakash

SOAP Adapter: Content Type Issue in WebServices via HTTP

Hi,
I have configured a Receiver SOAP adapter. When i had to test the message i had an HTTP 415 error.
i found that the sender SOAP adpater that received this message is not capable of handling Content-Type: Application/XML i.e. which is being transmitted by the Receiver SOAP Adapter.
Please let me know how to configure in the Receiver SOAP adapter so that the HTTP Content-Type would be TEXT/XML instead of Application/XML .
Thanks in Advance,
Venkatesh

Hi Michal,
I have created a Web service for a RFC function Module. The webservice is available in SOAMANAGER.
It got activated also . But whenever I tried to test, I am getting the below error,
"Message Envelope not found. Probably Empty SOAP message"
 Request:
 POST /sap/bc/srt/rfc/sap/yotci_i015_linkp8sap/100/yotci_i015_linkp8sap/yotci_i015_linkp8sap HTTP/1.1
Host: sapkrftewd01.krft.net:8030
Content-Type: text/xml; charset=UTF-8
Connection: close
Authorization: <value is hidden>
Content-Length: 657
SOAPAction: ""
<?xml version="1.0" encoding="UTF-8" ?><SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xs="http://www.w3.org/2001/XMLSchema"><SOAP-ENV:Header><sapsess:Session xmlns:sapsess="http://www.sap.com/webas/630/soap/features/session/"><enableSession>true</enableSession></sapsess:Session></SOAP-ENV:Header><SOAP-ENV:Body><ns1:YotciI015Linkp8sap xmlns:ns1='urn:sap-com:document:sap:soap:functions:mc-style'><IvParam1>POD</IvParam1><IvParam2>00006095</IvParam2><IvParam3>01/14/2009</IvParam3><IvParam4>PDF</IvParam4></ns1:YotciI015Linkp8sap></SOAP-ENV:Body></SOAP-ENV:Envelope>
 Response:
 HTTP/1.1 500 Message E 1S 406 cannot be processed in plugin mode HTTP
content-type: text/xml; charset=utf-8
content-length: 0
accept: text/xml
sap-srt_id: 20090224/141936/v1.00_final_6.40/49A4677A2D0736EDE10000000A3597E9
server: SAP Web Application Server (1.0;700)
Is this because of "do not use SOAP envelope" check?
I didn't check this check box.
If that is the error could you please tell me how to see the "do not use SOAP envelope"?
Where can I find SOAP channel?
I am very new to SOAP concept.
One JAVA application is going to invoke this Webservice from SAP.
Please help me.
Thanks,
Bala.

Special characters in sender soap adapter provoke HTTP 500 error

Hi,
SAP R3 is sending a SOAP message to PI through SOAP adapter.
When the payload does NOT contain german characters like ü, it works fine.
However, when the payload DOES contain special characters, the SOAP adapter replies with an HTTP 500 code error.
If I use SoapUI to send the soap message, and setting UTF-8 as the encoding in the program options, it will go through fine. If I change to ISO-8859-1 it will fail.
I'm thinking in two options:
- Make sure that SAP R3 sends the message in UTF-8 format (I think this is happening currently), as if SoapUI works, then probably R3 is not using UTF-8.
- Force the adapter to use UTF-8. Is this possible? In the sender SOAP adapter I've added AF_Modules/MessageTransformBean (type local EB), and then Transform.ContentType for parameter name and --> text/plain;charset=utf-8 for parameter value. The sender adapter will fail then for every message, with or without special characters.
Anyway, in this link (http://help.sap.com/saphelp_nwpi71/helpdata/EN/a4/f13341771b4c0de10000000a1550b0/frameset.htm) it seems to say that the sender soap adapter cannot be extended with modules, so maybe that's the reason why it fails when trying to add a module.
Thanks

If I use SoapUI to send the soap message, and setting UTF-8 as the encoding in the program options, it will go through fine. If I change to ISO-8859-1 it will fail.
I'm thinking in two options:
Check the use of option 1 ..... the URL which SAP is using to send the data can containe the encoding information.
Check this SAP note: https://service.sap.com/sap/support/notes/856597
From the above note:
Q: What character encoding is supported by the SOAP sender adapter?
+you can supply the encoding information with the xmlenc variable in the request URL as in+
Regards,
Abhishek.

How to make call to Sender Soap Adapter using HTTPS with Client Aut

Hello everyone, I have spent some time trying to get this to work. We downloaded a trail certificate from SAP and installed it on our machine and I created a webservice that works great. I tested the HTTPS without client authentification and it works great, as soon as I change it to use with Client Authentification I can't get it to go through. I am using Soap Sonar to test the certificates. To get the certificate I called the url with firefox then saved the certificate in my trust store, from there I import it to soap sonar as a signed certificate, but I am getting the error <Exception>Object contains only the public half of a key pair. A private key must also be provided.</Exception> I assume I am doing something way wrong, is there a way to get the certificate with both public and private key pair, or a way to test this that I can't seem to find in documentation or blogs?
I def award points
Cheers
Devlin

Hi
I think This link is useful to u
http://www.sapag.co.in/SAP-XI-SOAP-Adapter-FAQ'S.html
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/40611dd6-e66e-2910-f383-e80fb44f9cd4
Thanks
Santosh

SOAP to SOAP / HTTP 200 error

Hi
I have the following scenario SOAP to SOAP and am getting a HTTP 200 error.
com.sap.engine.interfaces.messaging.api.exception.MessagingException: java.io.IOException: No SOAP Envelope but 1 definitions; HTTP 200
I have configured a sender SOAP channel with default values (Nothing is checked). My receiver channel is configured in a similar manner. The SOAP action is specified. I have tested the receiver webservice in WSNavigator and successfully can get it to call. The webservice was created from a function module that has used the create webservice functionality, and then endpoints created in SOAMANAGER.
There are no mappings in this scenario.
When I right click on the sender agreement and get the WSDL, I take that URL and place it into the WSNAVIGATOR tool. I supply the same values that I did when I called the service directly. When I execute, the error above appears in SXMB_MONI.
Ideas?

Here is the error. There is no principle propagation and the user is setup in the BI system.
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:Category>XIAdapterFramework</SAP:Category>
<SAP:Code area="MESSAGE">GENERAL</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText>com.sap.engine.interfaces.messaging.api.exception.MessagingException: java.io.IOException: No SOAP Envelope but 1 definitions; HTTP 200 OK</SAP:AdditionalText>
<SAP:Stack />
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Edited by: Mike Marowski on Feb 18, 2010 12:12 AM

SOAP Adapter - Guaranteed delivery

Hi ppl,
I have a requirment where we are exploring the possibility of the source system being able to expose its data in http format so that we can get use XI SOAP adapter to get the same over https. As SOAP adapter would access the data through WAN, what would happen to the data if the WAN is broken? How does the guaranteed delivery work in case of SOAP adapter?

>
Ethan Hunt wrote:
> thanks for your reply. For inbound messages, how will the data be recieved by SOAP adapter in case of broken WAN. If the source system is exposing the data once in every minute and the WAN is broken for 10 min, when it comes up again, will SOAP adapter recieve all the messages sent by the source system during the connectivity failure? I am not sure how the expose of data in http format works.
From your comments, it seems that the source system acts as a client, and PI (SOAP Adapter) will receive the data from the client.
You can configure the "Quality of Service" of the sender soap adapter with 3 possible options:
- Exactly once (async)
- Exactly once in order (async)
- Best effort (synchronous)
In the first two cases, your client will get an HTTP 200 response (with an empy SOAP message), while in the last case it will get as a response the message you have configured in PI. Take into account that in the first two cases, even if there is an internal error in PI (mapping error for example) your SOAP adapter will still have delivered an HTTP 200 response, as the SOAP adapter did its mission (received the message and delivered it to the Integration Server).
If the client can't reach PI, it won't get an HTTP 200, it will get an HTTP 500 or other error code, so it's your client responsability to retry sending the message until it gets the proper response.
http://help.sap.com/saphelp_nwpi71/helpdata/en/fc/5ad93f130f9215e10000000a155106/content.htm
Edited by: Jorge Lopez on Jul 13, 2009 3:20 PM

XI SOAP adapter vs webservice testing tools

Actually I have creted simple xslt mapping and managed to come up with exactly in the format of endpoint request format of the webservice.
here is the payload( I have created the SOAP Envelop, Header and body in the payload)
<?xml version="1.0" encoding="utf-8"?>
<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:eb="http://www.ebxml.org/namespaces/messageHeader" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:xsd="http://www.w3.org/1999/XMLSchema">
<SOAP-ENV:Header>
 <eb:MessageHeader SOAP-ENV:mustUnderstand="1" eb:version="1.0">
 <eb:ConversationId>sucesss</eb:ConversationId>
 <eb:From>
 <eb:PartyId type="urn:x12.org:IO5:01">applevac.com</eb:PartyId>
 </eb:From>
 <eb:To>
 <eb:PartyId type="urn:x12.org:IO5:01">webservices.sabre.com</eb:PartyId>
 </eb:To>
 <eb:CPAId>P4XC</eb:CPAId>
 <eb:Service eb:type="sabreXML">session</eb:Service>
 <eb:Action>SessionCreateRQ</eb:Action>
 <eb:MessageData>
 <eb:MessageId>mid:[email protected]</eb:MessageId>
 <eb:Timestamp>2001-02-15T11:15:12Z</eb:Timestamp>
 <eb:TimeToLive>2001-02-15T11:15:12Z</eb:TimeToLive>
 </eb:MessageData>
 </eb:MessageHeader>
 <wsse:Security xmlns:wsse="http://schemas.xmlsoap.org/ws/2002/12/secext" xmlns:wsu="http://schemas.xmlsoap.org/ws/2002/12/utility">
 <wsse:UsernameToken>
 <wsse:Username>5555</wsse:Username>
 <wsse:Password>password</wsse:Password>
 <Organization>L5x5</Organization>
 <Domain>DEFAULT</Domain>
 </wsse:UsernameToken>
 </wsse:Security>
</SOAP-ENV:Header>
<SOAP-ENV:Body>
 <eb:Manifest SOAP-ENV:mustUnderstand="1" eb:version="1.0">
 <SessionCreateRQ>
 <POS>
 <Source PseudoCityCode="P4XC"/>
 </POS>
 </SessionCreateRQ>
 </eb:Manifest>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>
I want XI to post just the payload and nothing else so....
I selected Do not use envelope in the adapter configuration because we have every thing( SOAP envelop, header and body in the payload) but it is not working as i am still getting the same error message before implementing this xslt.
Error Message:
<StackTrace>com.sabre.universalservices.base.session.SessionException: errors.session.USG_CONVERSATION_ID_REQUIRED at com.sabre.universalservices.gateway.control.SecurityInterceptor.executeOnRequest(SecurityInterceptor.java:116) at com.sabre.universalservices.base.interceptor.Interceptor.execute(Interceptor.java:113) at com.sabre.universalservices.base.interceptor.InterceptorChain.applyInterceptors(InterceptorChain.java:32) at com.sabre.universalservices.base.interceptor.InterceptorManager.process(InterceptorManager.java:121) at com.sabre.universalservices.gateway.control.WSGateway.onMessage(WSGateway.java:415) at com.sabre.universalservices.gateway.control.WSGateway.handleRequest(WSGateway.java:313) at com.sabre.universalservices.gateway.control.WSGateway.doPost(WSGateway.java:247) at javax.servlet.http.HttpServlet.service(HttpServlet.java:709) at javax.servlet.http.HttpServlet.service(HttpServlet.java:802) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter
Do you have any idea like XI will add anything to this pay load when it sends out to the webservice?
If i take the payload from the XI and try it in SOAPUI(tool to test webservice, you would know it already ) it works fine, I mean I was able to get the proper response but in XI it does not work.
Any help in this regards is highly appreciated.
we are using PI 7.0 and SP 9.
Message was edited by:
 Venkat Marni
Message was edited by:
 Venkat Marni

Hi,
Finally I could solve the problem.
I was actually trying to post the information from the http client at the sender and receiver side I am getting the error.
Later i have actually created the webservice for my sender interface in XI then post the info using the SOAPUI(3rd party tool) to post the info to XI and then Xi will communicate the webservice using SOAP adapter then I got the proper response from the webservice.
In this whole episode I guess there is some thing wrong in using a htp client but technically we should be able to use http client as XI will take the payload and use xslt mapping to come up with target interface soap message( but i do not know why XI failed in that).
thanks for all your help and hope this is clear.
thanks,
Venkat

SOAP Adapter XI 3.0 - HTTP 200 response fails

Similar Messages

Maybe you are looking for