Synchronous Scenario SOAP to Proxy and Proxy to SOAP

Hi Sdn,
I am new to Synchronous Scenario.
Third party will send SOAP message requesting some information from SAP.
SOAP - > PI -> Proxy SAP
they are expecting a response Proxy - > PI -> SOAP.
Could you please let me know how to design teh Synchronous Scenario in PI .
Thanks

> Create DT and respective MT for Request and Response.
> Create Service Interfaces with Synchronous mode with respective MT's.
> Create Two separate MM with respective Request and Response MT's.
> Create Operation Mapping and call both Request and Response Mappings in it.
> Complete the Configuration part considering Sender SOAP and Receiver ECC Services.
> Configure CC with required parameters in Sender SOAP CC and Receiver XI CC.
> Generate wsdl from Sender agreement and save it as a local file.
> Use SOAP UI or any available Tool for testing purpose. Import the generated wsdl, provide input data and execute the test.
> If you are comfortable with expected result, deliver wsdl to the Sender Party.
> For Inbound Proxy, you can refer initial replies.
Hope it helps.!
Regards,
Sunil

Similar Messages

  • SOAP error in synchronous scenario for ABAP Proxy with Oracle D/B

    Dear Experts,
    I am working in Sender ABAP Proxy <====>SAP PI 7.31 JAVA only <====> Oracle Database. My proxy configuration are working successfully.
    Apart from that, I have maintained a SOAP sender communication channel under the ECC business system with
    Transport Protocol as HTTP
    Message Protocol as XI 3.0
    Adapter Engine as Central Engine
    When I am testing from ECC at Tx SPROXY, I am receiving following error.
    com.sap.engine.interfaces.messaging.api.exception.MessagingException: com.sap.aii.adapter.xi.routing.RoutingException: InterfaceDetermination did not yield any actual interface at com.sap.aii.adapter.soap.web.SOAPHandler.processSOAPtoXMB(SOAPHandler.java:746) at com.sap.aii.adapter.soap.web.MessageServlet.doPost(MessageServlet.java:505) at javax.servlet.http.HttpServlet.service(HttpServlet.java:754) at javax.servlet.http.HttpServlet.service(HttpServlet.java:847) at
    1. In XI3.0 protocol, I can not select BE but when selected HTTP 1.0 as Message protocol then I can find the BE.
    2. No Response message is shown in ECC when testing the message.
    3. How do Receiver JDBC adapter for Oracle Database is configured 
    4. What would be Message Protocol for Oracle Database i.e. XML SQL Format or Native SQL format for Select operation.
    Please guide.. All your inputs will be appreciated......
    Regards
    Rebecca

    Dear Indrajit,
    Appreciate your inputs.. Yes I have configured all the ABAP proxy configurations and there no question of missing any thing as Tx SLDCHECK in ECC is working perfectly fine.
    But still to go, some of the queries needs more input.
    1.In ID, i have created a Sender SOAP communication channel with listed details.
    Transport Protocol as HTTP
    Message Protocol as XI 3.0
    Adapter Engine as Central Engine
    Is there any parameters which I may be missing from Module tab of Synchronous SOAP Cc ?
    2. In the Cc monitoring, the JDBC receiver status shows "Database operation successfully completed" but I could not find any response data from database. The Message monitoring should have 2 messages for 1 trigger, but I could find only 1 message by SOAP only?
    Sorry to bother experts...Please answer in sequence...
    Regards
    Rebecca

  • Message flow in SAP PI 7.31 JAVA only for ABAP Proxy synchronous scenario with Oracle DB

    Dear Experts,
    I am working on a synchronous scenario Sender ABAP Proxy <===> SAP PI 7.31 JAVA only <===> Oracle Database.I have successfully
    configured all the proxy configurations as well both Sender SOAP and JDBC receiver channels are showing no error when pinged from
    Cc monitoring in NWA.
    1.During testing at Tx SPROXY , I am triggering a message and after 5 minutes I receive an PARSING error message with 2 messages in ECC
    local IE i.e. Tx SXMB_MONI.
    Note : In NWA , I can see only 1 message that too in cancelled status.
    2.Seeing the trace of the messages I assume that the messages have not moved from sender ECC system. I am still confused with flow of message
    from the Message Audit log. Audit log of error messages.Could any one share the full Audit log of a successful message generated in SAP PI 7.31 JAVA only.
    3.I observed that the QIN Scheduler status in ECC is in INACTIVE status. There is no queue id for 2 messages generated in ECC. Does
    it should in ACTIVE status in Tx SMQR..
    Regards
    Rebecca

    Hi Thomas,
    Valuable inputs..
    1. Since I don't have any audit log for successful message, would you be able to share referring to the
    below screenshot whether the message was put into receiver JDBC adapter and JDBC adapter tried to retrieve the Select response from Oracle Database.
    2.I have done some setting in Advance mode of the receiver JDBC to increase the time out and other parameters as per SAP note but still the issue is same. If you perhaps have some experience in such scenarios, please share some input so that I can ask the Oracle Database administrator exactly what is required from our side.
    3.Regarding the slow response from Oracle , there was some suggestion that the datatype of the request and response should match the column name of the Oracle database. I did that.. Do you have any more suggestion that may be hampering the generation of the response message from the Oracle like SAP note or document.
    Regards
    Rebecca

  • No response message in Proxy to JDBC synchronous scenario

    Dear Team,
    I am working on synchronous scenario Sender ABAP proxy <===> SAP PI 7.31 <===> Oracle Database.All the necessary proxy configuration has been successfully tested.
    Business Scenario:
    ABAP proxy will send a single Vendor Id to Oracle DB as request and in return , it has to retrieve all the columns related to Vendor as response.Oracle Database stores all the Vendor information.There are 11 columns including the vendor Id in the view for the Vendor records.
    Design :
    For Request structure:
    a-->Created MT for Sender ABAP Proxy with only 1 field for Vendor Id.
    b-->Created MT for Receiver JDBC  with Action as SELECT , Table with "View Name" , Access with Constant Blank for all 11 column and Key as Vendor Id.
    I have been following  the link and Bhavesh Kantilal document.
    http://help.sap.com/saphelp_nw73/helpdata/en/44/7b7171fde93673e10000000a114a6b/content.htm?frameset=/en/44/7b7855fde93673e10000000a114a6b/f
    rameset.htm&current_toc=/en/ca/b977f1c7814201954f20bb87ad7aab/plain.htm&node_id=71
    For Response structure:
    Created MT for Receiver JDBC with All the column names.
    Created MT for target ABAP ECC with the same 11 column name of JDBC response.
    Note :
    1.Database team shared a excel file as a sample payload which has all the column names of a vendor and I created my DT with the same naming conventions as they are maintaining in their database i.e. Column names are in CAPs, in the same order and even the special characters in the column name.
    2. The PING test connection for Cc works fine to database.
    Please read out my queries as the I am not receiving any response from Oracle DB and gives error as timeout exception:
    1.Since I am trying to retrieve all the column of the view , am I doing the correct procedure of putting all the column name in the JDBC request structure and making a Select statement. Can I add < * > to fetch all the column name and if so where can I add it.
    2. Whats the difference between SELECT and SQL_QUERY and on what circumstances I can add it?
    3. How can I test ICO in ID?
    4. Can I use any SOAP tool to test the messages? Is there any functionality in NWA to test the messages directly to JDBC .
    Hope all your inputs can improve my design part.
    Regards
    Rebecca

    Hi Rebecca,
    Did you go through all of these links below?
    PROXY to JDBC- SYNC
    Proxy to JDBC Sync, with Idoc Receiver
    JDBC to PROXY Sync Scenario | SCN
    JBDC Receiver Insert Statement Response
    Re: Synchronous JDBC select
    receiver JDBC structure
    Regards,
    Jannus Botha

  • Proxy Receiver Synchronous scenario

    Hi EveryBody,
    I am working on a synchronous scenario in which Proxy is receiver.
    I have generated the PROXY for the inbound synchronous Interface and also have created a Program
    in se38.
    I need to call a RFC function module in the code and push the data from Proxy to RFC and also
    have to send the response from RFC to XI via Proxy.
    Can somebody help me out on the same?
    Helpful answers will be rewarded points.
    Thanks,
    RK

    Hi Rupash,
    For example...
    method ZXI_II_MI_PROXY_IN_DNI_NOMBRE~EXECUTE_SYNCHRONOUS.
    **** INSERT IMPLEMENTATION HERE **** ***
    DATA:
    lv_ID type char10,
    lv_NAME type char30.
    lv_ID        =  input-MT_PROXY_DNI-DNI.
    *lv_NAME      =  input-MT_PROXY_DNI-NOMBRE.
    CALL FUNCTION 'ZXI_001'
    EXPORTING
       P_DNI          = lv_ID
    IMPORTING
       P_NOMBRE = lv_NAME.
    output-MT_PROXY_NOMBRE-NOMBRE = lv_NAME.
    endmethod.
    FUNCTION zxi_001.
    ""Interfase local
    *"  IMPORTING
    *"     VALUE(P_DNI) TYPE  CHAR10 OPTIONAL
    *"  EXPORTING
    *"     VALUE(P_NOMBRE) TYPE  BEZEI30
      CHECK NOT p_dni IS INITIAL.
      SELECT SINGLE nombre INTO p_nombre
       FROM zxi_0001
       WHERE dni = p_dni.
    ENDFUNCTION.
    Regards,
    Carlos

  • SOAP to Proxy synchronous scenario

    Hi,
    Hope you are all doing well.
    I have a SOAP to Proxy synchronous scenario. As part of this scenario, the data structure of the response sent by SAP is different from the response sent back to the SOAP requester. Hence I have used request message mapping between the SOAP request sent by requester and the one passed on to SAP and response message mapping between the response sent by SAP and the one passed on to the requester. Both the message mappings are incorporated in a single Interface mapping.
    The problem is that the interface is behaving like a asynchronous one, i.e., request is passing over to SAP but though the proxy is giving a response back, the same is not coming over to XI.
    It would be really helpful if you can let me know what might have gone wrong.
    regards
    Debansu

    Hi,
    you should have that:
    1. Two Message Mapping:
    1.1. a Message Mapping for request    (called MM_request)    , from MT_SOAP_request     to   MT_Proxy_request.
    1.2. a Message Mapping for response (called MM_response) , from MT_Proxy_response   to   MT_SOAP_response.
    2. One Operation Mapping (in PI 7.1) or Interface Mapping (in PI 7.0) from SI_SOAP to SI_ Proxy with:
    2.1 in the tab "request", so from MT_SOAP_request     to   MT_Proxy_request    , give your Message Mapping "MM_request".
    2.2 in tab "response"   , so from MT_Proxy_response   to   MT_SOAP_response, give your Message Mapping "MM_response".
    3. In you Directory, you define a flow like that:
    from SI_SOAP to SI_ Proxy by using your Operation Mapping.
    If I missed nothing, that's all.
    MT = Message Type
    MM = Message Mapping
    SI =Service Interface in PI 7.1  or Message Interface in PI 7.0.
    regards.
    Mickael
    Edited by: Mickael Huchet on Oct 19, 2011 4:07 PM

  • SOAP - XI- PROXY synchronous  scenario

    Hi Experts,
    I have a
    SOAP -
    XI -
    PROXY  Synchronous Scenario
    I have done the following things ESR and ID
    ESR:
    1. Created DT and respective MT for Request and Response.
    2. Created Service Interfaces with Synchronous mode with respective MT's.
    3. Created Two separate MM with respective Request and Response MT's.
    4. Created Operation Mapping and call both Request and Response Mappings in it.
    Integration Directory (ID):
    1. Configured considering Sender SOAP and Receiver ECC Services.
    2. Configured CC with required parameters in Sender SOAP CC and Receiver XI CC.
    3. Generate wsdl from Sender agreement and save it as a local file.
    I am getting error in receiver agreement. Do I need to specify any Module parameters in Module TAB for Sender CC or Receiver CC to synchronous scenario.
    Please hep me out.
    Thanks

    Hi Ram,
    I am getting error in receiver agreement. Do I need to specify any Module parameters in Module TAB for Sender CC or Receiver CC to synchronous scenario.
    It looks like you did not create a receiver agreement, or if you did, it did not match the interface that is given or configured in Interface Determination. Can you recheck your configuration?
    Regards,
    Mark

  • Proxy to File Synchronous Scenario

    Hello,
    My scenario is 
    SAP System ----->(Proxy)   PI -------->(File)  FTP
    Synchronous Scenario
    I have been using the RequestResponseBean and ResponseOnewayBean module in the Sender Request Adapter channel to convert the file adapter from Asynchrounous to Synchronous scenario.
    While Triggering Data From Proxy the receiver request channel is placing the file in the FTP.
    But the sender Response channel is saying that "No suitable Sender  agreement found" error.
    Also in the Audit log :SOAP: call failed com.sap.engine.interfaces.messaging.api.exception.MessagingException: Error encountered while executing mapping: com.sap.aii.af.service.mapping.MappingException: 204 .
    Getting the above error.
    Also I need the Sender Response Channel to pick the file after 10 minutes of placing the file in the FTP by the receiver Request channel.
    Please help on this.

    My question is , can I use graphical mapping as I am using a java class for content conversion?
    You can use as long as the structure generatde by the JAVA program is same as the source-message structure of the message mapping.
    I have developed a java code for content conversion and it is working fine. How to use this .jar file in XI?
    In my opinion this should be the adapter module....as the conversion needs to be done in the channel and inclucing it as a mapping wont help.
    Regards,
    Abhishek.

  • "SOAP:Fault" in scenario with ABAP proxy client

    Hello,
    I realized the scenario CRM40_Basis620(ABAP proxy client)->XI->File.
    XI:
    The sender communication channel is a XI adapter (Parameters: HTTP 1.0, XI 3.0, Integration Server, Security profile unchecked, Security level - HTTP).
    CRM:
    The proxy generation is ok.
    SLDCHECK is ok.
    All RFC destinations are ok.
    APPINT_200_620 for CRM was installed and configured well (I think so, but...).
    When I ran the ABAP proxy client on CRM, sxmb_moni(CRM) returned the text for the XML Message (Display-CallIntegrationServer-Payloads-TraceDocument):
    <?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
    - <SAP:TraceHeader xmlns:SAP="http://sap.com/exchange/MessageFormat">
      <Trace level="1" type="B" name="CL_XMS_TROUBLESHOOT-ENTER_PLSRV" />
      <Trace level="1" type="T">****************************************************</Trace>
      <Trace level="1" type="T">* *</Trace>
      <Trace level="1" type="T">* *</Trace>
      <Trace level="1" type="T">XMB entry processing</Trace>
      <Trace level="1" type="T">system-ID = EST</Trace>
      <Trace level="1" type="T">client = 300</Trace>
      <Trace level="1" type="T">language = E</Trace>
      <Trace level="1" type="T">user = BABKIN_RA</Trace>
      <Trace level="1" type="Timestamp">2007-08-06T13:55:12Z</Trace>
      <Trace level="1" type="T">* *</Trace>
      <Trace level="1" type="T">* *</Trace>
      <Trace level="1" type="T">****************************************************</Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_UC_EXECUTE" />
    - <!--  ************************************
      -->
      <Trace level="1" type="T">Message-GUID = DC4424A659314CF18F500002A541D0E7</Trace>
      <Trace level="1" type="T">PLNAME = SENDER</Trace>
      <Trace level="1" type="T">QOS = EO</Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_ASYNC" />
    - <!--  ************************************
      -->
      <Trace level="1" type="T">Get definition of external pipeline = SENDER</Trace>
      <Trace level="1" type="T">Get definition of internal pipeline = SAP_SENDER</Trace>
      <Trace level="1" type="T">Generated prefixed queue name = XBTS0004</Trace>
      <Trace level="1" type="T">Setup qRFC Scheduler OK!</Trace>
      <Trace level="1" type="T">----
    </Trace>
      <Trace level="1" type="T">Going to persist message + call qRFC now...</Trace>
      <Trace level="1" type="T">NOTE: The following trace entries are always lacking</Trace>
      <Trace level="1" type="T">- Exit WRITE_MESSAGE_TO_PERSIST</Trace>
      <Trace level="1" type="T">- Exit CALL_PIPELINE_ASYNC</Trace>
      <Trace level="1" type="T">Async barrier reached. Bye-bye !</Trace>
      <Trace level="1" type="T">----
    </Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
    - <!--  ************************************
      -->
      <Trace level="1" type="B" name="CL_XMS_MAIN-PERSIST_READ_MESSAGE" />
      <Trace level="1" type="T">Note: the following trace entry is written delayed (after read from persist)</Trace>
      <Trace level="1" type="B" name="SXMS_ASYNC_EXEC" />
    - <!--  ************************************
      -->
      <Trace level="1" type="T">----
    </Trace>
      <Trace level="1" type="T">Starting async processing with pipeline SENDER</Trace>
      <Trace level="1" type="T">system-ID = EST</Trace>
      <Trace level="1" type="T">client = 300</Trace>
      <Trace level="1" type="T">language = E</Trace>
      <Trace level="1" type="T">user = BABKIN_RA</Trace>
      <Trace level="1" type="Timestamp">2007-08-06T13:55:12Z</Trace>
      <Trace level="1" type="T">----
    </Trace>
    - <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_SYNC">
      <Trace level="1" type="T">Get definition of pipeline PID= SENDER</Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-LOOKUP_INTERNAL_PL_ID" />
    - <Trace level="1" type="B" name="PLSRV_CALL_INTEGRATION_SERVER">
      <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV" />
    - <!--  ************************************
      -->
      <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL" />
    - <!--  ************************************
      -->
    - <Trace level="1" type="B" name="CL_XMS_PLSRV_CALL_XMB-ENTER_PLSRV">
      <Trace level="1" type="T">URL for integration server read from global configuration</Trace>
      <Trace level="1" type="T">URL= http://SRMDEV.oao.sng:8011/sap/xi/engine?type=entry</Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-SET_TECHNICAL_ROUTING_PROPERTY" />
    - <Trace level="1" type="B" name="CL_XMS_PLSRV_CALL_XMB-CALL_XMS_HTTP">
      <Trace level="1" type="System_Error">HTTP-client: error response= <SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/"> <SOAP:Header> </SOAP:Header> <SOAP:Body> <SOAP:Fault xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/"><faultcode>SOAP:Client</faultcode><faultstring>Error during conversion of XI message</faultstring><faultactor>http://sap.com/xi/XI/Message/30</faultactor><detail><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="SECURITY">INBOUND_SECURE_LEVEL</SAP:Code><SAP:P1>DC4424A659314CF18F500002A541D0E7</SAP:P1><SAP:P2/><SAP:P3>HTTP</SAP:P3><SAP:P4/><SAP:AdditionalText/><SAP:ApplicationFaultMessage namespace=""/><SAP:Stack>Message DC4424A659314CF18F500002A541D0E7 was sent with ''. Channel configuration, however, requires 'HTTP' </SAP:Stack></SAP:Error></detail></SOAP:Fault> </SOAP:Body> </SOAP:Envelope></Trace>
      </Trace>
      <Trace level="1" type="System_Error">Exit XMB because of system error!</Trace>
      <Trace level="1" type="System_Error">System-Error: HTTP.HTTP_STATUS_CODE_NEQ_OK</Trace>
      <Trace level="1" type="System_Error">HTTP status code 500 : Error during conversion of XI message</Trace>
      <Trace level="1" type="B" name="CL_XMS_TROUBLESHOOT-ENTER_PLSRV" />
      </SAP:TraceHeader>
    I think the main problem is the parameter "HTTP Security level" for the channel, but not sure.
    Does anybody know where to find a solution?
    Regards,
    Roman

    Hi Roman
    There is no need for an XI adapter for client proxy.... we only use that for server proxies.
    Vaibhav

  • File to Proxy synchronous scenario

    Experts,
       I am working on a File to proxy synchronous scenario.
    I am doing the content conversion at the sendre side by using java program as  input structure is very complex so have to go fr java code. Its a  txt file at sender side.
    Once I read the file in XI, am doing a graphical mapping ( just one to one mapping)  then using the server proxy , a service entry is getting created then response am sending to the receiver.
    My question is , can I use graphical mapping as I am using a java class for content conversion? both in one scenario is possible?
    I have developed a java code  for content conversion and it is working fine. How to use this .jar file in XI?
    Can Any one help me wz thsi one?
    Thanks in Advance
    Virendra

    My question is , can I use graphical mapping as I am using a java class for content conversion?
    You can use as long as the structure generatde by the JAVA program is same as the source-message structure of the message mapping.
    I have developed a java code for content conversion and it is working fine. How to use this .jar file in XI?
    In my opinion this should be the adapter module....as the conversion needs to be done in the channel and inclucing it as a mapping wont help.
    Regards,
    Abhishek.

  • SAP Client Proxy to Webservice Synchronous Scenario

    Hi Experts,
    I have an outbound Synchronous Scenario.In which i have to trigger a Client Proxy from SAP side and Connect to a WebService using PI.
    I have with me the WSDl and URL for Webservice.Can anyone guide me with the necessary steps.
    Regards
    Gaurav

    Hi gaurav,
    From client proxy u have to send request and get the response back...
    So, for this create 2 corresponding data types and message types. and mapping will be between request message type which u created and request wsdl message and another mapping for response wsdl message and response message type which u created.
    create service interface outbound synchronous(give the message types which u created) and inbound synchronous(give the wsdl request and response messages).
    Regards,
    Sunitha

  • Java Proxy - XI - RFC Synchronous Scenario OUTBINDING Problem.

    Java Proxy -> XI -> RFC Synchronous Scenario. Problem
    Hi,
         I'm doing a Java Proxy -> XI -> RFC Syncronous Scenario.
         A Java Server Socket is running as a Demon. When a client make a request to the Java Server Socket, this one call Java Proxy Client and set up the parameters.
         The first time that execute the scenario it works perfectly but no the next one and so on.
         The error when I check the monitor (TCODE: SXMB_MONI) is in PLSRV_OUTBOUND_BINDING.
    <Trace level="1" type="B" name="CL_XMS_PLSRV_OUTBINDING-ENTER_PLSRV">
      <Trace level="1" type="T">no outbound binding found.</Trace>
      <Trace level="1" type="T">No standard agreement found for , DES210_DEV, , JPX_DEV, urn:servipago:SERVIPAGO_SAP_02, mi_os_t1</Trace>
    </Trace>
    <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
    And it has sense, because my scenario doesn't begin with the execution of FM (RFC).
    A Hint, my services in the first try are:
         <b>Sender Service:</b>          JPX_DEV (Java Proxy Client)
         <b>Receiver Service:</b>     DES210_DEV (R/3 4.6C)
    But the second try and so on the services that I saw in the monitor are:
         <b>Sender Service:</b>          DES210_DEV (R/3 4.6C)
         <b>Receiver Service:</b>     JPX_DEV (Java Proxy Client)
    I can't understand why they swich each other.
    Any idea?

    Hi,
    Outbound binding problem is because of Reciever Determination/Agreement is not activated or refreshed correctly.
    Try to recreate or refresh and activate it. Then check it.
    also do the cache refresh in SXI_CACHE.
    Also in go to Integration Builder(XI home page)->Administration->Cache Overview and do all the cache refresh.
    Hope this helps
    Regards,
    Moorthy

  • Scenario SOAP - PI - PROXY - Exception handling

    Hi all,
    I have the following scenario:
    Scenario SOAP(.NET)  <-> PI <-> PROXY
    When I raise an exception at the proxy side, PI will be informed with an exception text that an exception has occured.
    In the .NET receiver I only get an application exception (but not the real exception) - no exception text
    How can I get the exception text at .NET side?
    There is a datatype of type "XXXXException".
    But I can't use this class in the catch block because it is not inherited from class exception.
    regards

    Hi,
    thanks for your answer.
    But how to handle the exception in my C# client:
    I have created the .NET classes out of the WSDL
    There is a class ZQM_SVC_QMEL_GETException generated, but I don't know how to use it.
    try
                res.ES_SVC_QMEL = client.MI_OSRBG_QM_MASTERDATA_AUDIT_QMEL_GET_SYNC_OUT("123");
            catch (ZQM_SVC_QMEL_GETException  ex1)
    This coding is not working because the class ZQM_SVC_QMEL_GETException is not inherited from the class exception.
    This class has an attribute Nodes and several methods getSchema, ReadXML, WriteXML.
    But I don't know how to use it.
    Any idea?
    regards

  • Werb services to proxy- synchronous scenario

    Hi experts,
       Can anyone help me with the detailed scenario of  synchronous WEB SERVICES TO PROXY step by step. I tried searching in sdn but  no luck.
    Also tell me  here that XI will expose the Outbound Interfaces as a Web Service Interface.  how the  Web Service Description (WSDL File) will be generated for the Interfaces in Integration directory?
    Also mapping is not required here.
    Thanks
    Veeru

    what types of business systems have to create for this webservices to proxy kind of scenario
    you dont need multiple business systems....just create one business system in SLD and then import it into ID.
    Assign the inbound message interface to this business system and configure your scenario.
    Check if a Business System already exists for this SAP system....if there is another Proxy/ IDOC/ RFC scenario developed for this SAP system then there should be a Business System created...just re-use the same.
    If you need help on how to create SLD then just make a simple search on SDN.....you will find good blogs/ documents.
    On the Sender side (WS) you need to create Business Service in ID.
    Regards,
    Abhishek.

  • Timeout Error in a Synchronous XI - SOAP scenario

    Hi All,
    I have developed a Synchronous ABAP proxy to SOAP web service scenario.
    ECC sends an ABAP proxy request to PI, PI forwards the request to the target system as SOAP message.
    I have checked the interface via SOAP UI and it works fine but when we run the end-to-end flow it always ends with a Synchronous timeout error.
    The Target system confirms that the response is sent from there side but in PI we are not receiving any response and the system throws a  timeout error.
    As both PI and the Target system are in same Landscape there is no firewall in between.
    Please suggest what can be the possible reasons and the approach to resolve the same?
    Thanks in advance,
    Shashank

    Hi,
    "The target system needed credentials for one  inbound interface, so for this synchronous scenario(PI<->Target) should the target system maintain credentials some where when the response is sent back to PI as the SOAP channel is on Java Stack?"
    Generally for receiver channel we get the user name and password from target system ie web service.
    How did you test in SOAPUI? did you test it with providing username and password or not?
    even if web service requires user/pwd then it will throw 401 unauthorized error.
    check this
    can you go to RWB-->component monitoring-->adapter Engine-->communication channel monitoring-->your channel
    check if the channel has any errors/exceptions logs.
    Regards,
    Muni.

Maybe you are looking for