Webservice for proxy to SOAP adapter interface

Hi Experts,
we have scenario Proxy to SOAP for this inteface is it possible to provide the webservice from PI side.
if yes please let me know the steps.
i know the process how to provide the webservice when the SOAP adapter at sender side.
1) through sender agreement---->Display WSDL.
2) Tools---->Disply WSDL
is it poassible to provide the webservice when SOAP adapter at receiver end by using 2 nd process?

we have scenario Proxy to SOAP for this inteface is it possible to provide the webservice from PI side.
if yes please let me know the steps.
i know the process how to provide the webservice when the SOAP adapter at sender side.
1) through sender agreement---->Display WSDL.
2) Tools---->Disply WSDL -
> yes that is possiable for only sender side as webservice because sender always consumer
is it poassible to provide the webservice when SOAP adapter at receiver end by using 2 nd process?
No that is not possiable to import WSDl File In receiver agreement because receiver always Provider .
in ESR:
wsdl file ll be imported in External defination as external message.
in ID:
in receiver Comm.channel -> call the soap URL and Soap Action(not manadatary)

Similar Messages

Defining a Webservice for an XI SOAP Adapter

Hi together,
i have a little problem with an SOAP XI scenario.
I have build an XML -> XI -> Idoc Scenario.
Everything is working ok with the standard http request.
Now i have made a new SOAP communication channel and set this one up
with my message interface from the http scenario. After that i tried to generate
a wsdl in the xi ( integration directory ). ( Scenario is Webservice -> XI -> Idoc )
I send this file to one of our java programmers. He has to build the webservice
on an other system. But he says that his system can not generate the webservice from the file.
He gets this message in the Log Files:
WSDL part <M2S_ROUTING> points to unavailable element with qname: {}<M2S_ROUTING>.
Its my first time to set up an SOAP communication and i have no knowledge
of java. I have tried to search in the forum, but there was no point for my
problem.
Can i use the normal message interface from my http scenario for the soap scenario?
do i have to change something in the wsdl-file that xi generates?
The url for the generation is ok. this one i have made like shown in "How To
Use the XI 3.0 SOAP Adapter".
I also testet the scenario with XmlSpy and with that its works correct.
Only the other system does not generate the webservice from the file.
( its is an NW2004 SP12 on an other server/network )
Thanks for any answers,
Carsten

redefined question

Error while invoking the ABAP Proxy via SOAP Adapter

Hi,
My scenario involves SOAP Client invoking a webservice hosted in PI which in turn invokes the ABAP Proxy asyncronously.
SOAP Client -> PI -> ECC (ABAP Proxy) . This works fine.
Next , I have exposed the ECC Service Interface as webservice using SOA Manager transaction. Now, once the service is created using SOAManager, i replaced the XI Adapter with SOAP Adapter and provided the target URL as the URL provided by the SOAManager.
SOAP Client -> PI -> ECC (ABAP Proxy via SOAP Adapter)
With this approach, i am encountering the below error message
2009-05-29 12:17:55 Error Adapter Framework caught exception: null
2009-05-29 12:17:55 Error Delivering the message to the application using connection SOAP_http://sap.com/xi/XI/System failed, due to: com.sap.engine.interfaces.messaging.api.exception.MessagingException.
Any ideas on the above errror message? Any pointers or inputs will be appreciated.
Thanks,
Vinayak Kamath

> 2009-05-29 12:17:55 Error Adapter Framework caught exception: null
> 2009-05-29 12:17:55 Error Delivering the message to the application using connection SOAP_http://sap.com/xi/XI/System failed, due to: com.sap.engine.interfaces.messaging.api.exception.MessagingException.
This is a generic error message which does not have any information about the error which has occurred.
Do you see any error messages in the SOAP client?
Regards
Stefan

Why we do not need sender agreement for Mail and SOAP adapter

