SOAP adapter: WSDL issue

Hi Experts,
I am working on File-XI-->Mail scenrio using SOAP adapter. My file contains only one line fields say:
TATA 407
I have configered File adapter perfectly and CC of it is showing perferctly green (Data is coming in MONI). On the counter SOAP side, I would like to send this file to the Gmail. But I am not able to do this due to the fact that I am not understanding the WSDL ? I have read several doucments but not one is giving the perfect idea about it.
Please tell me how to accomplish it. Please avoid to send the links. Please help ASAP.
-=Soniya=-

Hi Soniya,
>>I do agree that Mail adapter can be used in place of SOAP
No, it's not that.
SOAP and Mail adapter are two different things. SOAP adapter is used to exchange SOAP messages (do not confuse "message" with "email message") between applications (XI/PI to third pary OR third-party application to XI/PI) using SOAP/HTTP protocol. Whereas Mail adapter is used to send email using IMAP/POP3 protocol.
>>Somebody is saying that Webservices are the one, where you send your messages either side people are saying.
Correct. You can configure SOAP adapter as sender in PI and receive SOAP messages in PI sent by some third-party application. OR you can configure SOAP adapter as receiver and post the message form PI to some third-party provided URL.
For exposing webservice from PI all you need to do is to go to Integration directory. Select the sender aggrement you want to puslish as web service. From TOOLS menu say display WSDL. Save this WSDL and provide it to client/third-party application. They will have to generate the client proxy class and post the message from there to PI.
For cosuming webservice in PI (posting message from PI), third-party application has to provide you with a URL which you will enter into SOAP receiver type adapter.
Regards.

Similar Messages

Sender SOAP Adapter Security Issue

Hi All,
We are building a SOAP to proxy scenario. The sender is a SOAP Adapter and the receiver is Proxy. The SOAP WSDL and URL is provided to the legacy system. When the legacy system is trying to send the data using the WSDL and the URL provided, they are receiving a dialog box to enter the user name and password. We can create a system user and provide those credentials to the legacy system. However, the legacy folks are not interested in including this in their web service.
Could you please suggest, if there is a way to create the web service such that it wouldn't request for user credentials? Something like no authorizations in the web service?
Thanks,
Manohar Dubbaka.

Hi Preeti,
Thanks for the response. Since we are on PI 7.0, I believe the setting that you are referring to should be on Visual Admin. Could you please let us know the parameter or the setting that needs to be changed in VA?
I am not sure, how we can make use of SSO to prevent them from entering the user credentials. Your help in this regard would be much appreciated.
Thanks,
Manohar Dubbaka.

SOAP adapter Module Issue

Hi,
i had configured a JDBC to SOAP scenario and the SOAP adapter has the Module (localejbs/ReplaceXMLTag)
now the issue is while execute teh scenario, it works fine at DEV but shows error at QA as given below
"Delivery exception: Object not found in Lookup of Replace XML tag"
please let me know how to resolve this issue.
Thanks in advance....

> i had configured a JDBC to SOAP scenario and the SOAP adapter has the Module (localejbs/ReplaceXMLTag)
> "Delivery exception: Object not found in Lookup of Replace XML tag"
Have you spelled this correct? The name in the error message seems to be different from th module name.

SOAP adapter 404 issues

Dear friends,
My scenario is web serivce to proxy, and i created the sender interface and relevant sender soap adapter, finally I exposed the outbound service with a web service, the URL is http://hostname:port/ISOAPAdapter/MessageServlet?channel=:servicename:channelname
After that, i called the web service from XMLSPY, but got the exception information in the response message:
<faultcode>SOAP:Server</faultcode>
               <faultstring>Server Error</faultstring>
               <detail>
                    <s:SystemError xmlns:s="http://sap.com/xi/WebService/xi2.0">
                         <context>XIAdapter</context>
                         <code>ADAPTER.JAVA_EXCEPTION</code>
                         <text><![CDATA[
com.sap.aii.af.ra.ms.api.DeliveryException: Received HTTP response code 404 : Not Found
     at com.sap.aii.af.ra.ms.impl.core.queue.consumer.CallConsumer.onMessage(CallConsumer.java:158)
     at com.sap.aii.af.ra.ms.impl.core.queue.Queue.run(Queue.java:917)
     at com.sap.aii.af.ra.ms.runtime.MSWorkWrapper.run(MSWorkWrapper.java:56)
     at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
     at java.security.AccessController.doPrivileged(AccessController.java:219)
     at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:102)
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)
          ]]></text>
                    </s:SystemError>
               </detail>
