SOAP Receiver problem

Hi everyone.
I'm facing a new problem with SOAP Receiver adapter.
We have an WSDL that works perfectly using SOAP Clients such as SOAPUI or StylusStudio. End-point is HTTPS://XXXXX:XXX/XXXXX
WSDL is like this :
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>

<tes:registraEntrada0Request xmlns:tes="http://testing.com" xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">
<asu_id>SIO7</asu_id>
<asu_descripcion>desc</asu_descripcion>
<uo_id>1272</uo_id>
<nombre>nombre</nombre>
<ape1>ape1</ape1>
<ape2>ape2</ape2>
<usu_id>virtualdesa</usu_id>
<usu_pass>virtualdesa</usu_pass>
</tes:registraEntrada0Request>
Problem is when i try to use this webservice from XI using a SOAP Receiver communication channel. I get a strange error :
soap fault: No Deserializer found to deserialize a ':asu_id' using encoding style 'null'. [java.lang.IllegalArgumentException]
I don't know if the problem is because HTTPS. All the process has been defined correctly in XI and my doubt is about the configuration of the RECEIVER SOAP or the WSDL structure.
Hope you can help me
Regards,
Inigo.

hi,
check out response by Ricardo,
Re: Error in Receiver Soap Adapter for Google API
maybe you need to fill some attributes in an adapter module like mentioned there
Regards,
michal

Similar Messages

SOAP receiver problems

Hi Folks,
I am sending data to the webservice using SOAP receiver. In the runtime workbench I can see the message as successfull, but the end user is claiming that , he didn't get the data from XI.
What could be the possible reason for this?
Where might the message lost?
And for one message which is using SOAP receiver as communication channel , In the audit log I can see the steps as below:
SOAP: request message entering the adapter with user J2EE_GUEST
SOAP: completed the processing
SOAP: continuing to response message
SOAP: sending a delivery ack
SOAP: sent a delivery ack
The message was successfully delivered to the application using connection SOAP_http://sap.com/xi/XI/System.
MP: Leaving module processor
The message status set to DLVD.
For other message I can see the log as :
SOAP: request message entering the adapter with user J2EE_GUEST
SOAP: completed the processing
SOAP: continuing to response message
SOAP: sending a delivery ack ...
SOAP: sent a delivery ack
MP: Leaving module processor
The message was successfully delivered to the application using connection SOAP_http://sap.com/xi/XI/System.
The message status set to DLVD.
Both are using same communication channel. still u can see the difference in the steps that are exicuted (check leaving module processer line in both).
Is it mandatory that the series of steps should be same for all the messages?
I have 2 queries, please answer both......
Thanks SPMD

HI
As a first test , import the wsdl shared by third party in soap uI/MS infopath/xml spy , fill in the test data (preferably same which you are trying to post now) and do a test :- doing this you will get to know if there is any problem in the WS iteslf. if you get http 200 ok then posting happened and ask the third party to check if they got any request.
If you have sync soap then you will be getting the desired response back to soap ui .
Also check if you need to put soap action also check the content type if its text/xml or app/xml some WS dont accept App/xml u may need to use message transformation bean in modules tab.
if there is any connectivity at ntwrk level then please try if you can trouble shoot using this blog
/people/varadharajan.krishnasamy/blog/2007/01/09/troubleshooting-soap-message--xi
Regards
$rinivas

SOAP receiver problem to configurate a soaplite WS