Hi SDN,
I know, we do not need sender agreement for IDOC ,HTTP,XI adapters. As these three adapters will run in Integration engine of the abap stack.
In our scenario if sender is other than IDOC or HTTP or XI .
By Refering Sivamni's blog.
/people/siva.maranani/blog/2005/05/25/understanding-message-flow-in-xi
message will be pickedup by communication channel with the help of sender agreement and prepare XI message header by performing cpa cache lookup. then message will go to module processor etc.
In our scenario if sender is IDOC or HTTP or XI .
As these 3 adapters are run in Integration engine.
Doubt 1:
how the integration engine will create the xi message header like sender interface sender system name etc...
Doubt 2:
I believe SOAP and mail adapter will run in adapter engine.but i came to know that we do not need sender agreement and sender comm channel for these two adapters too...then how the XI message header will create...
Please do correct me if i am wrong
and throw some light on the same..
Appreciate your help....
Regards,
Reehan.

Reehan,
Thanks for pointing me to that link. Guess I was wrong .,But,let me try to put to you why you need a sender agreement for a Sender SOAP Adapter,
1. In the sender SOAP adapter , the Sender Interface and the Interface Namespace as provided in the fields Default Interface Name and InterfaceNamespace. The Name of the Sender Service is provided in the WSDL when you ceate the WSDL in the Integration Directory. So, as all details are available in either the Sender SOAP adapter or in the WSDL url you do not need a Sender Agreement. It is not obligatory but you can always create the Sender Agreement.
2. For the mail adapter , if you select the option XIPAYLOAD, you will have the option to mention the Interface Name and Interface Namespace under XI Parameters and so in this case as once again the details provided in the sender agreement are available in the Sender Adapter itself the sender agreement is not needed for the mail adapter when you have select option XIPAYLOAD.
If you have selected XIALL then you need a sender agreement.
Regards
Bhavesh

Problems with SOAP Adapter/Interface

Hi Experts,
we currently try and experiment with XI 3.0 Stack 09 and the SOAP adapter respectively.
We started with a simple interface (foo..., see wsdl attachment) that we want to provide by XI.
All configurations (SLD, Integration Repository, Integration Directory) should have been done accordingly as we suppose, similar to other szenarios we have already implemented.
When we send a SOAP request based on a generated wsdl to XI we get the exception at the bottom of this text, containing e.g.
com.sap.aii.messaging.srt.BubbleException: error during conversion [null "null"];
com.sap.aii.messaging.util.XMLScanException: Parsing an empty source. Root element expected!
For sending the SOAP message we used XMLSpy.
Did someone have similar problems or can give us an working WSDL example, or some hint?
Thanks in advance,
Klaus Lukas
foo.wsdl
<?xml version="1.0" encoding="ISO-8859-1"?>
<wsdl:definitions xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:p1="urn://poreceive.xi.pse.siemens.com" targetNamespace="urn://poreceive.xi.pse.siemens.com" name="foo_out_sync">
 <wsdl:types>
 <xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="urn://poreceive.xi.pse.siemens.com" targetNamespace="urn://poreceive.xi.pse.siemens.com">
 <xsd:element name="foo" type="foo_DT"/>
 <xsd:complexType name="foo_DT">
 <xsd:annotation>
 <xsd:appinfo source="http://sap.com/xi/TextID">
 fe0bb241d2a011d9cd15e9729ee2f568
 </xsd:appinfo>
 </xsd:annotation>
 <xsd:sequence>
 <xsd:element name="item" type="xsd:string">
 <xsd:annotation>
 <xsd:appinfo source="http://sap.com/xi/TextID">
 fe0bb240d2a011d9acede9729ee2f568
 </xsd:appinfo>
 </xsd:annotation>
 </xsd:element>
 </xsd:sequence>
 </xsd:complexType>
 </xsd:schema>
 </wsdl:types>
 <wsdl:message name="foo">
 <wsdl:part name="foo" element="p1:foo"/>
 </wsdl:message>
 <wsdl:portType name="foo_out_sync">
 <wsdl:operation name="foo_out_sync">
 <wsdl:input message="p1:foo"/>
 <wsdl:output message="p1:foo"/>
 </wsdl:operation>
 </wsdl:portType>
 <wsdl:binding name="foo_out_syncBinding" type="p1:foo_out_sync">
 <soap:binding xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" style="document" transport="http://schemas.xmlsoap.org/soap/http"/>
 <wsdl:operation name="foo_out_sync">
 <wsdl:input>
 <soap:body xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" use="literal"/>
 </wsdl:input>
 <wsdl:output>
 <soap:body xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" use="literal"/>
 </wsdl:output>
 </wsdl:operation>
 </wsdl:binding>
 <wsdl:service name="foo_out_syncService">
 <wsdl:port name="foo_out_syncPort" binding="p1:foo_out_syncBinding">
 <soap:address location="http://xxxxxxxx:8000/XISOAPAdapter/MessageServlet?channel=:Foo_SOAP_Service:SOAP_Foo_out&version=3.0&Sender.Service=Foo_SOAP_Service&Interface=urn%3A%2F%2Fporeceive.xi.pse.siemens.com%5Efoo_out_sync" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"/>
 </wsdl:port>
 </wsdl:service>
