Query PI 7.1 - Sender SOAP Adpater & Testing

Hi,
I have SOAP to RFC scenario. My client (3rd Party) has provided me below webservice :-
---> http://115.119.23.132/sapwebservice/service.asmx?op=save_so
--> I have Import the WSDL file as external definitions, Created an Service Interface u2013 Outbound with external Message .
I have two Queries :-
1. In 7.1, Sender SOAP Configuration, there is no option like (below) that we had in 3.0 & 7.0
u2022         Use Query String
               Daflault XI Parameters
       Default Interface Namespace
       Default Interface Name
How to link the scneario with Interface (ESR) ?
2. How to Test this scenario ?
Thanks.

Hi Anshul,
--> If the client is providing the WSDL file they are consider as the service provider.So you need to consume the webservice using PI.
-->For consuming the Webservice you need to configure the receiver SOAP Adapter where you have to provide the SOAP Action and Target URL in the receiver CC.
-->In the PI 7.1 sender soap adapter will not have all the parameters like PI7.0,WSDL will be generated based on the sender agreement which is not there in PI7.0.Since from PI7.1 we have the concept of multiple operations.
-->
Please re-check your interface designing,as per view it would be like
SAP System (RFC Adapter)-->PI7.1--->Third Party Webservice(Receiver SOAP Adapter)
Thanks

Similar Messages

Propose URL when Configuring Sender SOAP Adpater

Hi
I am doing Sender SOAP adpater .. when i try to generate WSDl from PI .. i selected the Propose URL ..its pointing to the Intergration Engine ..
When i tested the WSDl file from XML spy its giving me the " Message is incomplete. No Sender found"
How we configure the scenario with Propose URL ..
S V
Edited by: S V on Apr 11, 2009 2:30 AM

