Acknowlegements for Proxy - XI - SOAP

Hi gurus,
I'm designing a scenario for R3 - XI - non-SAP systems using Proxy & Soap adapters(WS).
I would like to know about the acknowledgement options and how to configure them.
Any links & info provided will be very much appreciated and rewarded.
Thank you.
Regards,
S. Gokhan TOPCU

Hi ,
   For syncronous proxy we will get the acknowledgement back from proxy. use fault message type for rising exceptions.
   For Asyn proxy we won't get acknowledgement back in SXI_monitor in xi. u can monitor the Application errors rised from proxy in RWB -> message monitoring . their select ur proxy bussiness system and monitor. u can rise alert in xi by calling RFC SALRT_CREATE_API from ur proxy code.
u can monitor all Application error in SXI_monitor in ur Application System(R3)
for ack check following link
http://help.sap.com/saphelp_nw04/helpdata/en/f4/8620c6b58c422c960c53f3ed71b432/content.htm
Regards
Pradeep P N
Edited by: Pradeep P N on Dec 17, 2008 10:22 AM

Similar Messages

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

  • Proxy to SOAP in PI 7.1

    Hi Experts
    I have requirement for Proxy to SOAP (Synchronous) and it needs a BPM to get the response from SOAP and post to the Proxy
    Can any send the Prototype
    Thanks
    PR

    BPM design:
    Receive(Async From Proxy) -
    > SyncSend(To SOAP) ---> Send(Async from BPM to Proxy)
    you need to have:
    1) 1 OB Async SI for SAP ---> BPM.......1 ABS Async SI to receive the SAP message into BPM.....message in both the SIs is the Proxy structure
    2) 1 ABS Sync SI for BPM <---> SOAP ...... 1 IN Sync SI at the SOAP side
    3) 1 ABS Async SI for BPM----> Proxy.......1 IN Async SI at the SAP end....message will be the Proxy structure.
    You may need:
    1 OM for BPM <---> SOAP flow
    1 OM for BPM ---> Proxy....
    Have you opened one more thread with the same requirement??
    Regards,
    Abhishek.

  • 401 Error Proxy to SOAP

    Hi,
    We have sync interface for Proxy to SOAP. This interface works fine when run once.
    When we did volume testing, 10% of the messages ( randomly) failed  with 401 Unauthorized & 503 Service not aviabale.
    After researching we found a note 821026 which talks about the issue. We have done changes as per the note & inclease the connection Pool max to 100.
    Please advice, if there is anything we can do as it is still failing with 401 & 503 in PI.
    Regards

    Hi All,
    Thanks for reply. We have 3 PI Systems which calls the same Web service via SOAP (  Syn proxy-SOAP.
    First we observed this error in one of the system & now it comes in all. The error is
    com.sap.engine.interfaces.messaging.api.exception.MessagingException: java.net.SocketTimeoutException: Read timed out
    The sequence of event is  Inbound message from ECC looks good, the Mapping is OK. I see in response  the red & the error is in Inbound of Response.
    Below is the log in MDT
    02.02.2012 18:12:03 Information The message was successfully received by the messaging system. Protocol: XI URL: http://xxxxpd312.r1-core.r1.xxx.net:50000/MessagingSystem/receive/AFW/XI Credential (User): PIISUSER
    02.02.2012 18:12:03 Information Using connection SOAP_http://sap.com/xi/XI/System. Trying to put the message into the request queue.
    02.02.2012 18:12:03 Information Message successfully put into the queue.
    02.02.2012 18:12:03 Information The message was successfully retrieved from the request queue.
    02.02.2012 18:12:03 Information The message status was set to DLNG.
    02.02.2012 18:12:03 Information Delivering to channel: CC_SOAP_Rcvr_PaymentVerification
    02.02.2012 18:12:03 Information MP: entering1
    02.02.2012 18:12:03 Information MP: processing local module localejbs/sap.com/com.sap.aii.af.soapadapter/XISOAPAdapterBean
    02.02.2012 18:12:03 Information SOAP: request message entering the adapter with user J2EE_GUEST
    02.02.2012 18:12:18 Error SOAP: call failed: java.net.SocketTimeoutException: Read timed out
    SOAP: error occured: com.sap.engine.interfaces.messaging.api.exception.MessagingException: java.net.SocketTimeoutException: Read timed out
    02.02.2012 18:12:18 Error MP: exception caught with cause com.sap.engine.interfaces.messaging.api.exception.MessagingException: java.net.SocketTimeoutException: Read timed out
    02.02.2012 18:12:18 Error Adapter Framework caught exception: java.net.SocketTimeoutException: Read timed out
    02.02.2012 18:12:18 Error Delivering the message to the application using connection SOAP_http://sap.com/xi/XI/System failed, due to: com.sap.engine.interfaces.messaging.api.exception.MessagingException: java.net.SocketTimeoutException: Read timed out. Setting message to status failed.
    SXMB Log from ECC . This is shown
    <!--  Inbound Message
      -->
    - <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
      <SAP:Category>XIAdapterFramework</SAP:Category>
      <SAP:Code area="MESSAGE">GENERAL</SAP:Code>
      <SAP:P1 />
      <SAP:P2 />
      <SAP:P3 />
      <SAP:P4 />
      <SAP:AdditionalText>com.sap.engine.interfaces.messaging.api.exception.MessagingException: java.net.SocketTimeoutException: Read timed out</SAP:AdditionalText>
      <SAP:ApplicationFaultMessage namespace="" />
      <SAP:Stack />
      <SAP:Retry>M</SAP:Retry>
      </SAP:Error>
    I am not sure if this is issue in calling adapter engine( while sedning to web service) or When the Data is being send to Proxy this issue comes in.
    Ps: We have gone through many notes  & increase the connection pool & max wait time.
    Also we have increase the time out in SOAP adapter with no effect. BASIS is looking at SXMB_ADM Http paramterto increase but this was systems were working fine before that.
    Now even one message is not flowing.
    Thanks & please advice
    I

  • Error "soap fault: No operation available for request" in proxy to soap Scenario

    Hi Experts,
    Unable to trace the below error when pushing the message from RWB while testing the PROXY to SOAP interface
      Delivering the message to the application using connection SOAP_http://sap.com/xi/XI/System failed, due to: com.sap.engine.interfaces.messaging.api.exception.MessagingException: SOAP: response message contains an error XIAdapter/PARSING/ADAPTER.SOAP_EXCEPTION - soap fault: No operation available for request {http://schemas.xmlsoap.org/soap/envelope/}Envelope.
    Thank you very much if any one provided the solution
    Regards,
    Yugandhar 

    Hi Yugandhar,
    Check the below thread,
    Connecting from SAP PI To Salesforce
    Regards
    RK N.

  • Acknowledgement for AsynThird-party-- SOAP-- PI-- ABAP proxy-- ECC scenario

    Can someone please provide me a step-by-step for Third-party>SOAP>PI>ABAP proxy>ECC scenario.
    Third-part system is sending an Asynchronous HTTPS message to PI which is then routed to the ECC system to do some processing. I have read many blong and all SAP Docu available on this subject, but i am still confused.
    I understand that ABAP Proxies supports acknowledgement, but what needs to be done in the third-party system to be able to receive acknowledgements. Is there any special config. that needs to be done in Sender SOAP adapter?
    What diff. needs to be done in ABAP proxy to be able to send acknowledgement messages, any config. in XI receiver adapter?
    I will appreciate any guidance.
    Thanks,
    Saurabh

    HI
    Third party application need to have the synchronus communication enabled. If not then you need to get a wrapper develop for this kind of communication
    For proxy development
    Just go through these links:
    How to create proxy.
    http://help.sap.com/saphelp_nw04/helpdata/en/14/555f3c482a7331e10000000a114084/frameset.htm
    ABAP Server Proxies (Inbound Proxy)
    /people/siva.maranani/blog/2005/04/03/abap-server-proxies
    OutBound Proxy (Client Proxy)
    /people/sravya.talanki2/blog/2006/07/28/smarter-approach-for-coding-abap-proxies
    Outbound Proxy (Client Proxy)
    /people/ravikumar.allampallam/blog/2005/03/14/abap-proxies-in-xiclient-proxy
    How to Activate Proxy.
    /people/vijaya.kumari2/blog/2006/01/26/how-do-you-activate-abap-proxies
    File to R/3 via ABAP Proxy with good example
    /people/prateek.shah/blog/2005/06/14/file-to-r3-via-abap-proxy
    http://help.sap.com/saphelp_nw2004s/helpdata/en/48/d5a1fe5f317a4e8e35801ed2c88246/frameset.htm
    Synchronous Proxies:
    Outbound Synchronous Proxy
    https://www.sdn.sap.com/irj/sdn/wiki?path=/display/profile/abap%2bproxy%2boutbound%2bprogram%2b-%2bpurchase%2border%2bsend
    Inbound Synchronous Proxy
    https://www.sdn.sap.com/irj/sdn/wiki?path=/display/profile/abap%2bproxy%2binbound%2bprogram%2b-%2bsales%2border%2bcreation

  • OWSM Policy Binding Disabled for proxy/business server with SOAP 1.1

    Hi,
    I am using 11pPS2.
    In osb, i created a proxy service with soap 1.1. and business proxy with soap 1.1
    Now I click Policies tab of each service,
    In Service Policy Configuration,
    OWSM Policy Bindings is disabled to choose.
    So I can't attach any OWSM policy to osb service.
    Only Custom Policy bidings are enabled.
    appreciate any help and comments on this issue

    Need check if you Extend your Oracle Service Bus domain with Oracle Web Services Manager and Oracle Enterprise Manager.
    Select the following domain templates when running the Oracle Fusion Middleware Configuration Wizard
    Oracle Service Bus OWSM Extension
    Oracle WSM Policy Manager (automatically selected when you select the OWSM Extension)
    Oracle Enterprise Manager (optional, needed for creating and managing Oracle Web Services Manager policies)

  • Error in SOAP receiver channel in Synchronous Proxy to SOAP scenario

    Hi all,
    We are experiencing an issue with a synchronous Proxy to SOAP scenario. Getting below error message in the SOAP receiver communication channel for the response message.
    SOAP: Response message contains an errorXIAdapter/HTTP/ADAPTER.HTTP_EXCEPTION - HTTP 500 Internal Server Error
    Returning to application. Exception: com.sap.engine.interfaces.messaging.api.exception.MessagingException: Error encountered while executing mapping: com.sap.aii.af.service.mapping.MappingException: com.sap.aii.utilxi.misc.api.ResourceException: Could not determine mapping steps for message 1364b76e-ecbf-11e4-85f4-000023acfde6.
    We are running PI 7.4.
    Any help is appreciated.
    Thanks,
    Pushpa

    Hi,
    Seems the Receiver Webservice is not reachable. Did you try to test it using SOAP UI tool.
    1. Test a fresh message from local SOAP UI tool.
    2. Pick 3rd party WSDL file and Import in SOAP UI tool.
    3. Put some dummy data for mandatory fields
    4. Trigger it msg and ckh if you get successful / response msg.
    5. Check if firewall is open and that URL is not blocked.
    Hope it helps
    Regards,
    Azhar

  • PROXY to SOAP ; HTTP403 error in PI 7.1

    Hi team,
    it was proxy to HTTP scenario. Receiver : webportal . We have chnged it to Proxy to SOAP ,due to HTTP does not support multi message generation . I have checked Do NOT USE SOAP Envelope in SOAP rcv channel. Pls find the config details.
    Adapter Type: SOAP
    Trans.protocal: HTTP
    Mess.Protocal: SOAP1.1
    Do not use SOAP envelope : Checked
    Now Im getting error in RWB .
    "Message processing failed. Cause: com.sap.engine.interfaces.messaging.api.exception.MessagingException: SOAP: response message contains an error XIAdapter/HTTP/ADAPTER.HTTP_EXCEPTION - HTTP 403 Access denied"
    I checked with the basis people- they confirmed - some request hitting the site. but unable to read the content . they specified HTTP header should contain the content type : text/xml . If I checked "Do not use SOAP envelope " , I guess the content type is application/xml etc.
    so how can I change the HTTP content type to text/xml. OR any other reason tfor this error.
    thnaks
    Drumi.

    Hello,
    I checked with the basis people- they confirmed - some request hitting the site. but unable to read the content . they specified HTTP header should contain the content type : text/xml . If I checked "Do not use SOAP envelope " , I guess the content type is application/xml etc.
    so how can I change the HTTP content type to text/xml. OR any other reason tfor this error.
    The content type when Do Not Use SOAP Envelope is checked defaults to application/xml. To change it to the correct content type, use the MessageTransformBean for your requirement.
    ProcessingSequence                         ModuleName           Type     ModuleKey
    1          localejbs/AF_Modules/MessageTransformBean            LEB      0
    2          sap.com/com.sap.aii.af.soapadapter/XISOAPAdapterBean LEB      soap
    Module Configuration
    ModuleKey                ParameterName                ParameterValue
    0                      Transform.ContentType          text/xml
    For more info, see http://help.sap.com/saphelp_nwpi711/helpdata/en/57/0b2c4142aef623e10000000a155106/frameset.htm
    Check also if you are passing credentials in your Receiver.
    Hope this helps
    Mark

  • Error in Proxy to SOAP synchronous scenario

    Hi Gurus,
    Hope you are doing well. I have a Proxy to SOAP synchronous interface interacting with an external system (system outside the firewall/landscape of my company).
    When I am trying to post the request message from XI, I am getting the following error.
    MP: Exception caught with cause com.sap.aii.af.ra.ms.api.RecoverableException: SOAP: response message contains an error XIAdapter/PARSING/ADAPTER.SOAP_EXCEPTION - soap fault: The server was unable to process the request due to an internal error.  For more information about the error, either turn on IncludeExceptionDetailInFaults (either from ServiceBehaviorAttribute or from the <serviceDebug> configuration behavior) on the server in order to send the exception information back to the client, or turn on tracing as per the Microsoft .NET Framework 3.0 SDK documentation and inspect the server trace logs
    In the WSDL provided by the external application, i.e. receiver WSDL, there is no attribute/field with the name 'IncludeExceptionDetailInFaults' and there is no fault string defined.
    Where is this error being thrown up? Is it a network/firewall error that XI is unable to determine?
    Please provide an answer as soon as possible.
    regards
    Debansu

    Hi,
    i think it is the problem in the WSDL provider system, because it is throwing the Error with some string".NET",
    do the below steps for investigating the issue
    1)try pinging the URL provided in the WSDL from internet explorer.
    2)if it is successfull, try to push one message from SOAP UI to by importing that WSDL, if you get any error then it is problem in the end system.
    Thank You,
    Madhav

  • Abap proxy 2 soap

    Hi,
    this scenario is abap proxy 2 soap ,, , source system send some data to target webservice and target webservice return approval number.
    I checked target url and soap action in receiver soap adapter, and those value is correct.
    on sxmb_moni
    i got NO_MAPPINGPROGRAM_FOUND
    http://test.test.com/pt/ses001/approvalprocess SES001_IM does not exist in runtime cache</SAP:Stack>
    and Applicatoin Error
    <?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
    - <!--  Request Message Mapping
      -->
    - <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
      <SAP:Category>Application</SAP:Category>
      <SAP:Code area="UNKNOWN">APPLICATION_ERROR</SAP:Code>
      <SAP:P1 />
      <SAP:P2 />
      <SAP:P3 />
      <SAP:P4 />
      <SAP:AdditionalText>application fault</SAP:AdditionalText>
      <SAP:ApplicationFaultMessage namespace="http://xml.apache.org/axis/">hostname</SAP:ApplicationFaultMessage>
      <SAP:Stack />
      <SAP:Retry>M</SAP:Retry>
      </SAP:Error>
    here is Sent message log on MDT.
    2006-08-29 13:25:37 Error SOAP: response message contains an error Application/UNKNOWN/APPLICATION_ERROR - application fault
    2006-08-29 13:25:37 Success SOAP: response message leaving the adapter
    2006-08-29 13:25:37 Success Application attempting to send an XI message asynchronously using connection AFW.
    2006-08-29 13:25:37 Success Trying to put the message into the send queue.
    2006-08-29 13:25:37 Success The response message for message 44f23177-e6ed-0270-0000-000046028211(INBOUND) was successfully transmitted to the calling application.
    2006-08-29 13:25:37 Success The message status set to DLVD.
    2006-08-29 13:25:37 Success The application sent the message asynchronously using connection AFW. Returning to application.
    here is Receive message log on MDT.
    2006-08-29 13:25:37 Success The message was successfully received by the messaging system. Profile: XI URL: http://xi0034:50000/MessagingSystem/receive/AFW/XI
    2006-08-29 13:25:37 Success Using connection AFW. Trying to put the message into the request queue.
    2006-08-29 13:25:37 Success Message successfully put into the queue.
    2006-08-29 13:25:37 Success The message was successfully retrieved from the request queue.
    2006-08-29 13:25:37 Success The message status set to DLNG.
    2006-08-29 13:25:37 Success Delivering to channel: R_TEST_SOAP_SSS001
    2006-08-29 13:25:37 Success SOAP: request message entering the adapter
    2006-08-29 13:25:37 Success SOAP: completed the processing
    2006-08-29 13:25:37 Success SOAP: response message received 6bc3e4d0-3716-11db-a265-00145e483080
    2006-08-29 13:25:37 Error SOAP: response message contains an error Application/UNKNOWN/APPLICATION_ERROR - application fault
    i can see source data on sxmb_moni.
    <?xml version="1.0" encoding="utf-8" ?>
    - <nr1:APPROVALREQ_SES_MT xmlns:nr1="http://test.test.com/pt/ses001/approvalprocess">
      <TITLE>46</TITLE>
      <GUBUN />
      <REQUESTOR>46</REQUESTOR>
      <TEXTLINE>SAFSAFSAFDSAF</TEXTLINE>
      </nr1:APPROVALREQ_SES_MT>
    request message mapping of request
      <?xml version="1.0" encoding="UTF-8" ?>
    - <ns1:ApprovalRequest xmlns:ns1="http://70.2.207.241:8080/axis/ApprovalService.jws">
      <args1>46</args1>
      <args2>46</args2>
      </ns1:ApprovalRequest>
    I can not see any return value comming from target webservice on sxmb_moni.
    request message mapping error on response
    <?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
    - <!--  Request Message Mapping
      -->
    - <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
      <SAP:Category>Application</SAP:Category>
      <SAP:Code area="UNKNOWN">APPLICATION_ERROR</SAP:Code>
      <SAP:P1 />
      <SAP:P2 />
      <SAP:P3 />
      <SAP:P4 />
      <SAP:AdditionalText>application fault</SAP:AdditionalText>
      <SAP:ApplicationFaultMessage namespace="http://xml.apache.org/axis/">hostname</SAP:ApplicationFaultMessage>
      <SAP:Stack />
      <SAP:Retry>M</SAP:Retry>
      </SAP:Error>
    payload of request message mapping of response
    <?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
    - <!--  Request Message Mapping
      -->
      <ns2:hostname xmlns:ns2="http://xml.apache.org/axis/">ibmr52</ns2:hostname>
    please check what was my fault.
    thanks
    venjamin

    Hi Bhavesh.
    thanks for the note.,,
    please look at the bottom of this content.
    i can not see  "Method=Approval" between jws and args1 even though i set SOAP Action = Approval on Receiver SOAP Adapter.
    is this happening something wrong? or is it normal log?
    <?xml version="1.0" encoding="UTF-8"?>
    <ns1:ApprovalRequest xmlns:ns1="http://70.2.207.241:8080/axis/ApprovalService.jws"><args1>333</args1><args2>333</args2></ns1:ApprovalRequest>
    SAP_512dbe91-372d-11db-b291-00145e483080_END
    here is detail message log on MDT.
    --SAP_512dbe91-372d-11db-b291-00145e483080_END
    Content-ID: <[email protected]>
    Content-Disposition: attachment;filename="[email protected]"
    Content-Type: text/xml; charset=utf-8
    Content-Description: SOAP
    <SOAP:Envelope xmlns:SOAP='http://schemas.xmlsoap.org/soap/envelope/'><SOAP:Header>
    <sap:Main xmlns:sap='http://sap.com/xi/XI/Message/30' versionMajor='3' versionMinor='0' SOAP:mustUnderstand='1' xmlns:wsu='http://www.docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd' wsu:Id='wsuid-main-92ABE13F5C59AB7FE10000000A1551F7'>
    <sap:MessageClass>ApplicationMessage</sap:MessageClass>
    <sap:ProcessingMode>synchronous</sap:ProcessingMode>
    <sap:MessageId>44f23fa9-e6ed-0270-0000-000046028211</sap:MessageId>
    <sap:TimeSent>2006-08-29T07:10:08Z</sap:TimeSent><sap:Sender><sap:Party agency='' scheme=''></sap:Party>
    <sap:Service>BS_SAPR3_SSS0017</sap:Service></sap:Sender><sap:Receiver>
    <sap:Party agency='' scheme=''></sap:Party><sap:Service>BS_MMM_D</sap:Service></sap:Receiver>
    <sap:Interface namespace='http://sds.samsung.co.kr/pt/sessingle001/approvalprocess'>APPROVALREQ_MMM_IB</sap:Interface>
    </sap:Main><sap:ReliableMessaging xmlns:sap='http://sap.com/xi/XI/Message/30' SOAP:mustUnderstand='1'>
    <sap:QualityOfService>BestEffort</sap:QualityOfService></sap:ReliableMessaging>
    <sap:Diagnostic xmlns:sap='http://sap.com/xi/XI/Message/30' SOAP:mustUnderstand='1'>
    <sap:TraceLevel>Information</sap:TraceLevel><sap:Logging>Off</sap:Logging></sap:Diagnostic><sap:HopList xmlns:sap='http://sap.com/xi/XI/Message/30' SOAP:mustUnderstand='1'>
    <sap:Hop timeStamp='2006-08-29T07:10:08Z' wasRead='false'><sap:Engine type='BS'>BS_SAPR3_SSS0017</sap:Engine>
    <sap:Adapter namespace='http://sap.com/xi/XI/System'>XI</sap:Adapter><sap:MessageId>44f23fa9-e6ed-0270-0000-000046028211</sap:MessageId><sap:Info>3.0</sap:Info></sap:Hop>
    <sap:Hop timeStamp='2006-08-29T07:09:06Z' wasRead='false'>
    <sap:Engine type='IS'>is.00.xi0034</sap:Engine>
    <sap:Adapter namespace='http://sap.com/xi/XI/System'>XI</sap:Adapter>
    <sap:MessageId>44f23fa9-e6ed-0270-0000-000046028211</sap:MessageId><sap:Info>3.0</sap:Info></sap:Hop><sap:Hop timeStamp='2006-08-29T07:09:08Z' wasRead='false'>
    <sap:Engine type='AE'>af.sxd.xi0034</sap:Engine><sap:Adapter namespace='http://sap.com/xi/XI/System'>XIRA</sap:Adapter>
    <sap:MessageId>44f23fa9-e6ed-0270-0000-000046028211</sap:MessageId></sap:Hop></sap:HopList></SOAP:Header><SOAP:Body>
    <sap:Manifest xmlns:sap='http://sap.com/xi/XI/Message/30' xmlns:xlink='http://www.w3.org/1999/xlink' xmlns:wsu='http://www.docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd' wsu:Id='wsuid-manifest-5CABE13F5C59AB7FE10000000A1551F7'/></SOAP:Body></SOAP:Envelope>
    --SAP_512dbe91-372d-11db-b291-00145e483080_END
    content-id: [email protected]
    content-type: application/xml
    <?xml version="1.0" encoding="UTF-8"?>
    <ns1:ApprovalRequest xmlns:ns1="http://70.2.207.241:8080/axis/ApprovalService.jws"><args1>333</args1><args2>333</args2></ns1:ApprovalRequest>
    SAP_512dbe91-372d-11db-b291-00145e483080_END
    thanks
    venjamin
    Message was edited by: venjamin

  • Error in synchronous( abap proxy to soap)scenario

    Hi experts,
    My scenario is synchronous abap proxy to sysnchronous soap. for proxy I am using business system name as ERDCLNT220 and soap business system name as BS_HRS_DEV
    configuration steps are
    1. only client proxy to soap scenario I have done.
    communication channels: only receiver soap adapter. no proxy sender communication channel for client proxy.
    Already we have RFC destination connection and connection type H for proxy to xi.
    1.Is it required RFC destination connection for xi to server proxy.
    2.Is it required receiver proxy communication channel for server proxy?.
    i HAVE TESTED THIS INTERFACE. I am able to send the request. But I am not able to receive the response from soap webservice message .
    error is:
    SOAP: response message contains an error XIAdapter/PARSING/ADAPTER.SOAP_EXCEPTION - soap fault: Exception occurred while trying to invoke service method getPerson
    exception caught with cause com.sap.engine.interfaces.messaging.api.exception.MessagingException: SOAP: response message contains an error XIAdapter/PARSING/ADAPTER.SOAP_EXCEPTION - soap fault: Exception occurred while trying to invoke service method getPerson
    Error Adapter Framework caught exception: SOAP: response message contains an error XIAdapter/PARSING/ADAPTER.SOAP_EXCEPTION - soap fault: Exception occurred while trying to invoke service method getPerson
    Error Delivering the message to the application using connection SOAP_http://sap.com/xi/XI/System failed, due to: com.sap.engine.interfaces.messaging.api.exception.MessagingException: SOAP: response message contains an error XIAdapter/PARSING/ADAPTER.SOAP_EXCEPTION - soap fault: Exception occurred while trying to invoke service method getPerson. Setting message to status failed.
    Kindly help me.
    advance thanks
    thanks and regards
    elton
    Edited by: eltonsaranya on May 9, 2011 10:27 AM

    Your exception message shows problem at the webservice side.
    Check the following:
    a) you need two mappings one for proxy req to soap request and other soap response to proxy response
    b) You need to create service interfaces both sender and receiver synchronous .
    c) communication channel  QOS is best effort for both sender and receiver
    d) I dont see problem in soap configuration. Bcuz you are able to ping and while getting response from the method getPerson it fails.
    f) See your SOAP response structure matches with WSDL provided.
    g) You can also test outside PI.. I meant testing via soap client tool like SOAPUI  for that web service. So that you know whether problem exists on the target system or not.
    Hope that helps.

  • ABAP Client Proxy to SOAP

    Hi all,
    I am working on ABAP client proxy to SOAP Asynchronous scenario.  when iam sending the data from r/3 system data sent to webservice.
    but PI sending this same data  3 more to the third parth system.  when i checked in runtime workbench it is showing number of retrys 3
    how to resolve this issue.  please explain in detail
    Thanks
    Anil

    Anil,
    That's the default setting for Async SOAP communication...this can occur if the receiver is overloaded and cannot take any more feed and sometimes time out in the middle of the hand off...this would lead to re-try in PI...so you would see 3 entries of same data...refresh or clear the data from the receiver could solve the issue...
    Thanks,
    Srini
    Edited by: Srinivas Davuluri on Sep 9, 2010 1:51 PM

  • Problem Proxy to SOAP Synchronous

    Hi Experts, I was looking for a solution to this problem, but I could not find the solution, I hope you can help me.
    I have the scenario PROXY ==> PI ==> SOAP (Synchronus).
    When the Web Service is ok, I have no problems, my problem is with the Fault Exception, because I tested it in SoapUI, and I'm getting this message.
    <S:Envelope xmlns:S="http://schemas.xmlsoap.org/soap/envelope/">
       <S:Body>
          <S:Fault xmlns:ns4="http://www.w3.org/2003/05/soap-envelope">
             <faultcode>S:Server</faultcode>
             <faultstring>Error al insertar Domicilio en servicio Empleado</faultstring>
             <detail>
                <FaultException:FaultException xsi:nil="true" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://www.interacciones.com.mx/ServicioEmpleado/" xmlns:FaultException="http://www.interacciones.com.mx/ServicioEmpleado/"/>
                <ns2:exception class="mx.com.interacciones.servicioEmpleado.FaultException_Exception" note="To disable this feature, set com.sun.xml.ws.fault.SOAPFaultBuilder.disableCaptureStackTrace system property to false" xmlns:ns2="http://jax-ws.dev.java.net/">
                   <message>Error al insertar Domicilio en servicio Empleado</message>
                   <ns2:stackTrace>
                      <ns2:frame class="mx.com.interacciones.servicioEmpleado.ServicioEmpleadoImpl" file="ServicioEmpleadoImpl.java" line="87" method="agregarEmpleado"/>
                      <ns2:frame class="sun.reflect.GeneratedMethodAccessor267" line="unknown" method="invoke"/>
                      <ns2:frame class="sun.reflect.DelegatingMethodAccessorImpl" file="DelegatingMethodAccessorImpl.java" line="25" method="invoke"/>
                      <ns2:frame class="java.lang.reflect.Method" file="Method.java" line="597" method="invoke"/>
                      <ns2:frame class="weblogic.wsee.jaxws.WLSInstanceResolver$WLSInvoker" file="WLSInstanceResolver.java" line="101" method="invoke"/>
                      <ns2:frame class="weblogic.wsee.jaxws.WLSInstanceResolver$WLSInvoker" file="WLSInstanceResolver.java" line="83" method="invoke"/>
                      <ns2:frame class="com.sun.xml.ws.server.InvokerTube$2" file="InvokerTube.java" line="152" method="invoke"/>
                      <ns2:frame class="com.sun.xml.ws.server.sei.EndpointMethodHandler" file="EndpointMethodHandler.java" line="264" method="invoke"/>
                      <ns2:frame class="com.sun.xml.ws.server.sei.SEIInvokerTube" file="SEIInvokerTube.java" line="93" method="processRequest"/>
                      <ns2:frame class="com.sun.xml.ws.api.pipe.Fiber" file="Fiber.java" line="604" method="__doRun"/>
                      <ns2:frame class="com.sun.xml.ws.api.pipe.Fiber" file="Fiber.java" line="563" method="_doRun"/>
                      <ns2:frame class="com.sun.xml.ws.api.pipe.Fiber" file="Fiber.java" line="548" method="doRun"/>
                      <ns2:frame class="com.sun.xml.ws.api.pipe.Fiber" file="Fiber.java" line="445" method="runSync"/>
                      <ns2:frame class="com.sun.xml.ws.server.WSEndpointImpl$2" file="WSEndpointImpl.java" line="275" method="process"/>
                      <ns2:frame class="com.sun.xml.ws.transport.http.HttpAdapter$HttpToolkit" file="HttpAdapter.java" line="454" method="handle"/>
                      <ns2:frame class="com.sun.xml.ws.transport.http.HttpAdapter" file="HttpAdapter.java" line="250" method="handle"/>
                      <ns2:frame class="com.sun.xml.ws.transport.http.servlet.ServletAdapter" file="ServletAdapter.java" line="140" method="handle"/>
                      <ns2:frame class="weblogic.wsee.jaxws.HttpServletAdapter$AuthorizedInvoke" file="HttpServletAdapter.java" line="319" method="run"/>
                      <ns2:frame class="weblogic.wsee.jaxws.HttpServletAdapter" file="HttpServletAdapter.java" line="232" method="post"/>
                      <ns2:frame class="weblogic.wsee.jaxws.JAXWSServlet" file="JAXWSServlet.java" line="310" method="doPost"/>
                      <ns2:frame class="javax.servlet.http.HttpServlet" file="HttpServlet.java" line="727" method="service"/>
                      <ns2:frame class="weblogic.wsee.jaxws.JAXWSServlet" file="JAXWSServlet.java" line="87" method="service"/>
                      <ns2:frame class="javax.servlet.http.HttpServlet" file="HttpServlet.java" line="820" method="service"/>
                      <ns2:frame class="weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction" file="StubSecurityHelper.java" line="227" method="run"/>
                      <ns2:frame class="weblogic.servlet.internal.StubSecurityHelper" file="StubSecurityHelper.java" line="125" method="invokeServlet"/>
                      <ns2:frame class="weblogic.servlet.internal.ServletStubImpl" file="ServletStubImpl.java" line="292" method="execute"/>
                      <ns2:frame class="weblogic.servlet.internal.ServletStubImpl" file="ServletStubImpl.java" line="175" method="execute"/>
                      <ns2:frame class="weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction" file="WebAppServletContext.java" line="3594" method="run"/>
                      <ns2:frame class="weblogic.security.acl.internal.AuthenticatedSubject" file="AuthenticatedSubject.java" line="321" method="doAs"/>
                      <ns2:frame class="weblogic.security.service.SecurityManager" file="SecurityManager.java" line="121" method="runAs"/>
                      <ns2:frame class="weblogic.servlet.internal.WebAppServletContext" file="WebAppServletContext.java" line="2202" method="securedExecute"/>
                      <ns2:frame class="weblogic.servlet.internal.WebAppServletContext" file="WebAppServletContext.java" line="2108" method="execute"/>
                      <ns2:frame class="weblogic.servlet.internal.ServletRequestImpl" file="ServletRequestImpl.java" line="1432" method="run"/>
                      <ns2:frame class="weblogic.work.ExecuteThread" file="ExecuteThread.java" line="201" method="execute"/>
                      <ns2:frame class="weblogic.work.ExecuteThread" file="ExecuteThread.java" line="173" method="run"/>
                   </ns2:stackTrace>
                </ns2:exception>
             </detail>
          </S:Fault>
       </S:Body>
    </S:Envelope>
    So, I was reading a lot of threads, those said to copy the structure, but it doest not work.
    I tried to check the "Do Not Use SOAP Envolve", but when I did that I got this error.
    Message processing failed. Cause: com.sap.engine.interfaces.messaging.api.exception.MessagingException: SOAP: response message contains an error XIAdapter/HTTP/ADAPTER.HTTP_EXCEPTION - HTTP 415 Unsupported Media Type
    When I unchecked I got this error.
    <?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
    - <!--  Request Message Mapping
      -->
    - <SAP:Error SOAP:mustUnderstand="1" xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
      <SAP:Category>Application</SAP:Category>
      <SAP:Code area="MAPPING">EXCEPTION_DURING_EXECUTE</SAP:Code>
      <SAP:P1>com/sap/xi/tf/_MM_RecursosHumanos_ServicioEmplead~</SAP:P1>
      <SAP:P2>com.sap.aii.mappingtool.tf7.IllegalInstanceExcepti</SAP:P2>
      <SAP:P3>on: Cannot create target element /ns0:Fault. Value</SAP:P3>
      <SAP:P4>s missing in queue context. Target XSD requires a~</SAP:P4>
      <SAP:AdditionalText />
      <SAP:Stack>Runtime exception occurred during application mapping com/sap/xi/tf/_MM_RecursosHumanos_ServicioEmplead~; com.sap.aii.mappingtool.tf7.IllegalInstanceException: Cannot create target element /ns0:Fault. Values missing in queue context. Target XSD requires a~</SAP:Stack>
      <SAP:Retry>N</SAP:Retry>
      </SAP:Error>
    I could never see the Fault Structure in PI and neither in Web Service Navigator.
    Please, I need some help.
    Thank you very much.
    Regards

    If I test it in Soap UI I get the Fault, and in WsNavigator I can see the FaultCode and FaultString as a message on the top of the page.
    I do not know what more to do.
    <S:Envelope xmlns:S="http://schemas.xmlsoap.org/soap/envelope/">
       <S:Body>
          <S:Fault xmlns:ns4="http://www.w3.org/2003/05/soap-envelope">
             <faultcode>S:Server</faultcode>
             <faultstring>Error al insertar Domicilio en servicio Empleado</faultstring>
             <detail>
                <FaultException:FaultException xsi:nil="true" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://www.interacciones.com.mx/ServicioEmpleado/" xmlns:FaultException="http://www.interacciones.com.mx/ServicioEmpleado/"/>
                <ns2:exception class="mx.com.interacciones.servicioEmpleado.FaultException_Exception" note="To disable this feature, set com.sun.xml.ws.fault.SOAPFaultBuilder.disableCaptureStackTrace system property to false" xmlns:ns2="http://jax-ws.dev.java.net/">
                   <message>Error al insertar Domicilio en servicio Empleado</message>
                   <ns2:stackTrace>
                      <ns2:frame class="mx.com.interacciones.servicioEmpleado.ServicioEmpleadoImpl" file="ServicioEmpleadoImpl.java" line="87" method="agregarEmpleado"/>
                      <ns2:frame class="sun.reflect.NativeMethodAccessorImpl" file="NativeMethodAccessorImpl.java" line="native" method="invoke0"/>
                      <ns2:frame class="sun.reflect.NativeMethodAccessorImpl" file="NativeMethodAccessorImpl.java" line="39" method="invoke"/>
                      <ns2:frame class="sun.reflect.DelegatingMethodAccessorImpl" file="DelegatingMethodAccessorImpl.java" line="25" method="invoke"/>
                      <ns2:frame class="java.lang.reflect.Method" file="Method.java" line="597" method="invoke"/>
                      <ns2:frame class="weblogic.wsee.jaxws.WLSInstanceResolver$WLSInvoker" file="WLSInstanceResolver.java" line="101" method="invoke"/>
                      <ns2:frame class="weblogic.wsee.jaxws.WLSInstanceResolver$WLSInvoker" file="WLSInstanceResolver.java" line="83" method="invoke"/>
                      <ns2:frame class="com.sun.xml.ws.server.InvokerTube$2" file="InvokerTube.java" line="152" method="invoke"/>
                      <ns2:frame class="com.sun.xml.ws.server.sei.EndpointMethodHandler" file="EndpointMethodHandler.java" line="264" method="invoke"/>
                      <ns2:frame class="com.sun.xml.ws.server.sei.SEIInvokerTube" file="SEIInvokerTube.java" line="93" method="processRequest"/>
                      <ns2:frame class="com.sun.xml.ws.api.pipe.Fiber" file="Fiber.java" line="604" method="__doRun"/>
                      <ns2:frame class="com.sun.xml.ws.api.pipe.Fiber" file="Fiber.java" line="563" method="_doRun"/>
                      <ns2:frame class="com.sun.xml.ws.api.pipe.Fiber" file="Fiber.java" line="548" method="doRun"/>
                      <ns2:frame class="com.sun.xml.ws.api.pipe.Fiber" file="Fiber.java" line="445" method="runSync"/>
                      <ns2:frame class="com.sun.xml.ws.server.WSEndpointImpl$2" file="WSEndpointImpl.java" line="275" method="process"/>
                      <ns2:frame class="com.sun.xml.ws.transport.http.HttpAdapter$HttpToolkit" file="HttpAdapter.java" line="454" method="handle"/>
                      <ns2:frame class="com.sun.xml.ws.transport.http.HttpAdapter" file="HttpAdapter.java" line="250" method="handle"/>
                      <ns2:frame class="com.sun.xml.ws.transport.http.servlet.ServletAdapter" file="ServletAdapter.java" line="140" method="handle"/>
                      <ns2:frame class="weblogic.wsee.jaxws.HttpServletAdapter$AuthorizedInvoke" file="HttpServletAdapter.java" line="319" method="run"/>
                      <ns2:frame class="weblogic.wsee.jaxws.HttpServletAdapter" file="HttpServletAdapter.java" line="232" method="post"/>
                      <ns2:frame class="weblogic.wsee.jaxws.JAXWSServlet" file="JAXWSServlet.java" line="310" method="doPost"/>
                      <ns2:frame class="javax.servlet.http.HttpServlet" file="HttpServlet.java" line="727" method="service"/>
                      <ns2:frame class="weblogic.wsee.jaxws.JAXWSServlet" file="JAXWSServlet.java" line="87" method="service"/>
                      <ns2:frame class="javax.servlet.http.HttpServlet" file="HttpServlet.java" line="820" method="service"/>
                      <ns2:frame class="weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction" file="StubSecurityHelper.java" line="227" method="run"/>
                      <ns2:frame class="weblogic.servlet.internal.StubSecurityHelper" file="StubSecurityHelper.java" line="125" method="invokeServlet"/>
                      <ns2:frame class="weblogic.servlet.internal.ServletStubImpl" file="ServletStubImpl.java" line="292" method="execute"/>
                      <ns2:frame class="weblogic.servlet.internal.ServletStubImpl" file="ServletStubImpl.java" line="175" method="execute"/>
                      <ns2:frame class="weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction" file="WebAppServletContext.java" line="3594" method="run"/>
                      <ns2:frame class="weblogic.security.acl.internal.AuthenticatedSubject" file="AuthenticatedSubject.java" line="321" method="doAs"/>
                      <ns2:frame class="weblogic.security.service.SecurityManager" file="SecurityManager.java" line="121" method="runAs"/>
                      <ns2:frame class="weblogic.servlet.internal.WebAppServletContext" file="WebAppServletContext.java" line="2202" method="securedExecute"/>
                      <ns2:frame class="weblogic.servlet.internal.WebAppServletContext" file="WebAppServletContext.java" line="2108" method="execute"/>
                      <ns2:frame class="weblogic.servlet.internal.ServletRequestImpl" file="ServletRequestImpl.java" line="1432" method="run"/>
                      <ns2:frame class="weblogic.work.ExecuteThread" file="ExecuteThread.java" line="201" method="execute"/>
                      <ns2:frame class="weblogic.work.ExecuteThread" file="ExecuteThread.java" line="173" method="run"/>
                   </ns2:stackTrace>
                </ns2:exception>
             </detail>
          </S:Fault>
       </S:Body>
    </S:Envelope>

  • Proxy to SOAP scenario-With Attachment and Mapping

    I have a scenario to be developed, it is a Proxy to SOAP sceanrio.
    There are about 8 fields coming from Proxy.
    Can we create an attachment from these fields.
    Also we have to do a mapping of this attachment to a field in the target External Defination and also 2 fields of the 8 have to mapped to the other respective fields of the external defination.
    All this has to be posted on a webservice through SOAP with
    the 2 fields in payload and
    the attachment in the attachemnt section of the message
    Could this be achieved?

    In ABAP proxy you create a message with the two fields which you need for main SOAP message.
    The attachment is created exactly how it is requested from web service.
    You create a String with the XML (including tags) and do a codepage conversion to UTF-8 (or whatever is requested)
    Note: The payload is created in UTF-8 automatically, the attachment is treated as binary.
    You can also use a Java mapping for creating the attachment, if you have good Java skills, but I recommend to use program code for one purpose only on one place.

Maybe you are looking for