and then I opened the RWB to find the detail information from message monitoring, the relevant error information are as below:
2008-09-02 17:20:54     Success     SOAP: request message leaving the adapter (call)
2008-09-02 17:20:54     Success     Application attempting to send an XI message synchronously using connection SOAP_http://sap.com/xi/XI/System.
2008-09-02 17:20:54     Success     Trying to put the message into the call queue.
2008-09-02 17:20:54     Success     Message successfully put into the queue.
2008-09-02 17:20:54     Success     The message was successfully retrieved from the call queue.
2008-09-02 17:20:54     Success     The message status set to DLNG.
2008-09-02 17:20:54     Error     Returning synchronous error notification to calling application: com.sap.aii.af.ra.ms.api.RecoverableException: Received HTTP response code 404 : Not Found.
2008-09-02 17:20:54     Error     Transmitting the message using connection http://hostname:50000/sap/xi/engine?type=entry failed, due to: com.sap.aii.af.ra.ms.api.DeliveryException: Received HTTP response code 404 : Not Found.
2008-09-02 17:20:54     Error     The message status set to FAIL.
2008-09-02 17:20:54     Error     Returning to application. Exception: com.sap.aii.af.ra.ms.api.DeliveryException: Received HTTP response code 404 : Not Found
Does anybody know what's the problem? I ever cheched the message servlet: http://hostname:port/XISOAPAdapter/MessageServlet?channel=:servicename:channelname, the status is OK.
Regards,
Bean

Dear friends,
The problem has been finally solved, it's due to the wrong configuration of the pipeline URL in SLD for the integration server, the port should be 80*, not 5*00, thanks to all of you.
Bean

Sender SOAP Adapter Authentication issue

All,
We have a SOAP-XI-RFC scenario. We exported the wsdl from the Integration Directory. When we try to call the web service using webservice studio client. We get the following error. We are using a user that has (SAP_XI_ADMINISTRATOR role on it).
ResponseCode: 401 (Unauthorized)
Connection:close
Pragma:no-cache
Content-Length:1790
Cache-Control:no-cache
Content-Type:text/html
Date:Fri, 30 Nov 2007 20:01:23 GMT
Expires:0
Server:SAP J2EE Engine/7.00
WWW-Authenticate:Basic realm="XISOAPApps"
Any thoughts?
Thanks.

hi thezone ,
<i>ResponseCode: 401 (Unauthorized)</i>
as per this specific error try checking that
1.check the wsdl url format
http://<server>:<port>/XISOAPADAPTER/MESSAGESERVLET?channel=:<Service>:<Channel>
2. test the wsdl by putting the url in internet explorer and see if you are getting a dialog box for user name and password, also in this step you will confirm the working status of message servlets of web service.
3. by step 2 IE will send a message to XI, now you check your adapter
4. test ur xml instance in your soap tester, go to its properties and make sure that you had given correct user name and password over there on specified fields.
regarding your soap communication channel it will be activated after receiving first message. you can detect any problem in connection only after receiving first message.
Regards,
Mandeep Virk
reward points if helpful

Sender SOAP adapter - WSDL not working

Hi,
I am doing Sender SOAP and receiver RFC adapter for SOAP-BAPI scenario.The WSDL is generated after IR and ID config.
URL
http://host:port/XISOAPAdapter/MessageServlet?Sender.Service=BS_VCT_Sender&Interface=urn:abb-com:vct:sap:ven%5EUSER_MI
But by testing by XML spy, m getting error -
com.sap.aii.af.service.cpa.CPAException: Couldn't retrieve inbound binding for the given P/S/A values: FP=;TP=;FS=null;TS=null;AN=null;ANS=null;
Can you please let me know wats error in it. I have testing mappings and all is OK. How to test also pls tell me.
When opening URL in IE, its giving -Message Servlet is in Status OK.
Pls answer.
Thanks

Hi all
thanks for replies.
i am testing by xml spy 2009 sp1.
finally i am using this URLin SAP PI 7.0 :
*http://host:port/XISOAPAdapter/MessageServlet?senderService=BS_VCT_Sender&interface=USER_MI&receiverParty= &receiverService=Sys_RD2_520&interfaceNamespace=urn:abb-com:vct:sap:ven*
But problem is i am not allowed to save WSDL file with "&" only , when i am saving file like -> senderService=&interface then its giving WSDL file not well formed. I must use "&amp" in stead of "&" to make it well formed.
Thus its not identifying -
Couldn't retrieve inbound binding for the given P/S/A values: FP=;TP=;FS=BS_VCT_Sender;TS=null;AN=null;ANS=null;
Any way that & can be avoided in WSDL.