</wsdl:definitions>
soap message incl. error
<?xml version="1.0"?>

<SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
<SOAP:Body>
<SOAP:Fault>
<faultcode>SOAP:Server</faultcode>
<faultstring>error during
conversion</faultstring>
<detail>
<s:SystemError
xmlns:s="http://sap.com/xi/WebService/xi2.0">
<context>XIAdapter</context>
<code>XMLScanException</code>
<text><![CDATA[
com.sap.aii.af.mp.module.ModuleException
at com.sap.aii.af.mp.soap.ejb.XISOAPAdapterBean.process
(XISOAPAdapterBean.java:697)
at
com.sap.aii.af.mp.module.ModuleLocalLocalObjectImpl3.process
(ModuleLocalLocalObjectImpl3.java:103)
at com.sap.aii.af.mp.ejb.ModuleProcessorBean.process
(ModuleProcessorBean.java:221)
at
com.sap.aii.af.mp.processor.ModuleProcessorLocalLocalObjectImpl0.process
(ModuleProcessorLocalLocalObjectImpl0.java:103)
at com.sap.aii.af.mp.soap.web.MessageServlet.doPost
(MessageServlet.java:543)
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:385)
at
com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleReques
t(HttpHandlerImpl.java:263)
at
com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet
(RequestAnalizer.java:340)
at
com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet
(RequestAnalizer.java:318)
at
com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebConta
iner(RequestAnalizer.java:821)
at
com.sap.engine.services.httpserver.server.RequestAnalizer.handle
(RequestAnalizer.java:239)
at com.sap.engine.services.httpserver.server.Client.handle
(Client.java:92)
at com.sap.engine.services.httpserver.server.Processor.request
(Processor.java:147)
at
com.sap.engine.core.service630.context.cluster.session.ApplicationSessio
nMessageListener.process(ApplicationSessionMessageListener.java:37)
at
com.sap.engine.core.cluster.impl6.session.UnorderedChannel$MessageRunner
.run(UnorderedChannel.java:71)
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:94)
at com.sap.engine.core.thread.impl3.SingleThread.run
(SingleThread.java:162)
Caused by: com.sap.aii.messaging.srt.BubbleException: error during
conversion [null "null"]; nested exception caused by:
com.sap.aii.messaging.util.XMLScanException: Parsing an empty source.
Root element expected!
at
com.sap.aii.messaging.srt.xmb.XMBWebServiceExtension.onResponseToWS
(XMBWebServiceExtension.java:936)
at
com.sap.aii.messaging.srt.xmb.XMBWebServiceExtension.invokeOnResponse
(XMBWebServiceExtension.java:602)
at com.sap.aii.messaging.srt.ExtensionBubble.onMessage
(ExtensionBubble.java:58)
at com.sap.aii.af.mp.soap.ejb.XISOAPAdapterBean.process
(XISOAPAdapterBean.java:576)
... 20 more
Caused by: com.sap.aii.messaging.util.XMLScanException: Parsing an
empty source. Root element expected!
at com.sap.aii.messaging.util.StreamXMLScannerImpl.open
(StreamXMLScannerImpl.java:104)
at com.sap.aii.messaging.mo.DefaultItem.setData
(DefaultItem.java:294)
at
com.sap.aii.messaging.srt.xmb.XMBWebServiceExtension.makeItemFromPayload
(XMBWebServiceExtension.java:972)
at
com.sap.aii.messaging.srt.xmb.XMBWebServiceExtension.onResponseToWS
(XMBWebServiceExtension.java:879)
... 23 more
]]></text>
</s:SystemError>
</detail>
</SOAP:Fault>
</SOAP:Body>
</SOAP:Envelope>