Hello,
I have the problem to connect a web service of an partner which is wrote in perl and uses the soap:lite implementation.
Here is the code the partner have send to me:
Simple Web Interface = http://rico1.orionwt.co.uk/cgi/whXMLLoad.pl
XML Interface = <See sample Perl script
#!/usr/bin/perl
use SOAP::Lite;
Get Args
my $User = $ARGV[0];
my $Pass = $ARGV[1];
my $File = $ARGV[2];
my ($XmlBuffer, $Line);
open (XML, $File);
while ($Line = <XML>) {
$XmlBuffer .= $Line;
close (XML);
my $service = SOAP::Lite -> uri('urn:Orion::warehouse::whXMLFuncs')
->
proxy('http://rico1.orionwt.co.uk/cgi/warehouse/whOrionXML.pl');
my $result = $service -> ProcXML($XmlBuffer) -> result();
if (! $result) {
print "No XML result detected\n";
} else {
print "XML result detected \n$result\n";
sub SOAP::Transport::HTTP::Client::get_basic_credentials{
return $User => $Pass;
>
Have anyone an idea, if and how I can configurate this web service with the SAP XI SOAP Adapter?
Or isn't it possibly to configure this service, or generally soaplite services, with the SOAP adapter?

hi,
check out response by Ricardo,
Re: Error in Receiver Soap Adapter for Google API
maybe you need to fill some attributes in an adapter module like mentioned there
Regards,
michal

SOAP Receiver: Problem with SOAP Multipart Request (wsdl:part)

Dear PI experts,
our partner provided a WSDL with the following definition (I modified it to keep it simple and showing the principles)
   <wsdl:message name="nameOfMessage">
      <wsdl:part element="part1" name="header" />
      <wsdl:part element="part2" name="parameters" />
      <wsdl:part element="part3" name="attachment" />
   </wsdl:message>
After importing this WSDL in ESR, I found the following definition on tab 'WSDL':
         <xsd:complexType name="nameOfMessage">
            <xsd:sequence>
               <xsd:element name="header" type="authentication" />
               <xsd:element name="parameters" type="businessDatal" />
               <xsd:element name="attachment" type="Binary" />
            </xsd:sequence>
         </xsd:complexType>
When creating the request message in PI it looks as follows:
<nameOfMessage>
<header/>
<parameters/>
<attachment/>
</nameOfMessage>
However our WebService provider expects the following:
<soap:env>
<authentication/>
<parameters/>
<attachment/>
</soap:env>
When using SoapUI and importing the WSDL the request message looks as expected by the web service provider and the part names are resolved.
I could try to convert the request using XSLT but this does not seem to be a best practice approach.
Do you have any advice on how to handle this issue?
Thank you very much.

Hi Florian,
I modified some WS to be handled by another systems, and sometimes, when the SOAP adapter is involved, you send a Request to PI (that has NOT the same structure, than the declared in the MM) but it takes the req. anyway.
Did you try sending a request?
Juan.

Problem with soap receiver adapter

Hi All
I have Idoc sender and soap receiver in my scenario.
I am calling web service deployed on WAS.
The web service is getting called but the acknowledgement message in xi contains following system error acknowledgement because of which xi changes the status of message to WAIT and starts retrying.
<?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.aii.af.ra.ms.api.MessagingException: java.net.SocketTimeoutException: Read timed out: com.sap.aii.af.ra.ms.api.RecoverableException: java.net.SocketTimeoutException: Read timed out</SAP:AdditionalText>
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack />
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Please anybody can help to resolve this problem. This scenario has worked without any error previously.
Thanks in advance
Beena

Hi Bhavesh,
It is an Async call where method does not return anything.
I added entries in IDX_NOALE but still it is setting the message status to WAIT and does retry.
Following is the Audit Log in Runtime workbench :
Audit Log for Message: 22b3052d-c519-034e-85db-e65d541d6414
Time Stamp Status Description
2006-12-13 10:25:23 Error SOAP: error occured: java.net.SocketTimeoutException: Read timed out
2006-12-13 10:25:23 Error Exception caught by adapter framework: Read timed out
2006-12-13 10:25:24 Error Delivery of the message to the application using connection AFW failed, due to: Read timed out.
2006-12-13 10:25:24 Success The asynchronous message was successfully scheduled to be delivered at Wed Dec 13 10:30:24 GMT+05:30 2006.
2006-12-13 10:25:24 Success The message status set to WAIT.
2006-12-13 10:30:25 Success Retrying to deliver message to the application. Retry: 1
2006-12-13 10:30:25 Success The message was successfully retrieved from the receive queue.
2006-12-13 10:30:25 Success The message status set to DLNG.
2006-12-13 10:30:25 Success Delivering to channel: INSPWCCT_PVtoSAP_Ack
2006-12-13 10:30:25 Success SOAP: request message entering the adapter
2006-12-13 10:35:28 Success SOAP: call failed
2006-12-13 10:35:28 Success SOAP: sending a delivery error ack ...
2006-12-13 10:35:28 Success SOAP: sent a delivery error ack
2006-12-13 10:35:28 Error SOAP: error occured: java.net.SocketTimeoutException: Read timed out
2006-12-13 10:35:28 Error Exception caught by adapter framework: Read timed out
2006-12-13 10:35:28 Error Delivery of the message to the application using connection AFW failed, due to: Read timed out.
2006-12-13 10:35:28 Success The asynchronous message was successfully scheduled to be delivered at Wed Dec 13 10:40:28 GMT+05:30 2006.
2006-12-13 10:35:28 Success The message status set to WAIT.
I have tried this scenario earlier. I am sending the same Idoc from R3 which was processed successfully earlier.
Thanks
Beena.

SOAP receiver exception problem

Hi XI expert,
I am using scenario as following:
ABAP proxy -> xi -> soap receiver -> webservice
in sxmb_moni, the message runs ok. but in RWB, there are some error in CC monitor.
2007-07-07 11:33:54 Success SOAP: continuing to response message e305dd90-2c3a-11dc-95af-0015c5f7cd3b
2007-07-07 11:33:54 Error SOAP: response message contains an error XIAdapter/PARSING/ADAPTER.SOAP_EXCEPTION - soap fault:     Compilation Errors
2007-07-07 11:33:54 Success SOAP: sending a delivery error ack ...
2007-07-07 11:33:54 Success SOAP: sent a delivery error ack
2007-07-07 11:33:54 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:     Compilation Errors
2007-07-07 11:33:54 Error Exception caught by adapter framework: SOAP: response message contains an error XIAdapter/PARSING/ADAPTER.SOAP_EXCEPTION - soap fault:     Compilation Errors
2007-07-07 11:33:54 Error Delivery of the message to the application using connection SOAP_http://sap.com/xi/XI/System failed, due to: com.sap.aii.af.ra.ms.api.RecoverableException: SOAP: response message contains an error XIAdapter/PARSING/ADAPTER.SOAP_EXCEPTION - soap fault:     Compilation Errors.
2007-07-07 11:33:54 Success The asynchronous message was successfully scheduled to be delivered at Sat Jul 07 11:38:54 CST 2007.
2007-07-07 11:33:54 Success The message status set to WAIT.
What is the problem? and how can I deal with to identify the problem?

hi
Go through this links
Check out these threads..
RFC -> XI -> External web service
How to resolve this RFC_adapter_sender to SOAP_adapter_receiver Exception?
Why getting "DeliveryExcetion" in SOAP->XI->RFC scenario?
You may refer these fallowing weblogs
/people/riyaz.sayyad/blog/2006/05/07/consuming-xi-web-services-using-web-dynpro-150-part-i
/people/siva.maranani/blog/2005/09/03/invoke-webservices-using-sapxi
Thanks & Regards
Sridhar.Bommireddy

SOAP RECEIVER SSL Problems

Dear Community,
I have configured a SOAP Receiver to an external web service (https://server:7002/service). I have use IE to get the certificate of the server and have imported it into the keystore of the j2ee (using VA). I have imported it to the all current views available. We have SAP PI 7.0 SP18. The problem is that the SSL handshaking is not performed correctly. I have placed a tcp gateway monitor tool to see the messages pass through. As soon as the first message is send to the above URL and a response is received, I get a XIAdapter/HTTP/ADAPTER.HTTP_EXCEPTION - HTTP 500 Internal Server Error. Also, in the default trace log I get a no private key found.... Do I need extra steps to configure SSL in the SOAP Receiver? The service does not required a Client authentication certificate and has a certificate with o CA root certificate (since this is only a test system and has issued its own certificate). Any ideas? Any help will be appreciated.
Regards,
S.Socratous

Hello,
Generally it's a connectivity behaviour. Check if you have setup the connection to
the receiver and also check the explanation regarding 500 Internal Server Errors:
*Description: The server encountered an unexpected condition which prevented it from fulfilling the request.
Possible Tips: Have a look into SAP Notes u2013 804124, 807000*
It may be also a problem with the SSL certificate. So, check if it's not expired;
The correct server certificate may be not present in the TrustedCA keystore view of NWA .
Please ensure you have done all the steps described in these url (this is for 7.11):
Security Configuration at Message Level
http://help.sap.com/saphelp_nwpi711/helpdata/en/48/d1c7e690d75430e100000
00a42189b/frameset.htm
You may have not imported the certificate chain in the correct order (Own -> Intermediate -> Root);
Last, if the end point of the SOAP Call(Server) is configured to accept
a client certificate(mandatory), then make sure that it is configured
correctly in the SOAP channel and it is also within validity period.
(This certificate is the one which is sent to Server for Client
authentication)
Hope that helps.
With regards,
Caio Cagnani

Performance Problem on Soap Receiver Side

Hi,
my scenario is: FTP to SOAP (asynchronous) on PI 7.31 SP11.
The ftp sender is providing a few hundred files at once, unfortunately the processsing at productive environment takes too long, like 15-60 minutes, depending on the number of files.
What is really strange here, the same scenario is working 100% properly at the test environment! So i did some tests to find out the bottleneck:
FTP -> PI prod -> SOAP prod - slow
FTP -> PI test   -> SOAP prod - fast
FTP -> PI prod -> SOAP test   - fast
FTP -> PI prod -> NFS prod    - fast
So if found: Only slow, if i use the productive PI to productive soap receiver.
The adapter configuration is 100% the same as on test system.
I watched the slow messages and found:
First message:
Normal processing of the steps until "XISOAP: XI message received for processing".
Then it takes 4 seconds before "SOAP: Processing completed". This happens withing milliseconds on test environment.
Later messages stay longer and longer in a queue.The processing time is going up to 36 seconds (instead of 4).
-> Something is stopping / slowing them to be processed. This "stopper" becomes worse if more messages are processed.
Does anybody have an idea to explain this strange behaviour?
Regards,
Udo

Hi Udo,
The problem seems to be in the message system queue in the AFW in the production environment. It has sense because the SOAP pro and NFS pro are different adapters, however afaik the SOAP test channel uses the same thread pool that the SOAP pro in PI pro.
Have you check to increase the number of threads?. You can check the number of them,
in this URL http://host:port/MessagingSystem/monitor/systemStatus.jsp (System Status):
Regards.

Problem in SOAP Sender - SOAP Receiver Senario.

Hi,
I am working on SAOP Sender- SOAP Receiver Senario, i am using a standard web service.I have successfull created the senario and tested in the Test Configuration in Integration Directory. The problem occurs when i expose my sender interface as a Web Service and use Altova XmlSpy to send the SOAP Request, i am getting an HTTP error. Also it could be great if you could define steps required in Integration Directory -> Tools -> Define a Webservice.. the valued that should be inserted in the URL and other values to complete the Wizard
I am using this URL:- http://host:port/XISOAPAdapter/MessageServlet?channel=:<service>:<channel>
And when i use the default URL :- http://host:port/sap/xi/engine?type=entry i don't get an HTTP error, the message goes till the receiver determination and Says Sender Not found.
Looking forward to ur Guidance.
Harpreet

Hi Peter,
I have verified the name of the server and port, there is no problem in it.
Here is the detailed error:-
<?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>CPAException</code>
                         <text><![CDATA[
com.sap.aii.af.service.cpa.CPAException: invalid channel (party:service:channel) = :
     at com.sap.aii.af.mp.soap.web.MessageServlet.getChannel(MessageServlet.java:464)
     at com.sap.aii.af.mp.soap.web.MessageServlet.doPost(MessageServlet.java:400)
     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(AccessController.java:207)
     at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
          ]]></text>
                    </s:SystemError>
               </detail>
          </SOAP:Fault>
     </SOAP:Body>
</SOAP:Envelope>
Thanks !!
Harpreet

Problem in testing SOAP receiver adapter using SOAP UI

Dear Experts,
I'm trying to test my SOAP receiver adapter as mentioned in the blog http://www.sdn.sap.com/irj/scn/weblogs?blog=/pub/wlg/21844. [original link is broken] [original link is broken] [original link is broken] But, my request from ECC proxy keeps failing in XI communcation channel monitor. I've configured my receiver adapter http://ip:8080/mockSoapHTTPBinding and kept the authentication as NONE. Can any of you suggest?
ip - is my system ip shown in ipconfig.
mockSoapHTTPBinding - is the path.
Thanks.

What is the error of the messages? Are the messages leaving the SOAP adapter?
Please try both:
1. Go to Runtime Workbench -> Component Monitoring -> Adapter Engine -> Test message. Then, execute the message directly without the intermediate of the Proxy sender. This will allow you to check only the receiver SOAP.
2. Please use the TCPGateway tool attached from the note below. It will be a "man-in-the-middle" between the target WS and the Receiver SOAP channel, tracking the whole HTTP/SOAP message. Check if the message is well-formed.
[Note 856597 - FAQ: XI 3.0 / PI 7.0 / PI 7.1 SOAP Adapter|https://websmp230.sap-ag.de/sap(bD1wdCZjPTAwMQ==)/bc/bsp/spn/sapnotes/index2.htm?numm=856597]
under question "Q: How can I trace the whole message?"

SOAP Receiver - HTTP header problem

Hi,
Scenario: IDOC - - XI - - SOAP(webservice).
Third party is asking for missing "/" (path?) in header after "POST". Following is the message received by third party. How to override this header to put "/" after POST? Please help.
POST HTTP/1.0
Accept: /
Host: 100.10.2.5:9092
User-Agent: SAP-Messaging-com.sap.aii.messaging/1.0505
Authorization: Basic Z2hydHNvYXA6bm92ZWxs
content-id: <soap-48E034BD9F5B3308E1000000876CF529@sapcom>
Content-Type: text/xml; charset=utf-8
Content-Length: 313
SOAPACTION: "#batchRequest"
<SOAP:Envelope xmlns:SOAP='http://schemas.xmlsoap.org/soap/envelope/'>
    <SOAP:Header/>
    <SOAP:Body>
        <ns0:cvgtransaction xmlns:ns0='http://abc.com/xi/Novell' event='modify' workforceID='1' type='employee'>
            <attribute name='WWID' operation='replace'>1234567</attribute>
        </ns0:cvgtransaction>
    </SOAP:Body>
</SOAP:Envelope>

Hi!
with XI standard tools you have no chance to manipulate the soap envelope created by the XI. You have to configure your soap receiver communication channel to not create a soap envelope "Do not use SOAP envelope") and then you use e.g. a XSLT mapping to create a soap envelope by yourself.
Regards,
Volker

SOAP receiver inactive problem

Hi Gurus,
I am using a SOAP receiver channel, I actived this SOAP CC in ID , but when I go to RWB and goto Communication Channel monitor, found the SOAP receiver channel status is "Channel started but inactive" with a yellow triangle.
Our XI version is PI7.0 SP11.

Hi,
send the first message with it and check again
Regards,
michal
<a href="/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions"><b>XI / PI FAQ - Frequently Asked Questions</b></a>

Soap Receiver Adapter problem. very urgent..

Hi,
When I am sending data from XI to CRM through soap receiver communication channel I am getting error:
Message processing failed. Cause: com.sap.aii.af.ra.ms.api.RecoverableException: SOAP: response message contains an error XIAdapter/PARSING/ADAPTER.SOAP_EXCEPTION - soap fault: Authority check failed
Pls advice urgent.
Regards

Hi Rick,
At fist did you create SOAP fault message mapping in your scenario?
If not then plz do that.
Some links for ur help:
Troubleshooting - RFC and SOAP scenarios *** Updated on 20/04/2009 *** - have a look into this to troubleshoot your SOAP
Fault Message Types - A Demo (Part 1)
Receiver SOAP adapter scenarios:
RFC -> XI -> WebService - A Complete Walkthrough (Part 1)
RFC -> XI -> WebService - A Complete Walkthrough (Part 2)
Regards,
Vinod.

Help, strange problem about SOAP receiver adapter

Hi XI guru,
Secnario as following:
ABAP proxy -> XI -> SOAP receiver
I am using SOAP receiver to send data to legacy system. It looks good in sxmb_moni, so we go to RWB, I see the following error:
<b>2007-08-13 13:48:53 Success SOAP: continuing to response message df934151-4960-11dc-a195-0015c5f7cd3b
2007-08-13 13:48:53 Error SOAP: response message contains an error XIAdapter/PARSING/ADAPTER.SOAP_EXCEPTION - soap fault: java.lang.StringIndexOutOfBoundsException: String index out of range: 0
2007-08-13 13:48:53 Success SOAP: sending a delivery error ack ...
2007-08-13 13:48:53 Success SOAP: sent a delivery error ack
2007-08-13 13:48:53 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: java.lang.StringIndexOutOfBoundsException: String index out of range: 0
2007-08-13 13:48:53 Error Exception caught by adapter framework: SOAP: response message contains an error XIAdapter/PARSING/ADAPTER.SOAP_EXCEPTION - soap fault: java.lang.StringIndexOutOfBoundsException: String index out of range: 0
2007-08-13 13:48:53 Error Delivery of the message to the application using connection SOAP_http://sap.com/xi/XI/System failed, due to: com.sap.aii.af.ra.ms.api.RecoverableException: SOAP: response message contains an error XIAdapter/PARSING/ADAPTER.SOAP_EXCEPTION - soap fault: java.lang.StringIndexOutOfBoundsException: String index out of range: 0.
2007-08-13 13:48:53 Success The asynchronous message was successfully scheduled to be delivered at Mon Aug 13 13:53:53 CST 2007.</b>
So I use XMLSpy to simulate XI to send SOAP request to legacy system, it works fine.In XI, I use WSDL file which legacy system provided to build the mapping, so I think it should be fine. Please comments, thank you for your time.

Hi
For receiver webservice you need to configure a receiver soap adapter
http://help.sap.com/saphelp_nw04/helpdata/en/43/03612cdecc6e76e10000000a422035/frameset.htm
Check this blog:
/people/siva.maranani/blog/2005/05/23/communication-between-sap-system-webservice-using-proxies
/people/shabarish.vijayakumar/blog/2006/03/23/rfc--xi--webservice--a-complete-walkthrough-part-1
/people/shabarish.vijayakumar/blog/2006/03/28/rfc--xi--webservice--a-complete-walkthrough-part-2
Check out these threads..
RFC -> XI -> External web service
How to resolve this RFC_adapter_sender to SOAP_adapter_receiver Exception?
Why getting "DeliveryExcetion" in SOAP->XI->RFC scenario?
You may refer these fallowing weblogs
/people/riyaz.sayyad/blog/2006/05/07/consuming-xi-web-services-using-web-dynpro-150-part-i
/people/siva.maranani/blog/2005/09/03/invoke-webservices-using-sapxi
Pls reward if useful

Problem with SOAP receiver

Hello,
Our PI system is 7.4 . We have a lot of interface with related to proxy to soap.When they are used very intensively, errors occur in soap receiver .
Types are error:
503 server not avalibale,
401 unauthorized ,
invalid content type for SOAP:TEXT/HTML such as...
When system is restarted, mostly it is worked but after while again errors occur and a lot of message is waiting in queue.
what can we do for it?
Thanks in advance,
Nurhan

Hi Claudia,
It is dual stack installation. While calling soap receiver adapter, error occur. In sxmb_moni display error as follows:
After restart, we have new error:
It is abap proxy to soap scenario. It's synchronous communication.
Thanks,
Nurhan

SOAP Receiver problem

Similar Messages

Maybe you are looking for