Hi,
Dont use Proposed Url, Use the below URL:
If the SOAP adapter channel belongs to a service without party, the address is as follows:
http://<host>:<j2ee-port>/XISOAPAdapter/MessageServlet?channel=:<service>:<channel>
Go to the next page by choosing Continue.
Select the message interface you want to use for the WSDL. Make sure that you choose
an outbound interface and [pass the required parameters.
Choose Finish. On the next page you can see the WSDL that has been created. Choose
Save and specify a folder and a file name to store it on your local PC. The file extension must be wsdl
Sameer

Error while testing sender SOAP scenario from XMLSpy-but can test from RWB

HI,
I developed one scenario with sender SOAP adapter and Receiver side ABAP proxy.
Now I want to test my scenario.
I tested my scenario successfully from RWB-->Integration server Integration Engine. ( it posted successfully and I can see checked flag in SXMB_MONI)
But when I tried to test the scenario fro XML spy it is throwing HTTP error 500.
When I type my URL in internet explores it is giving Message Servlet is in Status OK.
I am not sure what is the difference between there two type of testing.
What does it mean by successful from RWB and fails from XMLSpy?
Why I am getting this error from XMLSpy?

Dear Ashok,
if RWB showing you successful then message in not in error.
XML Spy giving error HTTP 500 not it is just server error.This might be due to large payload.
here is the description of all error related with 500+
5xx Server Error
The server failed to fulfill an apparently valid request.
Response status codes beginning with the digit "5" indicate cases in which the server is aware that it has erred or is incapable of performing the request. Except when responding to a HEAD request, the server SHOULD include an entity containing an explanation of the error situation, and whether it is a temporary or permanent condition. User agents SHOULD display any included entity to the user. These response codes are applicable to any request method.
500 Internal Server Error
501 Not Implemented
502 Bad Gateway
503 Service Unavailable
504 Gateway Timeout
505 HTTP Version Not Supported
506 Variant Also Negotiates (RFC 2295)
507 Insufficient Storage (WebDAV) (RFC 4918)
509 Bandwidth Limit Exceeded
This status code, while used by many servers, is not an official HTTP status code.
510 Not Extended (RFC 2774)
first ping your server
Tcode for this is SM49>ping
Then in additional parameter put the server IP and execute it will show you its reachability.
if it is not reachable then contact the server vendor,
Else if it is timeout problemthen
you run Tcode SXMB_ADM>intregration engine configuration
put category RUNTIME
then click specific configuration
Then change/increase HTTP timeout
**PS: Reward points if useful**
Regards,
Sumit Gupta

Reading parameters from Query string : Sender SOAP adapter.

Hello Experts,
I have a SOAP to SOAP scenario. Here we will have multiple receivers and dynamic receiver determination is needed.
The sender will send a Value in Query string of URL to sender SOAP adapter. This value in Query string parameter will decide the receiver at runtime.
I need to know, how can we read values from Query string of incoming call? I did tried to search blogs & forum threads but unfortunately not able to hit the right links.
Any inputs will be of great help.
Should i use "Use Query String" on sender soap channel? I tried it, but i was not able to find any query string parameters in SOAP header or payload.
Please guide me, its bit urgent.
Regards,
Abhi.

> But the argument provided from their side is: They are using standard XSD and this service is provided out of box with sender application.
If they can add a URL parameter, they can also add a field to the structure.
> They cant control the value mapping of parameters in payload to the extent required to implement this change.
Adding a new field to the structure would not affect any existing mapping.
> Since they have this custom requirement of multiple receivers & receiver to be determined at runtime, they need to go for Query string.
This can be done based on any field of the payload.
> I need to find a way to read the query string in any case.
This is not supported by SOAP adapter.
> Can I use one of the header parameters to be mapped to this value (By selecting "Use Query string" & "Keep Headers" flag in sender CC) & then extract this value from header using Dynamic configuration ?
This feature works only for XI header fields, like message ID or QoS.
Not for individual parameters.

Query on Sender SOAP

Hello,
Do we need to Configure Sender in case of Sender SOAP adapters...Normally in which cases we can skip configuring the sender SOAP adapter.
Because In on of our interfaces ,in production..I have seen an interface with no sender SOAP Communication channel used in Sender Agreement ....Even then defined Sender SOAP communication channel in some business service...
What could be the reason...

1. When we use *Sender SOAP Adapter how the connectivity is happening with Remote Clients.
A:SOAP is an XML-based protocol for exchanging information in a decentralized, distributed environment.SOAP is a technology that allows XML to move easily over the Web. SOAP does this trough an XML envelope for delivering XML content and specifying a set of rules for services to follow when they receive a SOAP message.The fundamental change brought about by SOAP has been the ability to move data anywhere across the Web.
When ever XI needs to talk to a webservice you will go for SOAP adapter. If you need to enable some functionality as webservice using XI you can use SOAP Sender adapter. If you need to send request to a webservice you will go for SOAP Receiver
SOAP Message Structure :
SOAP Envelop: The outermost element of SOAP message. The envelope element is the root of the XML document that defines a SOAP message.
SOAP Header: An optional, yet key element in architecting a distributed system around XML. The header element provides a modular way of directing SOAP servers to do processing before passing the SOAP message on. For example, it is possible to add SOAP header information that instructs a server to add transaction or authentication information. Header are also important in building piped architectures where processing is done in stages and data is modified as it is passed from handler to handler.
SOAP Body: An element that must appear in a SOAP message. The Body element is where the transported XML is loaded. SOAP makes no assumptions about the kind of XML transport in the body of a SOAP message. XML or it may take the form of remote procedure call.
also these weblogs can give you a view where you can use SOAP adapters
EP-XI Integration using Web Services and Web Dynpro MVC
https://www.sdn.sap.com/sdn/weblogs.sdn?blog=/pub/wlg/1334 [original link is broken] [original link is broken] [original link is broken]
Looking for replacing SAP.NET connectors with SAP XI?
https://www.sdn.sap.com/sdn/weblogs.sdn?blog=/pub/wlg/2131 [original link is broken] [original link is broken] [original link is broken]
how the connectivity is happening with Remote Clients?
A:Configuring the Sender SOAP Adapter
http://help.sap.com/saphelp_nw04/helpdata/en/fc/5ad93f130f9215e10000000a155106/content.htm
2.How sender SOAP Adapter get those webservices from remote clients and when exactly Remote clients will send webservices to SOAP Adapter?
It purely depends on ur client & if ur client provides WSDL file then u no need to develop it in ID and use that WSDL.WSDL describes a particular web service. Using a wsdl, we are requesting the broker to point the exact system, application, message interface. Once it is found, the SOAP channel is opened between the provider and the consumer. So the WSDL is a must to access web services.
in XI, we have to define the Web service which we want to use for the Sender SOAP channel. It is done by choosing Define Web Service from the tool menu of Integration Directory.
There is no need to code any thing. Here, what you are doing is, just exposing the sender service,channel,Message Interface as a web service.
In XI, we need to map the incoming messages to the target message( to the actual web service from the provider) format and to maintain the technical and logical routing between the sender and receiver.
Check this blog to generate WDSL file...
Exposing BAPI as Web Services through SAP XI
Configuring a SOAP Sender Channel:
When we create a SOAP sender channel we have to define the namespace and the name of a message interface (values can be taken from Integration Repository).
Select the Quality of Service according to your interface type. If you are using a synchronous interface, select Best Effort. Otherwise, select Exactly Once or Exactly Once in Order.
Transport protocol : HTTP
Message protocol : SOAP 1.1
Adapter Engine: Integration Server
3. I need exactly how the webservices request is passing through sender SOAP Adapter.
After completion of ur scenario u can use XML spy for testing ur scenario.
Refer this Blog how to send SOAP message from XML Spy
Invoke Webservices using SAPXI
Web Services Testing: SAP Netweaver Platform
http://www.crosschecknet.com/web_services_testing_SAP.php
Using the SOAP inbound channel of the Integration Engine
XI: Propagation of meaningful error information to SOAP Client
An Overview of SOAP
Refer the following blogs for SOAP sender Configuration:
How to Use the XI 3.0 SOAP Adapter
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/d23cbe11-0d01-0010-5287-873a22024f79
How Tou2026Set Up a Web-Service-Related Scenario with SAP XI
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/befdeb90-0201-0010-059b-f222711d10c0
have a look at this weblog:
How to use Client Authentication with SOAP Adapter
SOAP Adapter
http://help.sap.com/saphelp_nw04/helpdata/en/69/a6fb3fea9df028e10000000a1550b0/content.htm
Architecture of connector for SAP XI
http://publib.boulder.ibm.com/infocenter/wbihelp/v6rxmx/index.jsp?topic=/com.ibm.wbia_adapters.doc/doc/sap_xi/sapximst14.htm
Configuring the Sender SOAP Adapter
http://help.sap.com/saphelp_nw04/helpdata/en/fc/5ad93f130f9215e10000000a155106/content.htm
Security Settings for the Sender SOAP Adapter
http://help.sap.com/saphelp_nw04/helpdata/en/1f/7e2441509fa831e10000000a1550b0/content.htm

Sending SOAP request from XI and writing a scheduler for this

Dear XI Experts,
My scenario is as follows.
We have two landscapes
1)     XI, R/3
2)     Client System(Remote, Other than SAP)
Now we have to pull the data from client system using WSDL (There will be one method for pulling the data in the WSDL file). The WSDL is provided by the client. We are importing that WSDL as external definition in Integration Repository and implementing the scenario SOAP to XI to RFC and configuring it Integration Directory.
Remember the client will not send the data to XI. Only we have to pull the data as mentioned above.
Problems:-
(i)     How to send SOAP request to the client using XI only?
(ii)     How to write a scheduler for this?
please help us.
Thanks...
Praveen Gujjeti

