SOAP Asynchronous Interface

Hi,
I have a senario where I will get the SOAP Message as a source and I need to send a Unique ID for the SOAP sender but this is to be done in Asynchronous way.
Is this is possible, if yes how?
Thanks
Amaresh

Hi Raj.
I think you are right but not at all. Since SOAP works over HTTP, it's sync. Your SOAP client will always receive a response code.
XI allows you to configure SOAP sender for async processing (although XI returns response code), but this only is valid in the scenario described by Amaresh if he develops a webservice for receiving the Unique ID as response when available.
If the generation of Unique ID (asynchronously) in the proxy takes a long time, I don't think that sync/async bridge is a good option because the SOAP client (waiting for the ID) will probably get timeout (usually 30 or 60 seconds), if you don´t change the timeout parameter of course. So, if SOAP is the only way to communicate the sender system, I would develop a webservice, invoked by XI, to receive the ID.
Regards,
Gari.

Similar Messages

  • Asynchronous Interfaces treated as Synchronous one?

    Hi eXperts,
    I'm now having a weird problem on an Asynchronous inbound interface in a SOAP-XI-R/3 scenario.
    When data coming through XI into R/3, the proxy is called, and works fine. But after the proxy call, a short dump happens in CL_PROXY_FRAMEWORK->XI_PROCESS_PAYLOAD saying the payload is 'null'. Since this is an Asynchronous interface, the payload would certainly be 'null' after the proxy call. So the problem is why this method even be called after the proxy?
    I checked the stack and found that CALL_PIPELINE_SYNC is used instead of CALL_PIPELINE_ASYNC, and I believe this might be the problem: SAP is treating this as an syschronous interface. However after checking settings in IR, both inbound and outbound interfaces are asynchronous.
    Has someone met this before? Does anybody know why SAP is treating an asynchronous interface as a synchronous one?
    Thanks in advance for your help.
    Regards
    Luis

    Hi,
    Did you check sender SOAP Adapter configuration ? What is the quality of service you mentioned ? it should be EO in your case.. check out this..
    also check is this proxy method is giving back the response.. check SXMB_MONI->Trace..
    Hope this helps,
    Regards,
    Moorthy

  • Synchronous - asynchronous interface (RFC - XI - jdbc)

    hello to everybody!
    i want configure a synchronous - asynchronous interface (RFC - PI - jdbc) whit my PI 7.1
    This RFC send 2 output tables to PI/XI and i want write it into 2 different tables in a SQL Server Database.
    How can i do it?
    i tried whit one mapping to a unique outbound datatype...but only header table was insert and not rows.
    i tried whit 2 Receiver Interfaces but i have on mapping the follow error:
    Multiple inbound interfaces not supported for synchronous calls
    so??
    other possibility?
    BPM?
    please help me
    Thanks
    Alessandro

    Hi,
    I have a similar problem; I have JMS - PI - RFC synchronous scenario. I will receive message from JMS, and depending on the data received, I should call either of two RFCs (NOT BOTH). The BAPI return message should then be sent back to JMS.
    Hence, I have one "Sender/Outbound" Message Interface, one receiver determination for that Message Interface - in which there is "one" receiver (backend SAP system).
    In "Interface Determination", I specifed the two BAPIs as two Interfaces, and defined conditions based on "context objects" - since I need to know the Interface Mapping "dynamically"
    However, I get the error - "Multiple inbound interfaces not supported for synchronous calls ". any suggestions on how to proceed?
    I am posting this question here as it is a related issue. Hope it is fine.
    Thanks,
    Archana

  • RFC TO SOAP ASYNCHRONOUS

    Hi all,
    My scenario is rfc to soap asynchronous.  when i am sending data from rfc it is showing success in sxmb_moni and in RWB.
    but it is reaching to third party webservice but it is not taking the data. then it is showing following error in SXMB_MONI response what was the issue
       *<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>*
    *- <!--  Call Adapter*
      -->
    - <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="HTTP">ADAPTER.HTTP_EXCEPTION</SAP:Code>
      <SAP:P1 />
      <SAP:P2 />
      <SAP:P3 />
      <SAP:P4 />
      <SAP:AdditionalText>HTTP 415 Unsupported Media Type</SAP:AdditionalText>
      <SAP:Stack />
      <SAP:Retry>M</SAP:Retry>
      </SAP:Error>
    and the version are PI 7.1,  and third party webservice is  Oracle 11g and weblogic server 10.3.2.0
    and my next question is in same scenario
    I checked using TCP Gateway PI to third party webservice .it is showing following error
    This is posted data
    POST /AdvancedMeteringInfrastructure-UtilitiesDeviceERPSmartMeterBulkCreateRequest-context-root/UtilitiesDeviceERPSmartMeterBulkCreateRequest_OutPort?wsdl HTTP/1.0
    *Accept: /*
    Host: 172.16.5.211:7002
    User-Agent: SAP-Messaging-com.sap.aii.af.sdk.xi/1.0505
    content-id: payload-a3368e536e4311dfa3dc00237d5e14c0(at)sap.com
    content-type: application/xml
    Content-Length: 1662
    SOAPACTION: "http://sap.com/xi/IS-U/Global2/UtilitiesDeviceERPSmartMeterBulkCreateRequest_Out"
    <?xml version="1.0" encoding="UTF-8"?>
    <ns1:UtilitiesDeviceERPSmartMeterBulkCreateRequest xmlns:ns1="http://sap.com/xi/SAPGlobal20/Global"><MessageHeader><ID schemeID="Device" schemeAgencyID="www.infotech.com">4446364534314343</ID><UUID schemeID="Device" schemeAgencyID="www.infotech.com">DF6E41CC-79E7-81F1-B9A3-0013725B3FAB</UUID><CreationDateTime>2010/06/02 T18:07:42</CreationDateTime><TestDataIndicator>true</TestDataIndicator><ReconciliationIndicator>true</ReconciliationIndicator><SenderBusinessSystemID>SLD_B001</SenderBusinessSystemID><RecipientBusinessSystemID>SLD_B002</RecipientBusinessSystemID></MessageHeader><UtilitiesDeviceERPSmartMeterCreateRequestMessage><MessageHeader><ID schemeID="Device" schemeAgencyID="www.infotech.com" schemeAgencySchemeAgencyID="001">4446364534314343</ID><UUID schemeID="Device" schemeAgencyID="www.infotech.com">DF6E41CC-79E7-82F1-B9A3-0013725B3FAB</UUID><CreationDateTime>2010/06/02 T18:07:42</CreationDateTime><TestDataIndicator>true</TestDataIndicator><ReconciliationIndicator>true</ReconciliationIndicator><SenderBusinessSystemID>SLD_B001</SenderBusinessSystemID><RecipientBusinessSystemID>SLD_B001</RecipientBusinessSystemID></MessageHeader><UtilitiesDevice><ID schemeID="DEID" schemeAgencyID="115">1200000120001564</ID><StartDate>2010.06.02</StartDate><EndDate>9999.12.31</EndDate><SerialID>1200000120001564</SerialID><MaterialID schemeID="MaterialID" schemeAgencyID="MPL_002">85</MaterialID><ProductUniqueItemID schemeID="Smart Meter" schemeAgencyID="MPL_002">SM1165HS</ProductUniqueItemID></UtilitiesDevice></UtilitiesDeviceERPSmartMeterCreateRequestMessage></ns1:UtilitiesDeviceERPSmartMeterBulkCreateRequest>
    ERROR
    HTTP/1.1 415 Unsupported Media Type
    Connection: close
    Date: Wed, 02 Jun 2010 12:26:33 GMT
    Content-Length: 0
    X-ORACLE-DMS-ECID: 0000IZsc9VaF^6WFLzyGOA1Bpe3k00007J
    X-Powered-By: Servlet/2.5 JSP/2.1
    Please give me the solution.
    Thanks
    Anil

    Hi,
         looks like there can be a problem with the webservice provider to which you are passing the data via SOAP adapter...
    check that webservice using some other tools like XMLSPY or SOAPUI...
    if everything is fine with that then test the entrie scenario by passing the same data...then you will get to know the exact problem...
    HTH
    Rajesh

  • Synchronous / Asynchronous Interface

    I am kinda confused about Synchronous interface/asynchronous.. When we talk about synchronous are we talking synchronous for the entire interface (From Sender system to XI to Receiver system) or we are just referring to Connection with XI system?
    If somebody can explain a classic synchronous and asynchronous scenario with a good example, I would really appreciate it..

    > I am kinda confused about Synchronous
    > interface/asynchronous.. When we talk about
    > synchronous are we talking synchronous for the entire
    > interface (From Sender system to XI to Receiver
    > system) or we are just referring to Connection with
    > XI system?
    XI decouples the sender and receiver of messages through interfaces. So, if the interface for the sender (called outbound interface) is synchronous, the sender is blocking on the request and the sender expects a response from XI synchronously.
    Consider
    System A -> XI -> System B
    If A's interface in XI is synchronous, then XI has to send a response to A synchronously. However XI may have an asynchronous interface with B. i.e. XI may post a message to B and may not expect a response from B. But A will not care what kind of processing happened between and B as long as A got a response back.

  • Soap/xml interface

    hi,
    I have a requirement to implement soap/xml interface over http. App server is mostly weblogic.
    Can you please provide any inputs in this regard?
    thanks.

    J2EEHunger wrote:
    hi,
    I have a requirement to implement soap/xml interface over http. Okay.
    App server is mostly weblogic.Mostly? Interesting.
    Can you please provide any inputs in this regard?If you're asking how to build an application using soap/xml that you can deploy to weblogic, then you've come to the wrong place. Hint: Google is useful for general questions.

  • Synchronous-Asynchronous Interface with Java Proxy

    Hi Gurus!!
    I have an Interface which begins on SAP with a call to an asynchronous ABAP Proxy . Xi sends the message to Java Proxy Server. This Java Proxy Server calls to a Java Proxy Client that sends the response to SAP through XI. This response is taken on SAP on ABAP Proxy Inbound.
    These arquitechture is a requirement, because the time between the request and the response could be 30 minutes and the user shouldn't be waiting the response synchronously.
    Is there any way to the user could manage the response in the same "thread" that he opened in the request?
    I hope have been clear enough.
    Thanks and regards,
    Manuel Míguez.

    The only possibility I could think of is using correlation. There also you have the limitation of java proxy as it does not support adapter modules. Could you use SOAP for your scenario?
    JMS receiver could use inherent properties to define correlations. But as your case is non-JMS, you have to define it manually. Say, if your receiver system is X, then the request from XI to system X should carry its message ID information. While X created the response message, it should use this message ID as the correlation ID for the response message. This could be achieved using an adapter module.
    I guess you were not looking for such a complex solution.
    Regards,
    Prateek

  • IDOC to SOAP asynchronous scenario Error handling

    Need an expert!!!!!!!!! advise on  error handling for IDOC--PI--
    SOAP scenario.This is a asynchronous scenario where PI is calling a Legacy system using SOAP adapter.My question is how i can do error handling in this scenario.If i get an alert in pi with payload variable that would be fine, do i need to use BPM and if that is tthe case what will be steps.
    Appreciate your help.
    Manish

    Hello Manish,
    My question is how i can do error handling in this scenario.
    Use the standard alert framework. Search on SDN / SAP Help for details.
    do i need to use BPM and if that is tthe case what will be steps.
    BPM is not required to raise alerts, as this is an async call.
    Regards,
    Neetesh

  • 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

  • IDOC to SOAP - Asynchronous message

    Dear friends,
    We are working on IDOC-SOAP scenario using Asynchronous communication. The Receiver has SSL Authentication as well. When we are sending requests, the Adapter Engine is showing below details in the Audit log:
    2009-01-13 07:11:40 Success MP: Processing local module localejbs/sap.com/com.sap.aii.af.soapadapter/XISOAPAdapterBean
    2009-01-13 07:11:40 Success SOAP: request message entering the adapter with user J2EE_GUEST
    2009-01-13 07:11:40 Success SOAP: Web Services Security processing...
    2009-01-13 07:11:40 Success SOAP: Web Services Security processing skiped. Empty body...
    2009-01-13 07:11:44 Success SOAP: completed the processing
    2009-01-13 07:11:44 Success SOAP: sending a delivery ack ...
    2009-01-13 07:11:44 Success SOAP: sent a delivery ack
    2009-01-13 07:11:44 Success MP: Leaving module processor
    2009-01-13 07:11:44 Success The message was successfully delivered to the application using connection SOAP_http://sap.com/xi/XI/System.
    2009-01-13 07:11:44 Success The message status set to DLVD
    Why is it skipping the security settings ?
    Other issue : Webservices is giving some response ( Success in case of succesful processing else SOAP XML based Fault message when there is any error at receiver end).
    PI should be notified when there is a fault message from receiver. but we dont want that message sent back to SAP system. Its PI support person should be notified about this. How can I solve this without using BPM.
    highly appreciate for any inputs on this.
    Regards,
    Srini

    You can not do that without BPM. You need wheels to move in a car. You can ask for a car that moves but does not have wheels. Wheels are meant for the movement. Similarly is BPM. May be few of the times you can skip the BPM, but not always.
    VJ

  • JMS Ack for Asynchronous interface

    Hi Experts
    Here My Interface is Proxy to PI to JMS (MQ) asynchronous.
    Once message is processed asynchronously MQ will send the Acknowledgement to PI with different Queue. Then PI need to pick this with sender JMS adapter.. is this approach will work?
    IF it I it worku2019s Please let me know the steps. Here I donu2019t want to use the BPM.
    Thank you
    Srini

    Dear Srinivasreddy
    As you mentiuoned this is an Asyncronous communication, then what are you going to do with response.
    Is your proxy expecting a response?
    In that case you should create a Synchronous interface and not an Asynchronous one.
    Please clarify
    Sourabh

  • Soap-proxy interface

    Hi Experts.
    I have an scenrio, i need to design the two interaces, first one is synchronus interface , it get the request from user (wsdl) and post the data in sap (using proxy) , once the data is arrived in sap, an ackownledgement ( error/ status) sent back to user,
    the second asynchronus interface is to send the response ( to the request sent from first interface) back to the client system
    ( proxy--> soap used)
    my query is how can the  the second interface is triggered in runtime, if i  write the code in report (proxy), do i need to schedule the background job ?
    please explain indetails
    Thanks
    NV

    Hello,
    I have an scenrio, i need to design the two interaces, first one is synchronus interface , it get the request from user (wsdl) and post the data in sap (using proxy) , once the data is arrived in sap, an ackownledgement ( error/ status) sent back to user,
    Receiving any type of response in a synchronous scenario is already an acknowledgement in itself, so no need to do anything additional here aside from configuring a normal synch scenario.
    the second asynchronus interface is to send the response ( to the request sent from first interface) back to the client system
    ( proxy--> soap used)
    my query is how can the the second interface is triggered in runtime, if i write the code in report (proxy), do i need to schedule the background job ?
    Once you have received the response from the first proxy, use its response as your input to the second proxy. No need to schedule a background job because it will be executed as soon as you receive a response from first proxy.
    Hope this helps,
    Mark

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

  • Multiple receivers asynchronous interface

    HI,
    I have a scenario wherein a third party sends file to ECC and some validations are being done at the ECC and a count of the records that have errors, count of records that are processed and a count of the success records are being spit out of SAP as email. Also, a file with those error records are being sent out.
    Now, my question is....I will not be sending the file back if there are no error records but email notification will be sent no matter what so that it includes the total records processed, failed (0 in this case), and success.
    When I use the same outbound proxy, is that possible to accomplish ?
    I mean the situation wherein I will not be sending file but I will be sending email. I have the same outbound interface in both the cases i.e to send emails as well as to send the file back.
    That will be great if someone could shed some light on this. Also, is there anyway I can include the file name that is being sent to SAP in the mapping so that I can mention that in the email saying "Following is the file that was sent..and it has so and so error records...."
    Many thanks.

    Nothing much to think about. Create 180+ communication channels and same number of receiver agreements and interface determinations!
    If you feel that all the 50 FTP servers are part of the same business system, create 1 receiver determination and 180 interface determintions. It might look a bit less messy.
    I have worked in other middleware products. Frankly, this is not how others work!!!! They provide provisions for changing any parameter of a communication channel at runtime.
    All the best,
    kk

  • Proxy To SOAP Asynchronous

    Hi Folks,
        I'm doing a scenario from proxy to soap. in that I'm fetching the data from the tables in the SAP system using the proxy and sending the same to the webservice through the SOAP adapter configured in the Receiver end. basically I have the XI sender adpter & the SOAP receiver adapter. My question here is whicle sending the data if the webservice is down can still the data be sent once the webservice is active ?
    Regards,
      santosh

    Santosh,
    My question here is whicle sending the data if the webservice is down can still the data be sent once the webservice is active ?
    If the web service is down, then the SOAP channel will try 3 times before going into error. Once the service is back up, you can re-send the message from RWB.
    Regards,
    Neetesh

Maybe you are looking for