Hi Klaus
In your wsdl file the soap address tag (given below)
<soap:address location="http://xxxxxxxx:8000/XISOAPAdapter/MessageServlet?channel=:Foo_SOAP_Service:SOAP_Foo_out&version=3.0&Sender.Service=Foo_SOAP_Service&Interface=urn%3A%2F%2Fporeceive.xi.pse.siemens.com%5Efoo_out_sync" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"/>
is to be edited as
<soap:address location="http://xxxxxxxx:50000//XISOAPAdapter/MessageServlet?channel=:Foo_SOAP_Service:SOAP_Foo_out" />
because the soap address format should be like :
http://host:port/XISOAPAdapter/MessageServlet?channel=party:service:channel
For more information :
http://help.sap.com/saphelp_nw04/helpdata/en/0d/5ab43b274a960de10000000a114084/frameset.htm
Hope this will be helpful.
Regards
Suraj

ABAP Proxy without SOAP adapter in PI7.3

Hi All,
We have dual stack implementation of PI7.3 but we do not wish to use the SOAP adapter for configuring an ABAP proxy scenario.
Is this possible? Is the Javastack only configuration in NW Admin available for use in dual stack implementation also?
Thanks and Regards,
Diptee

Hi All,
So it essetially means that only the below 2 options are available for ABAP proxy scenarios in PI7.3 for a ABAP+Javastack installation
- use of SOAP adapter over XI protocol
- use of conventional proxy configuration of the ABAP Integration Server
And the only Javastack config cannot be used for a dual stack implementation.
Please confirm if above is correct.
Regards,
Diptee
Edited by: diptee s on Sep 21, 2011 4:48 PM

Call ABAP-Proxy with SOAP adapter?

Hi all,
for a PI7.1-scenario I would like to use the Lookup-API in mapping. As I know I can use either RFC or SOAP channels, however I would rather call an ABAP-Proxy in my backend system instead.
So my question is: Is it technically possible to use the SOAP-adapter to call an ABAP-Proxy?
Your help would be appreciated, best regards
David

Hi Stefan,
Interesting answer here and one that has got me curious. Hope you can help.
1. When you say it is going to be possible to call a ABAP proxy using a UDF in the mapping of XI ( Lookup ), would it be using the WS Adapter of PI 7.1?
2. If 1 is yes, is there a new API code to do this, or is it the same lookup code as used previously in XI 3.0 and PI 7.0 Days?
3. If 1 is no, can you explain maybe a little more on how this would be possible using the standard SOAP adapter of XI?
Thanks a bunch.
Regards
Bhavesh

WebService: Proxy or Soap Adapter?

Hello,
is it possible to use proxies to connect via WebService?
Thanks in advance
Regards Mario