Outbound SOAP Adapter Authentication issue

Hi All,
We have a scenario vendor to ECC (SOAP to Proxy) scenario. They are consuming Xi webservice. Now we don't want to give them the USERNAME and PASSWORD for our Integration Engine. Is there a way we can hard code UserID/Passowrd in the Adapter instead?
Regards,
XIer

Ashish,
>Is there a way we can hard code UserID/Passowrd in the Adapter instead?
No
Cheers
Agasthuri Doss

Sender SOAP Adapter issue with webservices for authorization.

Hi All
Issue:
As we are developing a Web Service to fetch account balance from SAP(upon receiving the account no from client) and have given the wsdl file to J2EE application to call or make use of the service. But as a part of that service they expect userid/password to be entered manually from client pop-up. At this point of time, we don't want to enter userid/password manually but we want this to be hardcoded/embedded in Webservice so that there is no need of manual intervention upon calling this service.
Actual Requirement:
From Webservices to R/3-ECC6.0-IS-Banking-RFC (Synchronous Interface)
Sender: SOAP Adapter synchronous
Receiver: RFC Adapter synchronous
Note: Requesting a account number and getting response from RFC is account Balance and Date to webservice
Regards
Kiran kumar.s

Hi praveen,
Thanks for ur reply.What you said is exactly right but for time being i have to make the client not get the authorization(password--Username and password(pop-up)) when he invokes the WSDL into webservice for that u told that to write some hardcode in J2EE application,but i don't know that where to write and what to write.so, if possible can u give me the code and procedure.
This is the URL:
http://hcl3sap:50000/XISOAPAdapter/MessageServlet?channel=:BS_WEBSERVICE:CC_SOAPSENDER
Regards,
kiran kumar.

PI 7.1 problems publishing a WSDL of a sender soap adapter

We have upgraded our dev system from XI 3.0 to PI 7.1 and now I'm facing a problem with SOAP adapter. I have searched for answers here for a while but couldnu2019t find them. That why I start an own thread.
I thought with PI 7.1 it is very easy to publish the WSDL of SOAP adapter respectively a sender agreement. All you have to do is to choose your sender agreement and select the menu item "display WSDL" There you can get the WSDL and a WSDL URL. So it would be possible to deliver this URL to my partners. But while checking this URL respectively the delivered WSDL I've found a problem.
First of all the the WSDL URL doesn't look really good:
http://<server>:<port>/dir/wsdl?p=1_1ce2e954fe9632818bfff6c32f370748_portTypeBindingService
But it works. If I call this URL with a browser or with XML Spy I get the correct WSDL. Any chance to get a better readable URL?
The next thing is the proposed soap:address location in the WSDL. It has the following form:
http://<server>:<port>/XISOAPAdapter/MessageServlet?senderParty=&senderService=MYSERVICE&receiverParty=&receiverService=&interface=MYINTERFACE&interfaceNamespace=MYNAMESPACE"
If I compare it with the documentation i can see that the URL is completely different.
http://help.sap.com/saphelp_nwpi71/helpdata/en/43/951aceb1146353e10000000a11466f/frameset.htm
But again if it works all is fine but it doesn't work at least it doesnt work with XML Spy. The reason is the use of "& a m p ;" instead of only "&".
If I create a SOAP request with XML Spy an sent it to the XI I get the following error message: " Couldn't retrieve inbound binding for the given P/S/A values: FP=;TP=;FS=null;TS=null;AN=null;ANS=null;"
But if I change the SOAP request parameters replacing all the "& a m p ;" with "&" then it works.
Any chance to manage this? If I provide a WSDL on this way I want that my partners can use this "out of the box"