Ur Suggestion
"My proposition looks like that. in R/3 you have scheduled RFC call in some program. This RFC calls XI and XI is calling using SOAP adapter your client. Then response go back to your RFC and you can handle this data."
As you mentioned, I am not scheduling any RFC call in R/3. If you go through my first query u can find two points where I am having some doubts......
How to send SOAP request to the client using XI only? Is it possible to send a SOAP request from XI?
If so,
(ii) How to write a scheduler for this? So that it will invoke the webservice and get the data from client application(system)

Error 401 while sending SOAP Request to XI

hi friend ..
i am getting Error 401 while sending SOAP Request to XI..
can u suggest me where may be the error?
thanks..

Hi,
Refer these threads:
Testing XI SOAP scenario via XMLSpy
Re: SOAP Sender ADAPTER 401 No Authorisation
Re: XI Web Service - Code: (401) Unauthorized.
Try soap client https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/9b16d790-0201-0010-4e9b-baa5f42830d8
Regards
Suraj

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:
<i>Message Servlet is in Status OK</i>
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:
<i>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>
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

Sender SOAP Adapter - how to avoid changes of URL for diferent environments

Dear experts,
we have a concern with transports of PI objects in our environment.
Situation:
When we transport SOAP Sender objetcs in PI from Dev to Test the URL (Endpoint) changes automatically the hostname and the business system (target system in SLD). For example:
In Development to call the Web Service (Sender SOAP Adapater):
http://sappid1.evonceib.local:50100/XISOAPAdapter/MessageServlet?senderParty=&senderService=EvonceOSB_PEMP_D&receiverParty=&receiverService=&interface=PEMP_PagadoresMaintain_Async_Out_WS&interfaceNamespace=urn%3Aonce%3Asppemp%3Amanagedatosdepagadorpa_in_pemp
In Test to call the Web Service (Sender SOAP Adapater):
http://sappit1:50100/XISOAPAdapter/MessageServlet?senderParty=&senderService=EvonceOSB_PEMP_T&receiverParty=&receiverService=&interface=PEMP_PagadoresMaintain_Async_Out_WS&interfaceNamespace=urn%3Aonce%3Asppemp%3Amanagedatosdepagadorpa_in_pemp
Problem:
The consuming side only wants to have one endpoint and don't want to touch the development when transporting the consumer. Generally to find a work around via DNS aliases for the hostname should solve the prefix of the URL, but how to handle the difference of Business Systems senderService=EvonceOSB_PEMP_D and senderService=EvonceOSB_PEMP_T in the URL?
In the SLD I can not maintain two BS with the same name, when I do not define a transport target the import fails.
So anybody has an idea how to get exactly the same URL for diferent environments?
Thank you in advance,
Best Regards,
Karsten Blankenstein

