No Response in synchronous SOAP adapter

Hi Experts,
 I configured a soap-xi-soap scenario on XI 7.0, and i can run the whole scenario successfully. But i can not get the response from the outbound.
 I tested my scenario via XML spy, when i sent the request, i always got the following content in XML Spy:
<SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
 <SOAP:Header/>
 <SOAP:Body/>
</SOAP:Envelope>
But if i sent a request to my target web service directly, i can get the correctly ressult. like this:
 <?xml version="1.0" encoding="utf-8"?>
<SOAP-ENV:Envelope xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
 <SOAP-ENV:Body xmlns:rpl="urn:WS_Hello_NameSi">
 <rpl:sayHiResponse xmlns:rn0="http://schemas.xmlsoap.org/soap/encoding/" xmlns:rn1="java:sap/standard">
 <rpl:Response>This is Hello World test.</rpl:Response>
 </rpl:sayHiResponse>
 </SOAP-ENV:Body>
</SOAP-ENV:Envelope>
I used message monitor and channel monitor, all the information display successful.
when i use "SXMB_MONI" monitor, the technical routing is correct, but the content in response is wrong?
So what is the problem? Can somebody help me?
BTW, i want to use TCP Gate to monitor the request, unfortunately i can not capture anything in my scenario. but i can capture the request if i sent a request to web servies.
Thanks & regards
Rocky

Hi Matias,
   Thanks your reply!
   My question has been solved. Because i use the wrong Quality of service;
·    BE (Best Effort):
The message is sent synchronously. The sender waits for a response before it continues processing.
·   EO (Exactly Once):
The message is sent asynchronously. The sender does not wait for a response. The Integration Engine and the Adapter Engine guarantee that the message is sent and processed exactly once.
· EOIO (Exactly Once In Order):
Messages are delivered with the same queue names (supplied by the application) in the same sequence that they were sent from the sender system. Message processing is asynchronous in this case.
Use the Best effort for synchronous scenario.
Thanks&Regards
Rocky

Similar Messages

How to save the Response message from SOAP adapter

Dear Friends,
I am sending the FIle details webserver.here sender is FILE adapter and receiver is SOAP adapter.
FIle to SOAP working successfully, but I need response from SOAP.
Sender QoS is BE, so the response is coming to XI, but in SXMB_MONI it is showing DO YOU WANT TO SAVE IT or DISPLAY IT.
my requirement is response message is directly updated in XI system.
For response Can I use BPM or which method I need to use.
Please suggest me how to do the resonse message(SOAP to FILE).
Regards,
Shalini Shah.

Sender QoS is BE,
File adapter does not support sync communication. Therefore the scenario won't work as it is.
What are you planning to do with the response? If you want to process is further, then:
1. One way without BPM would be use of adapter module.
File - RFC - File without a BPM - Possible from SP 19.
2. Or you may use BPM with Async Sync bridge
/people/arpit.seth/blog/2005/06/27/rfc-scenario-using-bpm--starter-kit
Regards,
Prateek

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

Access to SOAP header in synchronous SOAP response?

Hi,
Scenario: message received via synchronous SOAP adapter call.
In the response which is sent back to the sender i can influence the SOAP body but not the SOAP header.
Is there a possibility to manipulate/add/map the SOAP header in synchronous response messages?
Thank you very much in advance for your hints.
Greetings
Michael

Hi Christophe,
per default PI is sending back something like this
<SOAP:Envelope xmlns:SOAP='http://schemas.xmlsoap.org/soap/envelope/'>
 <SOAP:Header/>
 <SOAP:Body>
 Payload, which can be accessed via mapping
 </SOAP:Body>
</SOAP:Envelope>
but required are some fields in the Header tag like:
<SOAP:Envelope xmlns:SOAP='http://schemas.xmlsoap.org/soap/envelope/'>
 <SOAP:Header>
 <SOAP:ABC>date</SOAP:ABC>
 </SOAP:Header>
 <SOAP:Body>
 Payload, which can be accessed via mapping
 </SOAP:Body>
</SOAP:Envelope>
Greetings
Michael

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

Issue with Receiver SOAP adapter for synchronous scenario

