Target URL - Receiver SOAP Adapter

Hi experts,
I would like to know if the "Target URL" parameter in the Receiver SOAP Adapter is a case sensitive one.
Point will be given,
Tks
Daniela Machado

From my experience, I have used the Receive SOAP adapter to contain the URL of the Sender SOAP adapter of XI itself and in these calls the URL was not case sensitive ( the hostname and port are not case sensitive ) but the Business System , Comm Channel Name , Interface Name and Namespace are case sensitive.
When calling a true webservice, I never paid real importance to the case sensitivity as I used to take the URL from the WSDL provided by the Webservice.
Though not the answer to your question hope it helps.
Regards
Bhavesh

Similar Messages

  • Error when setting dynamically the target URL in receiver SOAP Adapter

    Hi,
    I'm setting dynamically (from the mapping) the target URL in the receiver SOAP adapter:
    String url = "http://mosxd30:50000/XISOAPAdapter/MessageServlet?senderParty=&senderService=DUM&receiverParty=&receiverService=&interface=SI_OA_CustomInvoiceData&interfaceNamespace=urn:repsol.com:laboratory:firma";
    DynamicConfiguration conf = (DynamicConfiguration) container.getTransformationParameters().get(StreamTransformationConstants.DYNAMIC_CONFIGURATION);
    DynamicConfigurationKey key = DynamicConfigurationKey.create("http://sap.com/xi/XI/System/SOAP", "TServerLocation");
    conf.put(key, url);
    The receiver adapter fails with:
    "invalid content type for SOAP: TEXT/HTML; HTTP 401 Unauthorized"
    Reading weblogs, etc, the most probable cause for this is a wrong target URL, but then what I did was to set it as a fixed URL in the C.Channel, and it worked, so the URL is fine.
    In the communication channel, I'm using "Configure user authentication", with a user and password, and what I think it's happening is that if I use another different URL dynamically, the channel is ignoring the user authentication settings.
    Any ideas?
    Thanks

    I forgot to say that I've checked the SAP note "FAQ Soap adapter", and it says:
    Q: I get an authorization error "401 Unauthorized" from the adapter's servlet. What went wrong?
               A: The adapter's servlet is protected by default. You must use one of the user names assigned in security role xi_adapter_soap_message for component XISOAPAdapter. Please consult the documentation for Visual Administrator to view and change the security setting.
               The user authentication of the SOAP adapter is not part of the SOAP adapter but of the web container of the J2EE engine. The default authentication setting is defined in the web.xml descriptor file of the SOAP dapter web application. This setting may be modified from Visual Administrator with some restriction. Please refer to the security documentation for the J2EE engine.
               Please note that 710 onwards there is no Visual Administrator instead the Netweaver Administrator is to be used to assign the roles to the user to access the SOAP adater servlet.The user must be assigned one of the following roles SAP_XI_IS_SERV_USER, SAP_XI_APPL_SERV_USER, SAP_XI_DEVELOPER_J2EE, SAP_XI_ADMINISTRATOR_J2EE.
    The target URL is a sender soap adapter (the result of one interface is sent to another one via soap adapter), and it's this one which is complaining because of the authentication I think. But I don't know why it's ignoring the user authentication flag I'm using.

  • Target url for receiver soap adapter

    Hi everybody
    where will I get the target url to enter in the receiver soap adapter parameters? I got the link from wsdl  under "address location"..But when I open the link from the internet explorer I could see an empty  wsdl 
    <faultstring xml:lang="en">SRT: Wrong Content-Type and empty HTTP-Body received</faultstring>
    thanks
    Ramya

    Hi Ramya,
    When you try opening the URL using web browser, you are not sending any data and hence in response you get an empty message.
    But at the same time, the message shows you that the service corresponding to that URL is invoked, activated and running.
    Give the same URL in your receiver communication channel and try execcuting the scenario, as far as receiver URL is concerned, it should work.
    -Tanaya.

  • 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

  • Error using SSL on Receiver Soap Adapter

    Hi there,
    I'm having some problems on connecting to a third-party application running a webservice (meaning, through Receiver Soap Adapter). The third-party appl. demands us to use a SSL connection (its url starts with https), with user authentication through certificate.
    We've installed SAP Java Cryptographic toolkit and have a proper certificate configured on the KeyStorage entry, on Visual Administrator.
    On Soap Adapter, I've configured HTTP Transport Protocol and have selected the "configure certificate authentication" option and selected the certificate, filled the mandatory fields (target URL and soap action) but I keep getting this error message on SXMB_MONI: "com.sap.aii.af.ra.ms.api.DeliveryException: unable to create a socket".
    Is there anything else than installing SAP Java Cryptographic Toolkit to enable SSL on Soap Adapter? Is there another configurations that need to be done?
    Thanks in advance,
    Henrique.

    Hi
    can u please tell me, how u r able to resolve the problem
    i am also stuck in the same error
    basically i am working on SSO b/w three systems.
    EP>XI>R/3
    i am able to do the SSO between the EP-->XI
    but  when i try with EP-->XI->R/3 it is giving me error at the receiver side means receiver soap adapter is not accepting the SAP Logon Ticket.
    can u please tell me what entries should be given in the certificate authentication fields.
    please provide the solution.
    Thanks & Regards
    Rinku Gangwani

  • Receiver SOAP Adapter (HTTP AXIS)

    Hi Experts,
    I need to use receiver soap adapter to communicate with a WebService, actually it is a AXIS service i can see when i give the soap url in web browser.
    my question is for axis service, does it mean i have to use HTTP AXIS in the receiver channel to request the response for web service server? Can i use HTTP only without AXIS?
    when i use SoapUI to test the webservice, it works fine. But when i use receiver soap adapter with HTTP (without AXIS), it is responding with the belwo error.
    <sap:Error ...>
      <sap:Category>Application</sap:Category>
      <sap:Code area="UNKNOWN">APPLICATION_ERROR</sap:Code>
      <sap:AdditionalText>Application Fault</sap:AdditionalText>
      <sap:ApplicationFaultMessage namespace="http://sap.com/xi/XI/System/Axis/sample">host name</sap:ApplicationFaultMessage>
      <sap:Stack/>
    </sap:Error>
    Experts, please help on this, the major question is HTTP AXIS is required when target web service is an AXIS service?
    Thanks in advance.
    Regards,

    >>my question is for axis service, does it mean i have to use HTTP AXIS in the receiver channel to request the response for web service server? Can i use HTTP only without AXIS?
    You are going to consume webservice. You can use standard SOAP adapter itself to consume the webservice that is built with axis framework.
    Do you have some specific user authentication procedures like SAP Assertion Tickets, username token etc and some specific encapsulation formats (MIME, DIME, MTOM),WS Reliable Messaging  and so then you need SOAP Axis adapter. If you need to consume webservice with standard transport protocol (HTTP or HTTPS) and client authentication etc , our standard SOAP adapter is more than enough.
    Refer this link what axis soap adapter supports

  • Receiver SOAP Adapter - Connection Parameters

    I have a scenario where I need to pass some data (authentication data) to a web service.
    I tried using Connection Parameters - Connection User Authentication, and it seems it does not go through SOAP HEADER.
    Does anybody know I can pass data to a Web Service without using payload??
    Actually I need to pass information set up in communication channel like user authentication.
    Thanks and Regards,
    Fabio Ramos

    Hi Carlos,
    The link(pdf) is opening fine.... Just try again.
    It actully explains your need...
    Also go through this info below and see if it helps:
    1) Check the wsdl message,mapped message (input to the SOAP Adapter)
    2) Check the Target URL in the SOAP Reciever Adapter. Also SOAP Receiver Adapter Parameters -
    http://help.sap.com/saphelp_nw2004s/helpdata/en/29/5bd93f130f9215e10000000a155106/frameset.htm
    3) Try to test the WebService -
    /people/siva.maranani/blog/2005/03/01/testing-xi-exposed-web-services
    4) Also check these links -
    Receiver SOAP Adapter Error: invalid content type for SOAP: TEXT/HTML
    Problems with soap adapter?
    You need to mention the Target URL i.e URL of the WSDL file.
    Regards,
    Abhy
    Message was edited by: Abhy Thomas

  • Changing data structure in the receiver SOAP adapter

    I was wondering whether it is possible to have changing data structure in terms of one receiver SOAP adapter so I could sent data type 1 and 2 to a single XI web service enabled URL and make conditional parsing in terms of the received message ?
    I have a receiver SOAP adapter that ideally should be able to receive two different types of messages. But SOAP adapter is fixed to a sigle message interface that naturally has it's data structure set to just one type. I can just create conditions in terms of the data type 1 message that has been defined in the design side.
    Is it possible achieve this with just one SOAP receiver adapter?

    Henri,
    Please go through the note: 856597 (Quesiton NO 9)
    -Naveen.

  • Receiver SOAP adapter SSL error - client certificate required?

    Hi all,
    Problem configuring SSL in XI 3.0 NW04 SP17....
    I have followed the config steps from Rahul's excellent weblog at <a href="/people/rahul.nawale2/blog/2006/05/31/how-to-use-client-authentication-with-soap-adapter">How to use Client Authentication with SOAP Adapter</a> (my Basis team have done the Visual Admin steps) and am going through his example as it closely matches my requirement. So, I have a test receiver SOAP adapter sending messages to a web service URL defined for a sender SOAP adapter. My test scenario is:
    <b>Sender File -> <u><i>Receiver SOAP -> Sender SOAP</i></u> -> IDoc Receiver -> IDocs in R/3</b>
    The problem components are in italic and underlined above. My Receiver SOAP Adapter has the web service URL, Certificate Keystore Entry and View entered. If, in the Sender SOAP Adapter, I have an HTTP Security Level of HTTPS Without Client Authentication, the interface works fine (note that Rahul suggests you untick the User Authentication in the Receiver but with this Security Level, it seems to work with or without it).
    The problem is when I set HTTPS <b>With</b> Client Authentication in the Sender. I then get the following error in the message monitor:
    SOAP: response message contains an error XIServer/UNKNOWN/ModuleUnknownException - com.sap.aii.af.mp.module.ModuleException: java.security.AccessControlException: <b>client certificate required caused by: java.security.AccessControlException</b>: client certificate required at com.sap.aii.af.mp.soap.ejb.XISOAPAdapterBean.process(XISOAPAdapterBean.java:1111) at com.sap.aii.af.mp.module.ModuleLocalLocalObjectImpl3.process(ModuleLocalLocalObjectImpl3.java:103) at com.sap.aii.af.mp.ejb.ModuleProcessorBean.process(ModuleProcessorBean.java:250) at com.sap.aii.af.mp.processor.ModuleProcessorLocalLocalObjectImpl0.process(ModuleProcessorLocalLocalObjectImpl0.java:103) at com.sap.aii.af.mp.soap.web.MessageServlet.callModuleProcessor(MessageServlet.java:166) at com.sap.aii.af.mp.soap.web.MessageServlet.doPost(MessageServlet.java:421) at javax.servlet.http.HttpServlet.service(HttpServlet.java(Compiled Code)) at javax.servlet.http.HttpServlet.service(HttpServlet.java(Compiled Code)) at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java(Compiled Code)) at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java(Compiled Code)) at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java(Inlined Compiled Code)) at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java(Compiled Code)) at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java(Compiled Code)) at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java(Compiled Code)) at com.sap.engine.services.httpserver.server.Client.handle(Client.java(Inlined Compiled Code)) at com.sap.engine.services.httpserver.server.Processor.request(Processor.java(Compiled Code)) at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java(Compiled Code)) at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java(Compiled Code)) at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java(Compiled Code)) at java.security.AccessController.doPrivileged1(Native Method) at java.security.AccessController.doPrivileged(AccessController.java(Compiled Code)) at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java(Compiled Code)) at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java(Compiled Code)) Caused by: java.security.AccessControlException: client certificate required at com.sap.aii.af.mp.soap.ejb.XISOAPAdapterBean.process(XISOAPAdapterBean.java:843) ... 22 more
    Has anyone got any idea what this could be caused by?
    Many thanks,
    Stuart Richards

    Have you configured the https port with that keystore entry?
    Check out these links:
    http://help.sap.com/saphelp_nw2004s/helpdata/en/b0/881e3e3986f701e10000000a114084/frameset.htm
    http://help.sap.com/saphelp_nw2004s/helpdata/en/5c/15f73dd0408e5be10000000a114084/frameset.htm
    Regards,
    Henrique.

  • Receiver SOAP adapter - User authentication question

    XI experts,
    Here is the scenario - IDOC > XI > SOAP - Ansynchronous call..
    I need your all help to understand the user authentication on the "Receiver SOAP Adapter"... We are using "HTTP" transport protocol.
    I believe, the userid which we entered in the communication channel needs to have proper security on the web server. The Web server URL starts with "http://lsme
    01.xyz.com/...." .
    Question : Is this usrid and password will be encrypted when XI calls this web service?
    If an answer is "NO" then is there anyway we can encrypt it?
    Thanks in advance!
    Points will be given..
    MP

    XI experts,
    I need an answer to the following question....
    The Web server URL starts with "http://lsme01.xyz.com/...." .
    Question : Is this usrid and password will be encrypted when XI calls this web service?
    If an answer is "NO" then is there anyway we can encrypt it?
    Thanks in advance!
    Points will be given..
    MP

  • Receiver SOAP Adapter - Dynamic username & password

    Hi,
    I am working on a scenario where the receiver SOAP adapter will have dynamic user name & password. but the URL remains same. how do we achieve this.
    Thanks,
    Mahesh

    Hi Baskar,
    I have checked all your Replies in SDN related to SOAP Header Creation for Wssec Web Service.
    I am working on a Interface (CRM Proxy to Web Service having wssec) in PI 7.0 SP6. I have created the SOAP Header by using XSLT mapping to pass the username token and password but hardcoding user credentials in the XSLT mapping doesn't sound too neat. And transporting it from D to Q to P is even worse.
    And also i have 2 username and 2 passwords to access to different instances in the same web service. So i have to pass the different Username and Password based on the Instance in SOAP header dynamically using XSLT mapping.
    Therefore i request you help me out on how to pass the Username and password dynamically in the XSLT mapping to Create dynamic SOAP Header to access different instances.
    If possible can you provide step-by-step aproach including XSLT mapping and Code for dynamic SOAP Header creation.
    Thank you very much for your valuable inputs.
    Regards,
    Ajay Kodali.

  • Receiver SOAP Adapter Use Query String

    Hello everybody,
    I want to include in my Receiver SOAP Adapter the message id as part of the URL String, but I need to include only the MessageId value, if I use the Use Encoded Headers and Use Query String options it includes all the header fields as part of the URL, is there a way to define only the fields that I need?, thanks in advance.
    Regards,
    Julio Cesar

    May be you could try to use adapter specific message attribute "TServerLocation". This will help you set the dynamic URL.
    http://help.sap.com/saphelp_nw04/helpdata/en/29/5bd93f130f9215e10000000a155106/frameset.htm
    Regards,
    Prateek

  • Doubt on receiver soap adapter

    hi ,
    do we need to give the server details in the soap receiver details .
    ex: if i want to consume webservice using external definition what are the prequisites required and i need to send the same message in the format of WSDL file .

    Hello Vidya Sagar,
    To configure SOAP receiver communication channel you need Target URL(where actually the web service resides) and SOAP Action ( Service which you are calling). Please see below example Target URL and SOAP Action for testing purpose.
    Target URL Example : http://www.ezzylearning.com/services/CountryInformationService.asmx
    SOAP Action : http://www.ezzylearning.com/services/CountryInformationService.asmx/GetPopulationByCountry
    Here GetPopulationByCountry is the method which I am trying to call.
    Regards
    Sateesh

  • Receiver SOAP Adapter error

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

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

  • In what QOS does the receiver SOAP adapter work BE or EO?

    Hi,
    In what QOS does the receiver SOAP adapter work BE or EO?
    My guess is that it is by default EO, if so how do i make it work like synchronous?
    There is no option to set it explicitly.
    Thanks]
    Shakthi

    Siva,
    In receiving adapter you can't set the status. The receiving QOS is set in the pipeline by using the Sender Comm.channel QOS.
    So for example in SOAP to SOAP scenario, if you set the Sender comm.channel as BE, then through out the Pipeline till it reaches the Receiver Comm.channel the QOS will be considered as BE only( Even though you didn't explicitly said to the Receiver comm.channel).
    Hope it helps!
    raj.

Maybe you are looking for