hi,
>>>is it possible to use proxies to connect via WebService?
"ABAP proxies that were generated from message interfaces in the Integration Repository (IR) can be used in both infrastructures. This means that if none of the Integration Server services are required for a proxy-to-proxy communication scenario in ABAP, you can use a point-to-point connection using the Web service infrastructure instead."
from:
http://help.sap.com/saphelp_nw04/helpdata/en/86/58cd3b11571962e10000000a11402f/content.htm
SE80 - web services - you can see your server proxies
so I guess you should be ale to do it but if you just want to use web services you can also generate
a web service form any RFC (WAS 6.40)
http://help.sap.com/saphelp_nw04/helpdata/en/e9/ae1b9a5d2cef4ea4b579f19d902871/content.htm
Regards,
michal
<a href="/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions">XI FAQ - Frequently Asked Questions</a>

Acknowlegements for Proxy - XI - SOAP

Hi gurus,
I'm designing a scenario for R3 - XI - non-SAP systems using Proxy & Soap adapters(WS).
I would like to know about the acknowledgement options and how to configure them.
Any links & info provided will be very much appreciated and rewarded.
Thank you.
Regards,
S. Gokhan TOPCU

Hi ,
For syncronous proxy we will get the acknowledgement back from proxy. use fault message type for rising exceptions.
For Asyn proxy we won't get acknowledgement back in SXI_monitor in xi. u can monitor the Application errors rised from proxy in RWB -> message monitoring . their select ur proxy bussiness system and monitor. u can rise alert in xi by calling RFC SALRT_CREATE_API from ur proxy code.
u can monitor all Application error in SXI_monitor in ur Application System(R3)
for ack check following link
http://help.sap.com/saphelp_nw04/helpdata/en/f4/8620c6b58c422c960c53f3ed71b432/content.htm
Regards
Pradeep P N
Edited by: Pradeep P N on Dec 17, 2008 10:22 AM

SOAP adapter Using XI 3.0 error: invalid content type for SOAP: TEXT/HTML

Hi All,
I have the scenario to send a message to proxy via SOAP adapter . My PI server is 7.3 and my BI application server also 7.3. I have created service interface in the ESR and created the ABAP proxy in the Application server. Im using the receiver SOAP adapter with message protocol as XI 3.0. Am running this scenario in the central adapter engine. (That is i didnt create integrated configuration). I am facing the issue in the receiver SOAP channel as 'invalid content type for SOAP: TEXT/HTML: 401 Unauthorized'. But i can able to login into the URL which is given in the channel using the username and password used in the channel.
Can you please let me know if any addtional settings need to be done in PI side.
Regards,
Ramalakshmi.G

Hi,
Thanks for your reply. I have done my scenario with the integration configuration. Still i am facing the same issue " SOAP: TEXT/HTML; HTTP 401 Unauthorized". I have given the correct URL, username and password. Is this enough to connect to the receiver integration server from AE. Any settings need to be do in the receiver ABAP system and PI system. If so please share the corressponding note for the same. What should be the role is assigned to the userid given in the channel.
I have used sproxy to create the proxy in the receiver ABAP system. In PI i am using the SOAP adapter with XI 3.0 ,message protocol to call to this proxy. I have not done any settings in any of the servers. Do i need to do any settings.
Regards,
Ramalakshmi.G

SOAP Adapter = Webservice???

Hi,
I have created a service using the SOAP Adapter. My question is now: Is this service a webservice. If yes, how would I be able to obtain the related WSDL?
The outbound interface is accessed by the following URL:
http://myserver/XISOAPAdapter/MessageServlet?channel=:MY_BUSINESSSYSTEM:MY_COMCHANNEL
simply adding the argument &wsdl to the url doesn't pass back any WSDL.
Kind regards,
Heiko

