Webservice Interface - Soap Adapter

Hi,
Is there a way to put an XML payload into one field?
Our scenario is the following:
XI receives a request and is then sent to a 3rd party web service using SOAP adapter.  The web service expects the XML payload to be put into the field, strRequest.
In the example below the XML payload,
"<ns0:Request xmlns:ns0="XXXXXX"> <name>John</name></ns0:Request>"
would go into the field, strRequest.
<?xml version="1.0" encoding="utf-8"?>
<soap:Envelope xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
  <soap:Body>
    <Request xmlns="http://XXXXXX">
      <strRequest>
"<ns0:Request xmlns:ns0="XXXXXX"> <name>John</name></ns0:Request>"
</strRequest>
      <strID>string</strID>
    </Request>
  </soap:Body>
</soap:Envelope>
Thanks.

Duke,
Yes you can do it. Using CDATA you can do it.
Check this weblog:
/people/michal.krawczyk2/blog/2005/11/01/xi-xml-node-into-a-string-with-graphical-mapping
Also the same issue is discussed here:
Printint XML string using  XSLT mapping
Regards,
---Satish

Similar Messages

  • Webservices for soap adapter

    Hi,
    how to Create Webservices for XI message interfaces?
    Please help me out.
    Thanks.

    hi
    For more information check this links
    /people/shabarish.vijayakumar/blog/2007/11/07/walkthrough--soap-xi-rfcbapi
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/7ccd3e4e-0501-0010-95ae-afa58cb46b75
    /people/siva.maranani/blog/2005/09/03/invoke-webservices-using-sapxi
    /people/community.user/blog/2006/10/24/exposing-bapi-as-web-services-through-sap-xi
    http://www.riyaz.net/blog/index.php/2007/12/10/xipi-consuming-xi-web-services-using-web-dynpro-part-i/
    http://www.riyaz.net/blog/index.php/2007/12/11/xipi-consuming-xi-web-services-using-web-dynpro-part-ii/

  • Webservice for proxy to SOAP adapter interface

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

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

  • XI SOAP adapter vs webservice testing tools

    Actually I have creted simple xslt mapping and managed to come up with exactly in the format of endpoint request format of the webservice.
    here is the payload( I have created the SOAP Envelop, Header and body in the payload)
    <?xml version="1.0" encoding="utf-8"?>
    <SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:eb="http://www.ebxml.org/namespaces/messageHeader" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:xsd="http://www.w3.org/1999/XMLSchema">
      <SOAP-ENV:Header>
        <eb:MessageHeader SOAP-ENV:mustUnderstand="1" eb:version="1.0">
          <eb:ConversationId>sucesss</eb:ConversationId>
          <eb:From>
            <eb:PartyId type="urn:x12.org:IO5:01">applevac.com</eb:PartyId>
          </eb:From>
          <eb:To>
            <eb:PartyId type="urn:x12.org:IO5:01">webservices.sabre.com</eb:PartyId>
          </eb:To>
          <eb:CPAId>P4XC</eb:CPAId>
          <eb:Service eb:type="sabreXML">session</eb:Service>
          <eb:Action>SessionCreateRQ</eb:Action>
          <eb:MessageData>
            <eb:MessageId>mid:[email protected]</eb:MessageId>
            <eb:Timestamp>2001-02-15T11:15:12Z</eb:Timestamp>
            <eb:TimeToLive>2001-02-15T11:15:12Z</eb:TimeToLive>
          </eb:MessageData>
        </eb:MessageHeader>
        <wsse:Security xmlns:wsse="http://schemas.xmlsoap.org/ws/2002/12/secext" xmlns:wsu="http://schemas.xmlsoap.org/ws/2002/12/utility">
          <wsse:UsernameToken>
            <wsse:Username>5555</wsse:Username>
            <wsse:Password>password</wsse:Password>
            <Organization>L5x5</Organization>
            <Domain>DEFAULT</Domain>
          </wsse:UsernameToken>
        </wsse:Security>
      </SOAP-ENV:Header>
      <SOAP-ENV:Body>
        <eb:Manifest SOAP-ENV:mustUnderstand="1" eb:version="1.0">
          <SessionCreateRQ>
            <POS>
              <Source PseudoCityCode="P4XC"/>
            </POS>
          </SessionCreateRQ>
        </eb:Manifest>
      </SOAP-ENV:Body>
    </SOAP-ENV:Envelope>
    I want XI to post just the payload and nothing else so....
    I selected Do not use envelope in the adapter configuration because we have every thing( SOAP envelop, header and body in the payload) but it is not working as i am still getting the same error message before implementing this xslt.
    Error Message:
    <StackTrace>com.sabre.universalservices.base.session.SessionException: errors.session.USG_CONVERSATION_ID_REQUIRED at com.sabre.universalservices.gateway.control.SecurityInterceptor.executeOnRequest(SecurityInterceptor.java:116) at com.sabre.universalservices.base.interceptor.Interceptor.execute(Interceptor.java:113) at com.sabre.universalservices.base.interceptor.InterceptorChain.applyInterceptors(InterceptorChain.java:32) at com.sabre.universalservices.base.interceptor.InterceptorManager.process(InterceptorManager.java:121) at com.sabre.universalservices.gateway.control.WSGateway.onMessage(WSGateway.java:415) at com.sabre.universalservices.gateway.control.WSGateway.handleRequest(WSGateway.java:313) at com.sabre.universalservices.gateway.control.WSGateway.doPost(WSGateway.java:247) at javax.servlet.http.HttpServlet.service(HttpServlet.java:709) at javax.servlet.http.HttpServlet.service(HttpServlet.java:802) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter
    Do you have any idea like XI will add anything to this pay load when it sends out to the webservice?
    If i take the payload from the XI and try it in SOAPUI(tool to test webservice, you would know it already ) it works fine, I mean I was able to get the proper response but in XI it does not work.
    Any help in this regards is highly appreciated.
    we are using PI 7.0 and SP 9.
    Message was edited by:
            Venkat Marni
    Message was edited by:
            Venkat Marni

    Hi,
    Finally I could solve the problem.
    I was actually trying to post the information from the http client at the sender and receiver side I am getting the error.
    Later i have actually created the webservice for my sender interface in XI then post the info using the SOAPUI(3rd party tool) to post the info to XI and then Xi will communicate the webservice using SOAP adapter then I got the proper response from the webservice.
    In this whole episode I guess there is some thing wrong in using a htp client but technically we should be able to use http client as XI will take the payload and use xslt mapping to come up with target interface soap message( but i do not know why XI failed in that).
    thanks for all your help and hope this is clear.
    thanks,
    Venkat

  • SOAP adapter and dynamic target URL

    My scenario: synchronous communication ABAP Proxy <=> XI <=> External WebServices.
    There is a need to have configurable (dynamic) target URL for SOAP Adapter. This target should be configurable from ABAP Proxy. Any idea how can I achieve my goal?
    Some additional notes why I need configurable target URL. I've multiple WebService instances which has identical interfaces and the only difference is target URL. I see no need to define for each webservice different SOAP Adapter. The other thing is that customer want to have configuration of destination (target) url on backend system (where ABAP Proxy is used).

    Check http://help.sap.com/saphelp_nw70/helpdata/EN/29/5bd93f130f9215e10000000a155106/frameset.htm
    It's possible to set the URL for Soap dynamically.
    To process adapter attributes in the message header of the XI message, set the Use Adapter-Specific Message Attributes indicator and the Variable Transport Binding indicator.
    You can evaluate the following attributes in the message header:
    Description: You can set the entire URL.
    Technical name: TServerLocation

  • SOAP Adapter Basics

    Dear Friends,
    I need some crystal clear idea on SOAP Adapter Basics.
    Sample scenario for my understanding:
    When i send a Customer Request details webservices from a third party Webserver through sender soap adpater(Sync Interface) .
    It reaches PI system and then reaches SAP ECC to fetch the customer details through Proxies.
    In turn it gives customer repsonse details back to third party Webserver through the same sync Interface Soap Adapter.
    1.I keen to know what is really happening between Sending Webserver and SAP PI system through Sender soap adapter.
    2 When we use sender soap adpater do we really need to create webservice in Intgeration Directory, is it really mandatory.
    3. I keenly like to know for the above scenario what exactly sender soap adapter is doing ...as step by step guide.

    HI,
    U have to follow the steps and provide the WSDL URL,message interface name, namepsace once u give all the information it will generate the WSDL file and at the end u will get the save option u save that WSDL on ur desktop.
    Case one:
    Webservice- XI- SAP system.
    here remote client will act as sender. in this case from ID we create the WSDL file and send it to sender Webservice. This Sender will use the URL which we give while creating WSDL file from ID and send the message to XI.
    Case two:
    SAP System-XI-Webservice Receiver
    Here Werservice provide the WSDL file and we import that WSDL file in XI and use as a data type. IN the SOAP receiver we will mention the WSDL file URL through which XI will send the data to Webservice.
    chirag

  • Webservice call to XI Interface through SOAP Adapter from a Web application

    I  am getting  the following error, when I try to call the XI Interface using soap adapter from a web application.
    ERROR  :
    SystemError:
              <context>XIAdapter</context>
              <code>ADAPTER.JAVA_EXCEPTION</code>
              <text><![CDATA[
    com.sap.aii.af.ra.ms.api.DeliveryException: XIAdapterFramework:GENERAL:com.sap.aii.af.ra.ms.api.DeliveryException
    at some time i am getting the following error.
    faultCode: HTTP
    faultSubcode:
    faultString: (500)Internal Server Error
    faultActor:
    faultNode:
    faultDetail:
         {}:return code:  500
    &lt;SAP:Error&gt;&lt;SAP:Category&gt;XIServer&lt;/SAP:Category&gt;&lt;SAP:Code&gt;RCVR_DETERMINATION.NO_RECEIVER_CASE_BE&lt;/SAP:Code&gt;&lt;SAP:Stack&gt;No receiver could be determined&lt;/SAP:Stack&gt;&lt;/SAP:Error&gt;
         HttpErrorCode:500
    (500)Internal Server Error
    can any of  one help to resolve this.
    Thanks  in advance

    Ganie
    You are getting the exception at very first point of Pipeline Service i.e Receiver Determination, do compare the namespace, Sender Interface Name & Sender Service name with the payload you are sending from web-application, they must be exactly same.
    The best way to get the test payload is suggested in above reply.

  • 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.

  • Problems with SOAP Adapter/Interface

    Hi Experts,
    we currently try and experiment with XI 3.0 Stack 09 and the SOAP adapter respectively.
    We started with a simple interface (foo..., see wsdl attachment) that we want to provide by XI.
    All configurations (SLD, Integration Repository, Integration Directory) should have been done accordingly as we suppose, similar to other szenarios we have already implemented.
    When we send a SOAP request based on a generated wsdl to XI we get the exception at the bottom of this text, containing e.g.
    com.sap.aii.messaging.srt.BubbleException: error during conversion [null "null"];
    com.sap.aii.messaging.util.XMLScanException: Parsing an empty source. Root element expected!
    For sending the SOAP message we used XMLSpy.
    Did someone have similar problems or can give us an working WSDL example, or some hint?
    Thanks in advance,
    Klaus Lukas
    foo.wsdl
    <?xml version="1.0" encoding="ISO-8859-1"?>
    <wsdl:definitions xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:p1="urn://poreceive.xi.pse.siemens.com" targetNamespace="urn://poreceive.xi.pse.siemens.com" name="foo_out_sync">
         <wsdl:types>
              <xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="urn://poreceive.xi.pse.siemens.com" targetNamespace="urn://poreceive.xi.pse.siemens.com">
                   <xsd:element name="foo" type="foo_DT"/>
                   <xsd:complexType name="foo_DT">
                        <xsd:annotation>
                             <xsd:appinfo source="http://sap.com/xi/TextID">
                        fe0bb241d2a011d9cd15e9729ee2f568
                        </xsd:appinfo>
                        </xsd:annotation>
                        <xsd:sequence>
                             <xsd:element name="item" type="xsd:string">
                                  <xsd:annotation>
                                       <xsd:appinfo source="http://sap.com/xi/TextID">
                                fe0bb240d2a011d9acede9729ee2f568
                                </xsd:appinfo>
                                  </xsd:annotation>
                             </xsd:element>
                        </xsd:sequence>
                   </xsd:complexType>
              </xsd:schema>
         </wsdl:types>
         <wsdl:message name="foo">
              <wsdl:part name="foo" element="p1:foo"/>
         </wsdl:message>
         <wsdl:portType name="foo_out_sync">
              <wsdl:operation name="foo_out_sync">
                   <wsdl:input message="p1:foo"/>
                   <wsdl:output message="p1:foo"/>
              </wsdl:operation>
         </wsdl:portType>
         <wsdl:binding name="foo_out_syncBinding" type="p1:foo_out_sync">
              <soap:binding xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" style="document" transport="http://schemas.xmlsoap.org/soap/http"/>
              <wsdl:operation name="foo_out_sync">
                   <wsdl:input>
                        <soap:body xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" use="literal"/>
                   </wsdl:input>
                   <wsdl:output>
                        <soap:body xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" use="literal"/>
                   </wsdl:output>
              </wsdl:operation>
         </wsdl:binding>
         <wsdl:service name="foo_out_syncService">
              <wsdl:port name="foo_out_syncPort" binding="p1:foo_out_syncBinding">
                   <soap:address location="http://xxxxxxxx:8000/XISOAPAdapter/MessageServlet?channel=:Foo_SOAP_Service:SOAP_Foo_out&version=3.0&Sender.Service=Foo_SOAP_Service&Interface=urn%3A%2F%2Fporeceive.xi.pse.siemens.com%5Efoo_out_sync" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"/>
              </wsdl:port>
         </wsdl:service>
    </wsdl:definitions>
    soap message incl. error
    <?xml version="1.0"?>
    <!-- see thedocumentation -->
    <SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
    <SOAP:Body>
    <SOAP:Fault>
    <faultcode>SOAP:Server</faultcode>
    <faultstring>error during
    conversion</faultstring>
    <detail>
    <s:SystemError
    xmlns:s="http://sap.com/xi/WebService/xi2.0">
    <context>XIAdapter</context>
    <code>XMLScanException</code>
    <text><![CDATA[
    com.sap.aii.af.mp.module.ModuleException
    at com.sap.aii.af.mp.soap.ejb.XISOAPAdapterBean.process
    (XISOAPAdapterBean.java:697)
    at
    com.sap.aii.af.mp.module.ModuleLocalLocalObjectImpl3.process
    (ModuleLocalLocalObjectImpl3.java:103)
    at com.sap.aii.af.mp.ejb.ModuleProcessorBean.process
    (ModuleProcessorBean.java:221)
    at
    com.sap.aii.af.mp.processor.ModuleProcessorLocalLocalObjectImpl0.process
    (ModuleProcessorLocalLocalObjectImpl0.java:103)
    at com.sap.aii.af.mp.soap.web.MessageServlet.doPost
    (MessageServlet.java:543)
    at javax.servlet.http.HttpServlet.service
    (HttpServlet.java:760)
    at javax.servlet.http.HttpServlet.service
    (HttpServlet.java:853)
    at
    com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet
    (HttpHandlerImpl.java:385)
    at
    com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleReques
    t(HttpHandlerImpl.java:263)
    at
    com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet
    (RequestAnalizer.java:340)
    at
    com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet
    (RequestAnalizer.java:318)
    at
    com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebConta
    iner(RequestAnalizer.java:821)
    at
    com.sap.engine.services.httpserver.server.RequestAnalizer.handle
    (RequestAnalizer.java:239)
    at com.sap.engine.services.httpserver.server.Client.handle
    (Client.java:92)
    at com.sap.engine.services.httpserver.server.Processor.request
    (Processor.java:147)
    at
    com.sap.engine.core.service630.context.cluster.session.ApplicationSessio
    nMessageListener.process(ApplicationSessionMessageListener.java:37)
    at
    com.sap.engine.core.cluster.impl6.session.UnorderedChannel$MessageRunner
    .run(UnorderedChannel.java:71)
    at com.sap.engine.core.thread.impl3.ActionObject.run
    (ActionObject.java:37)
    at java.security.AccessController.doPrivileged(Native Method)
    at com.sap.engine.core.thread.impl3.SingleThread.execute
    (SingleThread.java:94)
    at com.sap.engine.core.thread.impl3.SingleThread.run
    (SingleThread.java:162)
    Caused by: com.sap.aii.messaging.srt.BubbleException: error during
    conversion [null "null"]; nested exception caused by:
    com.sap.aii.messaging.util.XMLScanException: Parsing an empty source.
    Root element expected!
    at
    com.sap.aii.messaging.srt.xmb.XMBWebServiceExtension.onResponseToWS
    (XMBWebServiceExtension.java:936)
    at
    com.sap.aii.messaging.srt.xmb.XMBWebServiceExtension.invokeOnResponse
    (XMBWebServiceExtension.java:602)
    at com.sap.aii.messaging.srt.ExtensionBubble.onMessage
    (ExtensionBubble.java:58)
    at com.sap.aii.af.mp.soap.ejb.XISOAPAdapterBean.process
    (XISOAPAdapterBean.java:576)
    ... 20 more
    Caused by: com.sap.aii.messaging.util.XMLScanException: Parsing an
    empty source. Root element expected!
    at com.sap.aii.messaging.util.StreamXMLScannerImpl.open
    (StreamXMLScannerImpl.java:104)
    at com.sap.aii.messaging.mo.DefaultItem.setData
    (DefaultItem.java:294)
    at
    com.sap.aii.messaging.srt.xmb.XMBWebServiceExtension.makeItemFromPayload
    (XMBWebServiceExtension.java:972)
    at
    com.sap.aii.messaging.srt.xmb.XMBWebServiceExtension.onResponseToWS
    (XMBWebServiceExtension.java:879)
    ... 23 more
    ]]></text>
    </s:SystemError>
    </detail>
    </SOAP:Fault>
    </SOAP:Body>
    </SOAP:Envelope>

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

  • Defining a Webservice for an XI SOAP Adapter

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

    redefined question

  • SOAP Adapter = Webservice???

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

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

  • Call Webservice with XI SOAP Adapter

    Hi there,
    I can't find sufficient information in the other posting about my scenario therefore I start a new again about XI and webservice.
    These parts are working:
    file adapter to XI and the SOAP Adapter is calling the Webservice (in the logfile I see the request from the XI)
    These parts aren't working:
    the response from the webservice
    Now my question:
    Is it necessarily to create a new Message Interface with communication channel from the webservice to XI or is it sufficient with an synchrony Message Interface and can I take a look of the response in the XI_Monitor.
    Where I can find information about an similarly scenario?
    THX for helping comments
    Kind Regards Johann

    Hi Johann,
             As others have adviced you dont need a seperate communication channel for the response message. Declaring your message interface as synch is enough.
    Also can you check <b>SXMB_MONI</b> for the request and the response messages. Just use transaction SXMB_MONI. and see if you get checked flags(successfull) or a red flag (error) for your messages.
    But Could you pls tell me if your are using the BPM for your scenario?? 
    If you are not getting response from the web service it could aalso be that the WEB Service is not working properly.
    First try to access the web link for the website using IE.
    Pls read the following for your reference:
    <b>In the SENDER SOAP ADAPTER, you will need to put the URL provided by the company and the SOAP ACTION to invoke a particular WEB METHOD. You will also need to provide URL Authorization, Proxy settings.
    make sure you are using the right SOAP ACTION.</b>
    Hope this helps or revert back.
    Regards,
    Ashish

  • Invoking a Webservice using a SOAP adapter

    Hi,
          I have the following scenario.
    SAP ABAP outbound proxy <-> SAP XI <--> External webservice.
    The above call is a synchronous call from SAP R/3 and a receiver soap adapter is configured for the Webservice.
    I am getting the following error messages when I try to run the scenario.
    1)ADAPTER.SOAP_EXCEPTION.
    2)<SAP:AdditionalText>
    soap fault: Server did not recognize the value of HTTPHeaderSOAPAction
    </SAP:AdditionalText>
    What could be the possible reasons for the error message?
    In the target URL of the soap adapter I am specifying the path till .asmx.
    Thanks,
    Leo

    Hi,
    There are 2 pieces of data that must be provided in the SOAP receiver adapter.  Both of them can be obtained from the WSDL of the soap service provider.
    1.  Target URL, which can be obtain from the attribute "location" of the "address" element in the WSDL.
    2.  SOAP Action, which can be obtain from the "soapAction" attibute of the "operation" element in the WSDL.
    Regards,
    Bill

  • Setting interface name dynamically from client for SOAP Adapter...

    Hi,
    does anyone have experience in setting the sender interface name in the HTTP-SOAP request dynamically? I have followed the instructions in "How To Use the XI 3.0 SOAP Adapter" on page 17 (see also SAP Note 856597) which say:
    "If you select Use Encoded Headers and Use Query String,
    [...]The sender SOAP adapter creates the XI message header according to the
    information provided in the query string. [...] In the sender SOAP adapter, you can use only some of the parameters, but the first
    parameter must always be the version. For example, you send from the Web service client to the following URL: http://<host>:<j2ee-port>/XISOAPAdapter/MessageServlet?channel=<party>:<service>:<channel>&version=3.0&Interface=http%3A
    %2F%2Fsap.com%2Ftest%5ETest
    This will overwrite the default interface and namespace of the sender channel."
    This is exactly what I need! However, what I actually get as a response following this description is a SOAP:Fault with a java.lang.StringIndexOutOfBoundsException: String index out of range: -1.
    Has anyone got this to work properly?
    Thanks in advance.

    Thank you for your input. I am using the following format for the call (with "x" standing for one letter each):
    http://xix.xxx.xx.xxx:5xx00/XISOAPAdapter/MessageServlet?channel=:xx_xxx_xxx_xxxx:xx_xxx_x_SOAP_S&version=3.0&Interface=http%3A%2F%2Fxxxxxxxx.xx%2Fxxxxxx%2Fxxxxxxxxxxxxxxxxxxxxxxxx%5Exxxxxxxxxxxxxxxxxxxxxx
    Anything wrong with that? With unchecked "Use Encoded Headers" and "Use Query String" it works fine (default interface) but as soon as I set these flags I get the SOAP-Fault response.
    We are on XI 3.0 SPS18.

  • Generate Message Interface for SOAP Adapter

    Hi All,
    I want to implement a scenario like this:
      ABAP System -> RFC Adapter -> XI -> SOAP Adapter -> Web Service
    Currently the WSDL of the web service is known. It is http://www.abysal.com/soap/AbysalEmail.wsdl
    How can I generate the inbound message interface in XI according to the WSDL?
    Thanks
    Jerome
    Message was edited by: Jerome Zhao
    Message was edited by: Jerome Zhao

    Hi Jerome,
    Import the WSDL as an external definition and then you can create a inbound Message interface based on that external definition.
    Regards,
    Sridhar

Maybe you are looking for

  • No externally managed transaction is currently active for this thread

    Got the following exception after updating an entity bean and call persist method. Code the given below the exception. Exception [TOPLINK-23010] (Oracle TopLink - 10g Release 3 (10.1.3.0.0) (Build 060118)): oracle.toplink.exceptions.TransactionExcept

  • Where does the ipad back up stored

    where does the ipad back up stored

  • Windows explorer stops working when i open any folder containing .mpg files.

    it started happening after i recovered my windows 7 with One Key recovery system.i have installed latest drivers and eliminated viruses but the problem persists..plz help

  • Cover Flow Freeze

    This problem is frustrating (is there any other kind?). When I use the cool, 3D, Cover Flow feature and flip through the cover art, the system freezes. The cursor doesn't move....nothing. It works for about 5 seconds until the system realizes that I'

  • Error Message 0:104

    I just converted a Word document to a PDF with CreatePDF and when I went to open it on the website it comes up with this message; "There is a problem with Adobe  Acrobat/Reader.  If it is running, opease exit and try again (0:104)' Please help becaus