Hello All,
We are facing a strange issue with the SOAP adapter in the interface we have setup. This is the 1st time we are using SOAP adapter in our system (PI 7.11 SP7). We are making a synchronous HTTP call to the web service exposed by another system in our landscape. The payload is send with SOAP envelope and there are no credentials to be maintained in PI settings.
The issue is that we are always getting timeout exception in PI audit logs after sending the request (3 minutes - standard timeout value, no additional config for this). But target system has confirmed that they are sending the response back. We tested from our server OS level and have received the response back in the same screen (to verify there is no firewall/port issue in between the systems). But when tried from RWB, it is always giving the timeout exception and we are not able to see any other log.
We have tried checking in the NWA logs as well after increasing the logging level to ALL for com.sap.aii.adapter.soap. But surprisingly, we didn't get any logs at all for the outgoing SOAP call or incoming response and hence we are unable to trace the issue.
We have setup another synchronous inbound SOAP interface (PI exposing the webservice) and it is working fine. We are also able to trace the logs in both audit log and NWA logs.
Is there anywhere else we can check for the logs? Audit logs is showing timeout error and we are not able to see anything in NWA logs.
Does the target system need to maintain PI credentials in the header when they send the synchronous response back?
Are there any specific settings which should be checked to enable the sync communication? (this should not be the case since the inbound interface is working fine)
Please help.
Thanks
Justin

Hi Amit,
Thanks for the reply.
Yes we had tested successfully via SOAP UI as well (forgot to mention that). We are getting back the expected response in SOAP UI without using any credentials. We got the same response when we tested it through OS commands from PI server.
The WS is hosted by the target system and they haven't maintained any credentials at their end. So when PI is trying to access, we don't need to provide any credentials. My question is, whether the target system should keep any credentials to send the synchronous response back to PI (java stack). We have tried that as well but since there aren't any logs, we are unable to verify whether the credentials are coming correctly.
The service interfaces are correct and PI configuration are OK. I will try the XPI inspector for logs as you have suggested.
Thanks
Justin

Synchronous messages through Soap Adapter

Hi XI Guru's
In my scenario I am sending a synchronous soap message over soap adapter. Message flow is like
3rd Party Application --> XI --> SAP R/3.
My message do get processed in SAP R/3 and I do get response in SXMB_MONI as well as in Message Monitoring in RWB.
The return message for message f1bdf1d0-cec5-11de-a9c0-0050569626f6(OUTBOUND) was successfully passed to the waiting "call" thread.
2009-11-11 05:27:26     Information     The message status was set to DLVD.
2009-11-11 05:27:26     Information     SOAP: response message entering the adapter (call)
2009-11-11 05:27:26     Information     SOAP: response message leaving the adapter
But still the response from XI does not reaches 3rd party application.
On digging the logs I found following message. Can this be an issue in XI which is blocking the reponse message from reaching the 3rd Party Application.( I tried posting the message through XML spy and I do get the response in XML spy.)
(Note : My XI Installation has central adapter engine)
#1.5 #0050569626F6004200000D0B00000B5000F66675B4B8DEA5#1257401122698#com.sap.engine.services.servlets_jsp.client.RequestInfoServer#sap.com/com.sap.aii.adapter.soap.app#com.sap.engine.services.servlets_jsp.client.RequestInfoServer#LOVEIN#25369##sapnw03_NPI_6935550#Guest#2fd59d51c9d111debb440050569626f6#HTTP Worker [4]##0#0#Warning##Plain###Cannot send an HTTP error response [500 "Application error occurred during the request procession." (details: "The WebApplicationException log ID is [0050569626F6004200000D0800000B5000F66675B4B8DEA5].")]. The error is: com.sap.engine.services.servlets_jsp.server.exceptions.WebIOException: *The stream is closed.*
+     at com.sap.engine.services.servlets_jsp.server.runtime.client.ServletOutputStreamImpl.ensureOpen(ServletOutputStreamImpl.java:354)+
Any help in this regard is appreciated .
Thanks
Lovein