Kulwant
Yes of course I can change that manually but therefore I have to save the WSDL to my local hard disc, change the WSDL and send it to my partner via mail. This is exactly the way I've done this till now. But with PI 7.1 I like to use the new opportunities.
Bhavesh
I have also no Service Repository till now. That's the reason why I want to use the way described in my initial post.
In PI 7.1 you can open the corresponding sender agreement of you SOAP adapter. There you find a menu item "display WSDL". If you choose this you get a window which displays the correct WSDL and an URL where you can find the WSDL too. If you copy this URL to a browser you get the same WSDL too.
http://help.sap.com/saphelp_nwpi71/helpdata/en/31/daa0404dd52b54e10000000a1550b0/content.htm
First part of my question is regarding to this URL. The URL has a strange format.
The second part is regarding to the form of soap:address in this generated WSDL. Here I have problems with the use of this "& a m p ;" string. But I have no influence on it. If I deliver my partners the obove mentioned URL to the WSDL and the WSDL contains this soap:address URL my partner will probably have the same problem like I with my XML Spy.
Gaurav
I don't understand you answer. I know the correct soap address but the IB tool generates it with this "& a m p ;" string instead of only "&". Thatu2019s the point. No idea if and how I can handle this.
But thank you for the note number. Was helpful. The number is in the online documentation too but I've read over it.
To bad that the online documentation isn't correct regarding to the soap address. But believe me the German version is even worse. There you can find the two soap adapter settings (XI parameter: interface namespace, interface) that are no longer existed in PI 7.1
Now I will test if a .NET application can handle this soap address correctly.
Edited by: Gil Ritter on Nov 14, 2008 11:25 AM

SOAP receiver adapter configuration issue

Hi Everyone,
When I am trying to excute a sync scenario from SAP<>XI<>Webservice from Integration engine , I am getting the below error message.
Error while sending message: com.sap.aii.af.ra.ms.api.DeliveryException: SOAP: response message contains an error XIAdapter/HTTP/ADAPTER.HTTP_EXCEPTION - HTTP 415 Cannot process the message because the content type 'text/xml; charset=utf-8' was not the expected type 'application/soap+xml; charset=utf-8'.
In the receiver SOAP adapter, I have configured Transformation module where I kept the MessageTransformationBean in processing sequence as a priority and also provided the module configuration.
ModuleKey: transform
ParameterName: Transform.ContentType
Parameter Value: application/soap+xml;charset=utf-8.
But still get the above error message in the communication channel. I am using certificates in my configuration that were deployed in visual Admin.
In the adapter configuration, I have just provided the Target URL, Configured User Authentication, certificate authentication and SOAP action.
Can anyone help me.. how to rectify the issue.....
Thanks in advance,
Hareen

HI Hareen,
I decided to give SOAP1.2 using the standard SOAP Adapter a try
There are a few noticeable differences between the request message of SOAP1.1 and SOAP1.2
1.) SOAP 1.1 uses a different namespace from SOAP 1.2. For SOAP 1.1 it is "http://schemas.xmlsoap.org/soap/envelope/" while for SOAP 1.2 it is "http://www.w3.org/2003/05/soap-envelope".
2.) SOAP 1.2 does not use SOAPAction in its header.
3.) Content type is also different, for SOAP 1.1 it is "text/xml" while for SOAP 1.2 it is "application/soap+xml"
So a sample request for SOAP 1.1 would be like this:
Content-Type: text/xml;charset=UTF-8
SOAPAction: "http://sampleaction"
While for 1.2 it is:
Content-Type: application/soap+xml;charset=UTF-8;action="http://sampleaction"
The SOAP action is moved to the content type (experts please correct me on this).
Based on the differences, you need:
1.) Construct the correct SOAP Envelope for request message mapping and remove it for the response mapping
2.) Use MessageTransformBean to change content type
3.) Leave SOAPAction as blank
I think dynamic soap action is no longer possible because the action is hardcoded in the module configuration (please correct).
Hope this helps,
Mark

Special Characters issue---u00FA ,u00A3---- in Reciver SOAP Adapter

Hi ,
I am facing issues with Spceial Characters ú ,£ at the reciver SOAP adapter ,the messages was stuk in XI with to the following error :An invalid character was found in text content. Error processing resource
I tried in several ways buy using XMBWS.XMLEncoding=iso-8859-1,
but it was not resloved still I am getting the same error,
Any one plz suggest me how to resolve this issue....
Regards,
Teja.

Hi ,
My scenario is RFC--SOAP ,the messages was successfully rached to RFC adapter and I am facing the issue at the receiver SOAP Adapter ......
I am getting error messages such as :
1) 400 Bad Request
2) In the XML Payload ......It is showing as Invalid Character found ....
For this I tried ...
1) In the source payload XML I done the chages in the encodding part
encoding part as iso-8859-1instead of utf-8.
2) I have triggered the message from Integration Engine ....then it was successfully processed through SOAP Adapter
3) with special characters...means there is no issue at target end.
4) the issue lies in XI so we have to resolve it.
I tried by using Adapter paramters which was provided by SAP but the result is same..
so the paramters which was provided by SAP are incorrect(for encoding)
Please help me in resolving this issue .........
Regards,
Teja.

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