Hi ,
It is recommended to use different environmemt for Dev,testing,Production. So your PI server host name and port will be different for every environment.
So URL will differ.
however if you dont want to change Business system Name then go for BUSINESS SERVICE/COMPONENT instead of BUSINESS SYSTEM. It will be same in every environment and also dont need to maintain anything in SLD

Sender SOAP Adapter problem in PI 7.1

Hello Everyone,
I have a problem with Sender SOAP Adapter
In PI 7.0 i am able to receive the messages through sender SOAP Adapter for both HTTP and HTTPS. But when i am testing in PI 7.1 i am unable to receive any messages at Adapter level for both HTTP and HTTPS
All sender leagcy system are getting different error messages like
1. 400 HTTP Bad request.
2. Invalid request.
3. BAPI error message
Could any one please assist me in this problem.
Thanks
Vick

Hi Vick,
Try like this......in ID from your sender agreement in which you have your sender SOAP comm channel, from menu select Display WSDL and then copy the WSDL URL and give it to source applications to use it.............create a service user for them to access PI 7.1 server while sending the SOAP req msg.............
your source applications may have to generate proxy from this WSDL URL in their application and then they can send a SOAP req msg to your PI 7.1 server............
Regards,
Rajeev Gupta

Sender SOAP Adapter - problem

Hi,
After reading through the forums I understood that SOAP adapter turns green only with the first message.
I have set everything up and sending a test message with XML Spy:
<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
     <SOAP-ENV:Body>
          <m:SIMPLE_OUT_MI xmlns:m="http://test.com/soapTest">
               <TEXT>TEST</TEXT>
          </m:SIMPLE_OUT_MI>
     </SOAP-ENV:Body>
</SOAP-ENV:Envelope>
XMLSpy returns me an empty message back:
<SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
     <SOAP:Header/>
     <SOAP:Body/>
</SOAP:Envelope>
I can not see the message in SXMB_MONI and the adapter stays gray.
Where do I look for the problem ?