hi,
>>I have created a service using the SOAP Adapter. My >>question is now: Is this service a webservice
yes having a soap adapter for a particular scenario makes that scenaro accessable by SOAP, ie webservice.
>>http://myserver/XISOAPAdapter/MessageServlet?>>channel=:MY_BUSINESSSYSTEM:MY_COMCHANNEL
>>simply adding the argument &wsdl to the url doesn't >>pass back any WSDL.
i see where u r coming from , unlike ohter development platforms, where if you know the endpoint , adding &wsdl gives you the wsdl. But in XI we are merely exposing the interface to be accessable by a soap sender. Hence you have to generate the wsdl manually from Configuration Drectory. Tools->webservce
cheers,
Naveen

Differences between webservice and proxy

Hi guys.
Which are the differences between webservices and proxys?
If I have a XI adapter (proxy) or Soap Adapter in Pi in both a Proxy Abap is created in SEECC to consume the service so I cant see the differences...
Regards

If I wanted to consume a webservice exposed in Pi by a Sender SOAP Sender, what would I have to do?
Nothing exceptional.....just define a message structure in PI....create a message interface....generate a WSDL for this Message Interface.....use the URL from this WSDL to send message.....it is a normal SOAP --> XI scenario.....many references are readily available on How to do this.
Regards,
Abhishek.

Error in Proxy to SOAP synchronous scenario

Hi Gurus,
Hope you are doing well. I have a Proxy to SOAP synchronous interface interacting with an external system (system outside the firewall/landscape of my company).
When I am trying to post the request message from XI, I am getting the following error.
MP: Exception caught with cause com.sap.aii.af.ra.ms.api.RecoverableException: SOAP: response message contains an error XIAdapter/PARSING/ADAPTER.SOAP_EXCEPTION - soap fault: The server was unable to process the request due to an internal error. For more information about the error, either turn on IncludeExceptionDetailInFaults (either from ServiceBehaviorAttribute or from the <serviceDebug> configuration behavior) on the server in order to send the exception information back to the client, or turn on tracing as per the Microsoft .NET Framework 3.0 SDK documentation and inspect the server trace logs
In the WSDL provided by the external application, i.e. receiver WSDL, there is no attribute/field with the name 'IncludeExceptionDetailInFaults' and there is no fault string defined.
Where is this error being thrown up? Is it a network/firewall error that XI is unable to determine?
Please provide an answer as soon as possible.
regards
Debansu

Hi,
i think it is the problem in the WSDL provider system, because it is throwing the Error with some string".NET",
do the below steps for investigating the issue
1)try pinging the URL provided in the WSDL from internet explorer.
2)if it is successfull, try to push one message from SOAP UI to by importing that WSDL, if you get any error then it is problem in the end system.
Thank You,
Madhav

Regaring File to IDOC Useing SOAP Adapter

Hi ,
Can any one please forward me an File to idoc Useing SOAP ADapter Senario.IF i am wrong please send me a simple senario of useing SOAP Adapter.
Regd's
Raj

Hi Raj,
I think i will give you some more information about SOAP adapters,So Please go through the link below and follow the steps mentioned in it while defining the web service.Then you will get to know the actual use of a SOAP adapter.
<a href="http://help.sap.com/saphelp_erp2004/helpdata/en/31/daa0404dd52b54e10000000a1550b0/content.htm">Defining Web Services</a>
Sending a Simple SOAP envelope to XI via HTTP using ASP
https://www.sdn.sap.com/sdn/weblogs.sdn?blog=/pub/wlg/1442 [original link is broken]
More links for SOAP Adapter:
/people/siva.maranani/blog/2005/09/03/invoke-webservices-using-sapxi
http://help.sap.com/saphelp_nw04/helpdata/en/9f/fdca3f01f33e1ce10000000a114084/frameset.htm
http://help.sap.com/saphelp_nw04/helpdata/en/69/a6fb3fea9df028e10000000a1550b0/frameset.htm
You can create SOAP Request from WSDL using the following tool.
http://www.gotdotnet.com/Community/UserSamples/Details.aspx?SampleGuid=65a1d4ea-0f7a-41bd-8494-e916ebc4159c
You've to expose your outbound message interface as a WSDL which can be used by say EP.
Also go thru the following threads
Re: WebService
Re: SOAP Client for Synchronous Scenario
Re: How to test a webservice as a standalone?
Also check this Pdf for the Receiever SOAP Adapter configuration:
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/40728f7b-0401-0010-d9bc-8c73884a3789
Regards,
abhy