WSDL url for sender and receiver SOAP adapter

Dear Experts,
I am working on SOAP --> SAP PI --> SAP ECC synchronous scenario. That means I have to create 2 Cc for SOAP i.e. Sender as well as Receiver adapter. I am responsible for creating the Request as well as Response structure in SAP PI. The sender application team is dependent on me to get the WSDL file.
Please provide the suggestions on the below.
Sender SOAP adapter.
1. I will create the WSDL from Sender Aggreement. How to get the url and what is the navigation step? Should I provide the    same url to sender application team to call the service.
Receiver SOAP adapter:
2. In the receiver SOAP adapter , Should I have to get the web service parameter of the sender application. As mentioned , I am creating the response structure as well. That means I can not import the WSDL from the sender application. How to get target url in the receiver SOAP Cc.
I refered to the forum SOAP SENDER - test in soapui but its not clear.
Regards
Alice Rebecca
Edited by: Alice@xi on Dec 20, 2011 5:48 PM

Dear Bhaskar,
For synchronous scenario
                                                            Request
MS Application (SOAP)<--> SAP-PI <--
> SAP ECC.
                                                                                Response
I am creating the Request as well as Response structure in SAP-PI and its agrreement for both
the ways.
So for the MS appl team, I will give the WSDL url from the sender agreement to make the request to SAP-ECC.
Now for receiving the response from SAP ECC, from where I should find the value to enter in the target url of SOAP
receiver channel.
1.Should I take the target url value from the MS Application team?
2.How to know whether the MS Application or SAP ECC is hosting the web service?
Regards
Alice

Connection issue between Data service(DQ) to PI through SOAP adapter.

Hi Guys,
We are trying to connect the data services(DQ) with SAP PI through SOAP adapter. I provided the wsdl file to data services team and they are trying to send messages to PI. Looks like the messages are showing successful in there system, but not showing up in PI system.
I tried the same file using xmlspy and PI receiving the messages from XMLSPY. We are wondering whats going wrong?
Any idea about this data services system? Is there any other better way to receive messages to PI apart from webservices?
PS: Connection is working fine from PI to DQ thorugh SOAP adapter.
Thanks
Deepthi.

>>>> We are trying to connect the data services(DQ) with SAP PI through SOAP adapter. I provided the wsdl file to data services team and they are trying to send messages to PI. Looks like the messages are showing successful in there system, but not showing up in PI system.
You are using soap sender adapter ... Hosting webservices and DQ team is able to access your webservice. Also using XMLSPY you are able to see pi messages.
If you are using advance adapter engine, Please check only in the RWB -> adapter engine.
If you are not using AAE, check in both SXMB_MONI and RWB for the wide range... Something problem with filter query in your checking...
Note since XMLSPY testing goes through Pi and able to monitor means you dont need another webservice client tool.
Solution:
use tcp monitor to monitor the soap message ... It is better option
/people/stefan.grube/blog/2007/03/29/troubleshooting-soap-http-and-mail-adapter-scenarios-with-tcpgateway

How to write won WSDL file for SOAP adapter ?

Hi experts
Can any one expalin me how to write WSDL file for SOAP adapter ?
What and all things i need to know ? i have no idea on this....
I got the business but to WSDL ...i am very new to this
Adv...thanks
Rakesh

HI,
Please see the below links,
Consuming XI Web Services using Web Dynpro Part II-/people/riyaz.sayyad/blog/2006/05/08/consuming-xi-web-services-using-web-dynpro-150-part-ii
Consuming XI Web Services using Web Dynpro Part I -/people/riyaz.sayyad/blog/2006/05/07/consuming-xi-web-services-using-web-dynpro-150-part-i
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/0d7349b6-0901-0010-ddbe-ec43178a61ff
/people/sap.user72/blog/2006/01/16/xi-propagation-of-meaningful-error-information-to-soap-client
/people/kevin.liu/blog/2006/04/12/wsdl-11-binding-extension-for-soap-12
Regards
Chilla..

SOAP adapter: WSDL issue

Similar Messages

Maybe you are looking for