Thanks for your reply Stephan / Abhishek.
To add some more info on the issue. This issue is when I am using PI 7.1 version.
I do not face the issue if I use XI 3.0 and end to end flow works fine and response message reaches 3rd party application.
Only difference I have in 2 versions is that in XI 3.0 we have been able to disable the soap adapter authentication (by changing web.xml file) where as in PI 7.1 we have not been able to disable that authentication and userid/ password info has to be provided while sending the soap message from 3rd Party application.
(Security if not disabled gives 401 message as described on following blog [SOAP Sender ADAPTER 401 No Authorisation|SOAP Sender ADAPTER 401 No Authorisation] )
On the other note do you guys know a way to disable this authentication on PI 7.1 version.
Thanks ,
Lovein

Data Headers in SOAP adapter Response

Hi there,
I have a working SOAP adapter on Xi 2.0, which accepts incoming requests from SOAP clients, it "transforms" these requests into RFC calls which in turn calls BAPI'S in R/3.
The BIG issue is that Xi (the SOAP adapter) sets and sends a set of headers into the response back to the SOAP client. For security and performance reasons, you dont want the system to send those headers over the net to the SOAP client.
Does anyone knows how to setup Xi in order to suppress these headers in the SOAP response?
PS: Below an example of the headers in the SOAP envelope.
<SOAP:Envelope xmlns:SOAP='http://schemas.xmlsoap.org/soap/envelope/'>
<SOAP:Header><sap:MessageHeader xmlns:sap='http://sap.com/exchange/MessageFormat' version='1.0'>.......
<Host>xxxx</Host>
<Sysid/>
<Sysnr>00</Sysnr>
<Mandt>200</Mandt>
<Dest/>
<Userid>XI_USER</Userid>
<Passwd>xxxx</Passwd>

If I want to set the content in the SOAP header when the client in SAP XI how would I do that?
I cannot see SOAP Header in XI MONI.
Please advice. I want to add to the contents of SOAP Header created by XI SOAP Receiver Channel.
Thanks
Ashish

Request Response Bean for SOAP Sender Adapter

Hi Friends,
Is it possible to use Request Response Bean Module described (FIle to RFC to File here) for SOAP(sender) and JDBC(receiver) adapter?
I want to configure SOAP to JDBC to JDBC scenario.
http://wiki.sdn.sap.com/wiki/display/HOME/UsingRequestResponseBeanModuleinFILE+Adapter
Scenario:
I will do SOAP adapter call Asynchronously and JDBC receiver adapter will select data from database. This response will go back to SOAP adapter and then SOAP will divert this response to another JDBC adapter. This JDBC adapter will insert data into another database.
I do not want to use ccBPM. Is there any design approach to implement this scenario?
Thanks,
Sandeep Maurya

Hi Sandeep,
SAP says SOAP sender adapter does not support Modules. You can serch Help.sap (for SOAP sender channel) to find the same.
I would suggest to use AXIS adapter (provides all the functionality of SOAP) and supports the Modules as well.
I have used the Module beans that you mentioned in the past... but it is not consistent with its processing.. sometimes it stucks with Message ID issue... I have seen same issue faced some other friends as well .. search on SDN you will find the issue with these modules...
Using BPM would be another option...
Thanks,
Sunil Singh

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 works synchronously with EO !??

Hello,
I configured Sender SOAP Adapter with EO. The SOAP adapter follow the message to a BPM.
All of this process work fine with the HTTP Adapter (that I use for test) but when I use the SOAP Adapter I receive a strange error message :
BPE_ADAPTER.SYNCHONOUS_MESSAGE
The process does not support the given synchronous interface or does not support synchronous messages
Does anybody know how to sovle this ?
Thanks
Regards
Chris

I always have the return code 0. This process work with the HTTP Adapter but not with the SOAP Adapter.
The only thing I change was the adapter in the sender agreement.
This is the begeening of the XI Message :

<SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" xmlns:SAP="http://sap.com/xi/XI/Message/30">
<SOAP:Header>
<SAP:Main xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" xmlns:wsu="http://www.docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" versionMajor="003" versionMinor="000" SOAP:mustUnderstand="1" wsu:Id="wsuid-main-92ABE13F5C59AB7FE10000000A1551F7">
<SAP:MessageClass>ApplicationMessage</SAP:MessageClass>
<SAP:ProcessingMode>synchronous</SAP:ProcessingMode>
<SAP:MessageId>1CCC5F0F-F2BB-BC49-BDC3-A6C2F209A645</SAP:MessageId>
<SAP:TimeSent>2006-12-26T11:50:36Z</SAP:TimeSent>
<SAP:Sender>
<SAP:Service>TOFFStaging</SAP:Service>
<SAP:Interface namespace="http://t.be/xi/TOFF/LeadCreation">MIOA0001_Offer</SAP:Interface>
</SAP:Sender>
<SAP:Receiver>
<SAP:Party agency="" scheme="" />
<SAP:Service>BP0001_ToffLeadCreation</SAP:Service>
<SAP:Interface namespace="http://t.be/xi/PI/LeadCreation">MIAA0001_Offer</SAP:Interface>
<SAP:Mapping notRequired="M">
<SAP:ObjectId>rrEYQC3BMRyBTROgtt+SaQ==</SAP:ObjectId>
<SAP:SWCV>g2bqoJATEdu/Gvy1rBATzQ==</SAP:SWCV>
<SAP:SP>-1</SAP:SP>
</SAP:Mapping>
</SAP:Receiver>
<SAP:Interface namespace="http://t.be/xi/PI/LeadCreation">MIAA0001_Offer</SAP:Interface>
</SAP:Main>
<SAP:ReliableMessaging xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:QualityOfService>BestEffort</SAP:QualityOfService>
</SAP:ReliableMessaging>
Regards,
Chris

Synchronous messages for SOAP adapter.

Hi All,
I wanna expose an interface in XI as a WebService.My requirement is to invoke a webservice which takes some input and hands it over to a DataBase and gets something from it(DB) and hands it over to the application which had called this WebService.Both the request and response have to go and come through the WebService.Is it possible to design an Outbound Intf in Synchronoues mode with both the input and output messages types and expose that Intf as a WebService.
Clarification and help on this wud b appreciated.
Thanx in Advance.
Anil Kumar Veepuri

Hi Anil,
You can definitely make an outbound Interface as a webservice.For this create two message
types(Request & Response) and make a synchoronous Message Interface out of it.This will be
our Outbound Interface. You will Definitely have JDBC Request and response.
Map the outbound Resquest type-> JDBC Request.
JDBC Response->Outbound Response.
Go to Tools->Define Web service, mention the Outbound Interface you have created.Now you save the WSDL created out of it and make a call to this interface through the SOAP Adapter.
Cheers,
Rashmi

Error in using XI-SOAP adapter, but no error with SAP-BC

Hi,
I am working on RFC->XI->Webmethod (.asp) scenatio.
I am using SOAP adapter.
Whin I am not using "Do not use SOAP Envelop".
I am getting "com.sap.aii.af.ra.ms.api.DeliveryException: invalid content type for SOAP: TEXT/HTML" Error in SXMB_MONI.
But when I am using "Do not use SOAP Envelop" then I am not getting any error. in SXMB_MONI status showing Successfully Processed. But the responce i am getting is "You are not authorized to view this page // HTTP 401.1 - Unauthorized: Logon Failed"
But same web-service is working fine while connected with SAP-BC.
Please Help why scenario is working with BC, but not with XI.
Thanks & Regards

Hi Bhavesh,
Thanks for reply.
I am getting all success in message monitoring, but still web-services sying they are not getting any message.
I am attaching all 4 logs for one synchronous communication of message monitoring.
I am not able to understand where message going and why XI showing success every where.
********1st(Sent Messages)
Success SOAP: response message leaving the adapter
Success Application attempting to send an XI message asynchronously using connection AFW.
Success Trying to put the message into the send queue.
Success The response message for message cf4fd921-4a74-11db-9312-001279933263(INBOUND) was successfully transmitted to the calling application.
Success The message status set to DLVD.
Success The application sent the message asynchronously using connection AFW. Returning to application.
********2nd (Sent Messages)
Success RFC adapter received sRFC for Z_PA_SAP_TO_Webservice from D02/230. Attempting to send message synchronously
Success Application attempting to send an XI message synchronously using connection AFW.
Success Trying to put the message into the call queue.
Success Message successfully put into the queue.
Success The message was successfully retrieved from the call queue.
Success The message status set to DLNG.
Success The message was successfully transmitted to endpoint http://XYZ.com:8000/sap/xi/engine?type=entry using connection AFW.
Success The application sent the message synchronously using connection AFW. Returning to application.
Success The message status set to DLVD
**********3rd (Received Messages)
Success Using connection AFW. Trying to put the message into the receive queue.
Success The XI response message for message d0372be1-4a74-11db-91d7-001279933263(INBOUND) was successfully returned to the calling application.
Success The message status set to DLVD.
**********4th (Received Messages)
Success The message was successfully received by the messaging system. Profile: XI URL: http://XYZ.com:50000/MessagingSystem/receive/AFW/XI
Success Using connection AFW. Trying to put the message into the request queue.
Success Message successfully put into the queue.
Success The message was successfully retrieved from the request queue.
Success The message status set to DLNG.
Success Delivering to channel: IF_O_502_WebserviceBusService_SOAP_In_02
Success SOAP: request message entering the adapter
Success SOAP: completed the processing
Success SOAP: response message received d0372be1-4a74-11db-91d7-001279933263
Success The message status set to DLVD.
Success The message was successfully delivered to the application using connection AFW.