SOAP Adapter Error

I am working on a scenario:
SOAP Client <-----> XI <----> Web service.
I am using SOAP Adapter on both sender and receiver side.
I downloaded the WSDL for the webservice and imported it in IR and created Message Interfaces based on it and I am also done with the configuration side.
I am trying to send a soap request to XI via XMLSPY using my XI generated wsdl ( Generated a web service in XI using my scenario).
I am getting an error back in XMLSPY when I send a soap request.
<?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>DeliveryException</code>
 <text><![CDATA[
com.sap.aii.af.ra.ms.api.DeliveryException: Received HTTP response code
500 : Timeout
 at
com.sap.aii.af.ra.ms.impl.core.queue.CallConsumer.onMessage(CallConsumer.java:144)
 at com.sap.aii.af.ra.ms.impl.core.queue.Queue.run(Queue.java:512)
 at com.sap.engine.frame.core.thread.Task.run(Task.java:64)
 at
com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:74)
 at
com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:141)
 ]]></text>
 </s:SystemError>
 </detail>
 </SOAP:Fault>
 </SOAP:Body>
</SOAP:Envelope>
I tried to check runtime message monitoring. Here are the details:
Audit Log for Message: d3294f20-b2dc-11da-8994-003048805a88
Time Stamp Status Description
2006-03-13 17:00:46 Success SOAP: request message leaving the adapter
(call)
2006-03-13 17:00:46 Success Application attempting to send an XI
message synchronously using connection AFW.
2006-03-13 17:00:46 Success Trying to put the message into the call
queue.
2006-03-13 17:00:46 Success Message successfully put into the queue.
2006-03-13 17:00:46 Success The message was successfully retrieved from
the call queue.
2006-03-13 17:00:46 Success The message status set to DLNG.
2006-03-13 17:00:46 Error Returning synchronous error notification to
calling application: Received HTTP response code 500 : Internal Server
Error.
2006-03-13 17:00:46 Error Transmitting the message using connection
http://diamond:8005/sap/xi/engine?type=entry failed, due to: Received
HTTP response code 500 : Internal Server Error.
2006-03-13 17:00:46 Error The message status set to FAIL.
2006-03-13 17:00:46 Error Returning to application. Exception: Received
HTTP response code 500 : Internal Server Error
2006-03-13 17:00:46 Error SOAP: call failed:
com.sap.aii.af.ra.ms.api.DeliveryException: Received HTTP response code 500 : Internal Server
Error
Can anyone suggest what could be wrong here?
Thanks,
Shubha.

Hi,
You can first test your Adapter Engine from "Runtime Work Bench".
Follow the steps for testing the SOAP Adapter from XI.
Step 1 :- Component Monitoring--> Click Adapter Engine.
Step 2 :- Select the "Test Message" Tab
Step 3 :- Give details for send to = http://host:port/XISOAPAdapter/MessageServlet?channel=:<service>:<channel> ,interface name, service, namespace
Step 4 :- Payload should be Soap Request. and click send message.
Check the result in SXMB_MONI.
Note : You can create SOAP Request from WSDL using the following tool.
http://www.gotdotnet.com/Community/UserSamples/Details.aspx?SampleGuid=65a1d4ea-0f7a-41bd-8494-e916ebc4159c
Regards,
Rakesh.

Webservice for proxy to SOAP adapter interface

Similar Messages

Maybe you are looking for