Hi Vick,
Try like this......in ID from your sender agreement in which you have your sender SOAP comm channel, from menu select Display WSDL and then copy the WSDL URL and give it to source applications to use it.............create a service user for them to access PI 7.1 server while sending the SOAP req msg.............
your source applications may have to generate proxy from this WSDL URL in their application and then they can send a SOAP req msg to your PI 7.1 server............
Regards,
Rajeev Gupta

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.

Sender SOAP Adapter parameter problem

Hi,
My scenario is Web service to RFC. I configured XI (7.0) and tested the scenario with Altova Xml Spy, it works. However the ones that are going to call the service say that they need a sevice with a XmlNode parameter.
They are going to use VB.NET to call the service. What should I do?
Please tell me how to
1. Reconfigure XI to accept XmlNode parameter in sender SOAP adapter(I think this is not possible since XmlNode is a language specific element which should not be used for the sake of compatibility in Web Services)
or
2. How to explain this to them ?
Regards,
-Tarik

Please refer to this blog http://blogs.msdn.com/kaevans/archive/2006/04/06/570223.aspx
Cheers
Fernand

Sender SOAP adapter error 401

Hello All,
Here the scenario is SOAP -> XI -> SAP ECC.
When the webservice is seding the message I am getting error in Sender SOAP channel.
Message is not going to Integration Engine.
Its failing with 401Un Authorized in sender soap adapter channel.My sender soap channel is plain channel with no authentication check and certificated etc.When webservice is seding request to XI its sending wit some usernmae which was there on XI box.I am facing this issue in Quality Env. The same is working fine in Dev box.
Please give me the list of points that I need to check here.
Thanks,
Regards,
Naresh

Hi,
I am facing this issue in Quality Env. The same is working fine in Dev box.
Once the scenario is transported from Dev to QA the location where the Webservice is hosted will also change
Hence you will have to change the target URL .....just the HostName / IP address and the port for all the webservices (that you transported to QA)
Once you are in QA and with no change to the URL the sender (which I suppose is also in QA env) will be still trying to ping the same old Dev-URL....in such situation the sender is bound to get UnAuthorized error....
So one in all change the URL in your WebService to point to QA and then test....
Same logic applicable to QA --> PROD
Regards,
Abhishek.

Duplicate check not working in sender soap adapter

Hi guys,
I have an urgent problem. I am using a Sender Soap Adapter (quality of service Best Effort) to receive certain web services requests and send back synchronous responses.
I have ticked the parameters "Use Encoded Headers" and "Use Query String" to implement duplicate check.
For this reason I am expecting XI to return errors of the following type when the sender systems posts duplicates:
<SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:Category>XIServer</SAP:Category>
<SAP:Code area="PERSIST">MSGGUID_EXISTING</SAP:Code>
<SAP:P1>D00B71AC7AEBDEB3E011E5E43C49D97B</SAP:P1>
<SAP:P2>CENTRAL</SAP:P2>
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Message ID D00B71AC7AEBDEB3E011E5E43C49D97B for pipeline CENTRAL, version already exists in system</SAP:Stack>
<SAP:Retry>N</SAP:Retry>
</SAP:Error>
However, although the duplicates go into an error status, the system is responding with the following message:
<SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:Category>XIAdapter</SAP:Category>
<SAP:Code area="BPE_ADAPTER">SYSTEM_FAILURE_INTERNAL</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>An internal error has occurred</SAP:Stack>
<SAP:Retry>N</SAP:Retry>
</SAP:Error>
Can anybody tell me how to force XI to return a message type "MSGGUID_EXISTING" when it catches duplicates? Or if there is any configuration I can change?
Many thanks,
Aldo

OK, this problem is resolved.
XI seams to send the error SYSTEM_FAILURE_INTERNAL the first time it receives a duplicate message and sends the MSGGUID_EXISTING error on the following attempt to post the same message.
Cheers.
Aldo
Edited by: Aldo Lazzarini on Sep 23, 2011 6:50 AM
Edited by: Aldo Lazzarini on Sep 23, 2011 6:53 AM

Query PI 7.1 - Sender SOAP Adpater & Testing

Similar Messages

Maybe you are looking for