Receiver SOAP Adapter error

Hi All,
 I am getting this response error message in my receiver SOAP Adapter while invoking a synchronous webservice.
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <ProcessMessageResponse xmlns="http://Sleek.Integrator.Messaging" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:s="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<ProcessMessageResult>Value cannot be null. Parameter name: Request string is a null reference.</ProcessMessageResult>
</ProcessMessageResponse>
Thx in advance
Ravijeet

Hi All,
 I am still getting the same error value is null. I am not able to track what could be the cause of the error. If I am taking the message from SXMB_MONI and using it in a client tool it is successfully calling the webservice.
Do we need to explicitly mention in some configuration that content type is soap/xml. SOAP header is omitting the content type or is not specifying "soap/xml" as the content type.
I am interacting with a WAF websevice, is there any compatibilty issue with Windows Webservice and SAP XI?
Also what should I pick as the SOAP Action from this wsdl file definition
<wsdl:portType name="IMessageProcessor">
 <wsdl:operation name="ProcessMessage">
 <wsdl:input message="tns:IMessageProcessor_ProcessMessage_InputMessage" wsaw:Action="XXX.Messaging/ProcessMessage"/>
 <wsdl:output message="tns:IMessageProcessor_ProcessMessage_OutputMessage" wsaw:Action="XXX.Messaging/ProcessMessageResponse"/>
 </wsdl:operation>
 </wsdl:portType>
 <wsdl:service name="MessageProcessor">
 <wsdl:port name="BasicHttpBinding_IMessageProcessor" binding="i0:BasicHttpBinding_IMessageProcessor">
 <soap:address location="http://XXX.com/cardax/provisioningservice"/>
 </wsdl:port>
Thx in advance
Ravijeet

Error in Sender SOAP Adapter on XI 3.0 SP13

Hi All.
I have an application that sends a SOAP message to XI SOAP Adapter, to reach a synchronous interface. I've generated the .wsdl file from the Integration Directory, within the URL:
http://sapbox:59800/XISOAPAdapter/MessageServlet?channel=:BS_PORTAL:CC_S_SOAP_CREDITO
When I try to reach this URL, I get the successful response:
Message Servlet is in Status OK
I've also created the sender SOAP communication channel, fullfilling the default namespace and default interface correctly.
However, when I use wsnavigator client provided by SAP to prove the scenario, the SOAP message doesn't achieve XI, as the XISOAPAdapter EJB throws some exceptions:
HTTP/1.1 500 Internal Server Error
Connection: close
Server: SAP J2EE Engine/6.40
Content-Type: text/xml; charset=utf-8
Date: Sat, 17 Sep 2005 02:59:12 GMT
<?xml version='1.0'?>

<SOAP:Envelope xmlns:SOAP='http://schemas.xmlsoap.org/soap/envelope/'>
<SOAP:Body>
 <SOAP:Fault>
 <faultcode>SOAP:Server</faultcode>
 <faultstring>Server Error</faultstring>
 <detail>
 <s:SystemError xmlns:s='http://sap.com/xi/WebService/xi2.0'>
 <context>XIAdapter</context>
 <code>BaseEJBException</code>
 <text><![CDATA[
com.sap.aii.af.mp.processor.ModuleProcessorException
 at com.sap.aii.af.mp.ejb.ModuleProcessorBean.process(ModuleProcessorBean.java:278)
 at com.sap.aii.af.mp.processor.ModuleProcessorLocalLocalObjectImpl0.process(ModuleProcessorLocalLocalObjectImpl0.java:103)
 at com.sap.aii.af.mp.soap.web.MessageServlet.callModuleProcessor(MessageServlet.java:162)
 at com.sap.aii.af.mp.soap.web.MessageServlet.doPost(MessageServlet.java:508)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
 at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:390)
 at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:264)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:347)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:325)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:887)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:241)
 at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
 at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148)
 at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
 at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
 at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
 at java.security.AccessController.doPrivileged(Native Method)
 at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:95)
 at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:159)
Caused by: com.sap.engine.services.ejb.exceptions.BaseEJBException: Exception in method process.
 at com.sap.aii.af.mp.module.ModuleLocalLocalObjectImpl3.process(ModuleLocalLocalObjectImpl3.java:121)
 at com.sap.aii.af.mp.ejb.ModuleProcessorBean.process(ModuleProcessorBean.java:227)
 ... 19 more
Caused by: java.lang.NoSuchMethodError: com.sap.aii.messaging.srt.xmb.XMBWebServiceExtension.setDynamicConfigurationMode(I)V
 at com.sap.aii.af.mp.soap.ejb.XISOAPAdapterBean.createXMBWSBubble(XISOAPAdapterBean.java:1129)
 at com.sap.aii.af.mp.soap.ejb.XISOAPAdapterBean.setup(XISOAPAdapterBean.java:265)
 at com.sap.aii.af.mp.soap.ejb.XISOAPAdapterBean.process(XISOAPAdapterBean.java:562)
 at com.sap.aii.af.mp.module.ModuleLocalLocalObjectImpl3.process(ModuleLocalLocalObjectImpl3.java:103)
 ... 20 more
 ]]></text>
 </s:SystemError>
 </detail>
 </SOAP:Fault>
</SOAP:Body>
</SOAP:Envelope>
I've already done something really similar on SP 9. Can it be a new problem from SP13? Does anyone has any idea?
Thanks in advance.
Deise Lima.

Hi Naveen,
I have configured a SOAP sender adapter in XI 3.0 and is using the URL
http://host:port/XISOAPAdapter/MessageServlet?channel=:BS_WEBSERVICE:CC_WEBSERVICE_SOAP to post the messages. When I open the URL in the browser I am getting the error.
Message Servlet is in Status ERROR
Status information:
Servlet com.sap.aii.af.mp.soap.web.MessageServlet (Version $Id: //tc/aii/30_VAL_REL/src/_adapters/_soap/java/com/sap/aii/af/mp/soap/web/MessageServlet.java#5 $) bound to /MessageServlet
Classname ModuleProcessor: null
Lookupname for localModuleProcessorLookupName: localejbs/ModuleProcessorBean
Lookupname for remoteModuleProcessorLookupName: null
ModuleProcessorClass not instantiated
ModuleProcessorLocal not instantiated
ModuleProcessorRemote not instantiated
But when I test the URL http://host:port/XISOAPAdapter/HelperServlet?action=FindChannel&channel=:BS_WEBSERVICE:CC_WEBSERVICE_SOAP to check the communication channel I am getting the right response as below.
<?xml version="1.0" ?>
http://host:port/XISOAPAdapter/HelperServlet?action=FindChannel&channel=:BS_WEBSERVICE:CC_WEBSERVICE_SOAP <s:ChannelInfo xmlns:s="http://sap.com/xi/WebService/xi30">
<channelID>e7ac884596ea3d088cbfd8b434f942f2</channelID>
<name>CC_WEBSERVICE_SOAP</name>
<type xmlns:st="http://sap.com/xi/XI/System">st:SOAP</type>
<direction>INBOUND</direction>
<party />
<service>BS_WEBSERVICE</service>
</s:ChannelInfo
I used the http capture to debug, In the 1st case though I am getting "Message Servlet in status error" I am seeing a 200 OK code in the http capture tool. When the message is posted from .net client proxy or Altova XML Spy we are getting a 500 internal server error.
Am not sure what causes the error

No Response in synchronous SOAP adapter

Similar Messages

Maybe you are looking for