Exception using fault message in java server proxy.

Hi All,
I am trying to use Fault message inside my server proxy code in Asynchronous java server proxy. I am referring the below mentioned link :
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/d06315a6-e66e-2910-039c-ba8bbbd23702?quicklink=index&overridelayout=true
I successfully deployed my SDA file but while running the scenario(http-XI-ftp in PI7.11) i am getting the folowing exception under MDT:
com.sap.engine.interfaces.messaging.api.exception.MessagingException: Error processing inbound message. Exception: Cannot locate proxy bean ServerProxyFTTest3.
I am using the following library refernces under application-j2ee-engine.xml file:  com.sap.aii.af.sdk.lib, com.sap.aii.proxy.svc, com.sap.xi.util.misc,com.sap.guid,com.sap.exception all of type "weak".
I have checked almost all the forums related to fault messages in asynchronous java server proxy but couldn't find much help.
Request you all to help me.
Thanks
Amit

Hi Rajesh,
I am deploying my SDA file on Non Central Adapter Engine.
I have also registered my interface using:
http://ISVSAPPISB:51000/ProxyServer/register?ns=http://infosys.com/poc&interface=SI_Proxy_IA&bean=localejbs/ServerProxyFTTest3&method=sIProxyIA
But still i ma getting the same exception.
Hi Gabriel,
I implemented my scenario using the same. But in addittion to the librarry referneces mentioned over there i have added one more refrence in it "com.sap.exception"  of type "weak". My structure is like this:
<?xml version="1.0" encoding="UTF-8"?>
<application-j2ee-engine xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="application-j2ee-engine.xsd">
<reference reference-type="weak">
  <reference-target provider-name="sap.com" target-type="library">com.sap.aii.af.sdk.lib</reference-target>
  </reference>
<reference reference-type="weak">
  <reference-target provider-name="sap.com" target-type="service"> com.sap.aii.proxy.svc</reference-target>
  </reference>
<reference reference-type="weak">
  <reference-target provider-name="sap.com" target-type="library">com.sap.xi.util.misc</reference-target>
  </reference>
<reference reference-type="weak">
  <reference-target provider-name="sap.com" target-type="library">com.sap.guid</reference-target>
  </reference>
    <reference reference-type="weak">
  <reference-target provider-name="sap.com" target-type="library">com.sap.exception</reference-target>
  </reference>
    </application-j2ee-engine>
Please help.
Thanks
Amit

Similar Messages

  • Propagate fault message from ABAP server proxy to XI

    Hello
    My scenario is asynch HTTP -> async ABAP server proxy.
    I have searched a forum but I didn't find the ansver on my question:
    Is it possible to propagate a fault message from SAP system to XI in case of asyncronous ABAP Proxy in order to see in SXMB_MONI of XI?
    I see errors only on SAP side but this solution doesn't satisfied me I want to see all errors in one place.

    Hi,
    Have u used commit work at the end of the code.
    Can you please tell me what all configuration u have done.
    U have referred the ABAP Proxy configuration:
    /people/vijaya.kumari2/blog/2006/01/26/how-do-you-activate-abap-proxies
    Refer the below log for Client Proxy -
    /people/ravikumar.allampallam/blog/2005/03/14/abap-proxies-in-xiclient-proxy
    Chirag

  • Error handling using fault message type in outbound synchronous ABAP proxy

    Hi,
    We've a scenario, outbound synchronous ABAP proxy to synchronous SOAP receiver. The requirement is to send multiple records in a single rquest and get response for all the records sent (in the same response message).
    Say if I send 10 records from ECC, I should get 10 records as response from SOAP to ECC. But the problem here is, there could be some invalid requests, for which an invalid error status code should be sent as part of response.
    Source Structure
    Req_Proxy
        req (0..unbounded, string)
    Response Structure
    Resp_SOAP
      Resp (0..Unbounded)
           respString (0..1, String) (carries the actaul response message)
          status code (0..1, String) (carries the status of the response, for ex, 001 (successful), 002 (error))
    And now we are planning to make use of Fault Message Type, to track the errors from SOAP (status code 002). But, we are not sure on how to track this for all the requested records. Is it possible to track the errors for all the requested records in a singe call using fault message type? For eg if 8 records are successful and 2 are invalid, then we should get 10 records in response 8 for valid and 2 for invalid accordingly.
    Please calrify.
    Thanks.
    Rohit

    For eg if 8 records are successful and 2 are invalid, then we should get 10 records in response 8
    for valid and 2 for invalid accordingly.
    Check if you can modify the WSDL structure to include an error node that would get populated incase of invalid entries....this would mean that you get the success and failure details in the single message....also at the proxy-end make the necessary change in your DT.....may be then you do not need to use the fault message...
    Regards,
    Abhishek.

  • Exception in Java Server proxy

    Hi,
    I created a synchronous Java Server Proxy , and when i tested it i got this error
    *Could not parse XMBMessage due to No SOAP Envelope but 1 MT_ProxyInput*
    What could i be doing wrong?
    <?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="PLAINHTTP_ADAPTER">ATTRIBUTE_SERVER</SAP:Code>
      <SAP:P1>500</SAP:P1>
      <SAP:P2>Internal Server Error</SAP:P2>
      <SAP:P3>com.sap.aii.af.ra.ms.api.DeliveryException: Could not create Message from TransportMessage. Reason: com.sap.aii.af.ra.ms.api.MessagingException: com.sap.aii.af.ra.ms.api.MessagingException: Could not parse XMBMessage due to No SOAP Envelope but 1 MT_ProxyInput</SAP:P3>
      <SAP:P4 />
      <SAP:AdditionalText />
      <SAP:ApplicationFaultMessage namespace="" />
      <SAP:Stack>HTTP server code 500 reason Internal Server Error explanation com.sap.aii.af.ra.ms.api.DeliveryException: Could not create Message from TransportMessage. Reason: com.sap.aii.af.ra.ms.api.MessagingException: com.sap.aii.af.ra.ms.api.MessagingException: Could not parse XMBMessage due to No SOAP Envelope but 1 {http://</SAP:Stack>
      <SAP:Retry>N</SAP:Retry>
      </SAP:Error>

    I chose HTTP instead of Xi adapter type

  • SOAP Adapter - Using Fault Message

    Hi all,
    I have developed a Synchronous Integration Scenario which receives a SOAP request to the SOAP adapter, calls an ABAP proxy in SAP ECC to post some information and return a response or a fault to the sender.
    This all works fine, I am using a fault message in the ABAP proxy to record errors and return them to the SOAP adapter using the fault mapping. Again this all works fine. However when an application error is identified and a fault message returned to thre SOAP adapter, I had expected that the error details in the fault message to be packaged up in a standard SOAP fault and returned to the sender. Instead the fault message details are sent as the payload in the SOAP body of the response.
    Can anyone provide information on if it is possible to return the fault message as a standard SOAP fault instead of in the SOAP body of the response.
    Thanks
    Gary

    Dont think this is possible in standard.
    As an alternate, maybe you can select option Do not use SOAP Enevlope int he sender SOAP Adapter and thereby the entire SOAP Message will enter the mapping and you would need to use a XSL or Java  mapping to strip the SOAP Envlope in the mapping for the request and like wise in the response mapping you would need to add the SOAP Enevlope to the response.
    For the fault message mapping you need not add the SOAP Envelope.
    Not a standard solution, but can be tried if the requirement is really worth it. Otherwise I think the Fault Message will continue to be sent as the payload in the the SOAP Enevlope as this is how the SOAP adapter works.
    Regards
    Bhavesh

  • Fault message in asynchronous ABAP Proxy

    Hi,
    I have a question about fault messages in asynchronous ABAP proxy server.
    The configured scenario is SOAP – XI – ABAP Proxy. Between XI and the ABAP Proxy I have configured an inbound asynchronous interface with a fault message, and then I have generated all the classes and implemented some code for exception handling in the ABAP Proxy side successfully.
    When I tested negative cases, the exception raises and it is visible in the SXMB_MONI transaction in the R/3 side, but this exception is not displayed in the SXMB_MONI of XI it just displays a successful delivery to the ABAP Proxy message.
    According the XI documentation it says “<i>In the asynchronous case, you can see a fault message in the monitoring of the Exchange Infrastructure.</i>” But this is not working.
    Am I missing something?

    Hi,
    This parameters are form group RUNTIME.
    Please check it:
    http://help.sap.com/saphelp_nw04/helpdata/en/d6/49543b1e49bc1fe10000000a114084/content.htm
    Regards,
    Wojciech

  • What to in SLD (Business and Technical sys)for Java server Proxy?

    I am using java server proxy for communicating with XI.
    I have HTTP as sender comm channel and XI as Receiver comm channel and this is the error i got in SXMB_MONI.
    What to give in SLD for java Server proxy, i have given Web as Java.....is this what the error says.Help is highly appreciated.
    <?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="">
      <SAP:Category>Application</SAP:Category>
      <SAP:Code area="MAPPING">EXCEPTION_DURING_EXECUTE</SAP:Code>
      <SAP:P1>com/sap/xi/tf/_Folder_MM_</SAP:P1>
      <SAP:P2>com.sap.aii.utilxi.misc.api.BaseRuntimeException</SAP:P2>
      <SAP:P3>Fatal Error: com.sap.engine.lib.xml.parser.Parser~</SAP:P3>
      <SAP:P4 />
      <SAP:AdditionalText />
      <SAP:ApplicationFaultMessage namespace="" />
      <SAP:Stack>Während des Anwendungs-Mappings com/sap/xi/tf/_Folder_MM_ wurde eine com.sap.aii.utilxi.misc.api.BaseRuntimeException geworfen: Fatal Error: com.sap.engine.lib.xml.parser.Parser~.</SAP:Stack>
      <SAP:Retry>M</SAP:Retry>
      </SAP:Error>
    =====================
    Thanks

    Hi,
    Refer this configuration guide:
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/ac6de690-0201-0010-54ac-8923089dcc97
    Refer these too:
    Java Proxy Inside Story Part I
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/a068cf2f-0401-0010-2aa9-f5ae4b2096f9
    Java Proxy Inside Story Part II
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/f272165e-0401-0010-b4a1-e7eb8903501d
    Regards
    suraj
    Message was edited by: S.R.Suraj
    Message was edited by: S.R.Suraj

  • Java Server Proxy---Deployment error?

    I am trying the scenario from this blog
    /people/rashmi.ramalingam2/blog/2005/06/25/an-illustration-of-java-server-proxy
    I am getting deployment error
    May 30, 2006 1:39:34 PM /userOut/deploy (com.sap.ide.eclipse.sdm.threading.DeployThreadManager) [Thread[Deploy Thread,5,main]] ERROR:
    [003]Deployment aborted
    Settings
    SDM host : sapep
    SDM port : 50018
    URL to deploy : file:/C:/DOCUME1/ADMINI1/LOCALS~1/Temp/temp57679JPS_EAR.ear
    Deployment exception : Server sapep did not accept login request as apiadmin on port 50018 - CmdXmlFactory could not find Top Element within String: "null".
    Inner exception was :
    Server sapep did not accept login request as apiadmin on port 50018 - CmdXmlFactory could not find Top Element within String: "null".
    Help me
    Thanks

    Hi Saru,
    It seems u dont have the correct sdm password or someone has changed the sdm password.It has not accepted the credentials u have given during deployment.
    Check with all Sap enterprise portal settings in the prefernces/NWDS
    The host name,alias,port
    If not done with
    Try to change the sdm password using this Password trouble in SDM
    restart server again after changes
    even try
    - Stop nd restart the sdm from yor NWDS and deploy once again
    Thanks,
    Swathi
    Do offer pts:-)

  • Error in Java Server Proxy 7.1

    Hi,
    i am working on Java Server Proxy in PI 7.1, i am able to deploy EAR file successfully.
    when i am execting the scenario i am getting the following error
    JPR could not process the message. Reason: No remote bean found for reference of class $Proxy2917.
    can any one help me to resolve this issue.
    if there is any Blog or documentation on Java proxy PI 7.1, can you please share with me.
    Thank You,
    Madhav

    Hi Madhav,
       i think you are facing error because you not defined you bean class peopely,and check the configuration of J2EE-engine.xml file .
    refer the link
    http://help.sap.com/saphelp_nwpi71/helpdata/EN/ce/81a797cc9642c8bbef249bfd84dd45/content.htm
    Regards,
    Raj

  • Error code 403  in Java Server Proxy

    Hi All,
    I developed Java Server Proxy.
    1. I get the Generated files from IR.
    2. Implement those files in J2EE Application.
    3. Configure all .xml configuration files.
    4. Deploy the .ear file.
    5. Register the Bean in JPR registry.
    finally i put the file in source side then the file picked successfully.
    I checked in Message Monitor i got success message but I Checked in SXMB_MONI then i got the following error .
    ERROR:
      <?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="">
      <SAP:Category>XIServer</SAP:Category>
      <SAP:Code area="INTERNAL">HTTP_RESP_STATUS_CODE_NOT_OK</SAP:Code>
      <SAP:P1>403</SAP:P1>
      <SAP:P2>Forbidden</SAP:P2>
      <SAP:P3 />
      <SAP:P4 />
      <SAP:AdditionalText><!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> <html> <head> <title>Error Report</title> <style> td {font-family : Arial, Tahoma, Helvetica, sans-serif; font-size : 14px;} A:link A:visited A:active </style> </head> <body marginwidth="0" marginheight="0" leftmargin="0" topmargin="0" rightmargin="0"> <table width="100%" cellspacing="0" cellpadding="0" border="0" align="left" height="75"> <tr bgcolor="#FFFFFF"> <td align="left" colspan="2" height="48"><font face="Arial, Verdana, Helvetica" size="4" color="#666666"><b>  403 &nbsp Forbidden</b></font></td> </tr> <tr bgcolor="#3F73A3"> <td height="23" width="84"><img width=1 height=1 border=0 alt=""></td> <td height="23"><img width=1 height=1 border=0 alt=""></td> <td align="right" height="23"><font face="Arial, Verdana, Helvetica" size="2" color="#FFFFFF"><b>SAP J2EE Engine/7.00 </b></font></td> </tr> <tr bgcolor="#9DCDFD"> <td height="4" colspan="3"><img width=1 height=1 border=0 alt=""></td> </tr> </table> <br><br><br><br><br><br> <table width="100%" cellspacing="0" cellpadding="0" border="0" align="left" height="75"> <tr bgcolor="#FFFFFF"> <td align="left" colspan="2" height="48"><font face="Arial, Verdana, Helvetica" size="3" color="#000000"><b>  You are not authorized to view the requested resource.</b></font></td> </tr> <tr bgcolor="#FFFFFF"> <td align="left" valign="top" height="48"><font face="Arial, Verdana, Helvetica" size="2" color="#000000"><b>  Details:</b></font></td> <td align="left" valign="top" height="48"><font face="Arial, Verdana, Helvetica" size="3" color="#000000"><pre>  No details available</pre></font></td> </tr> </body> </html></SAP:AdditionalText>
      <SAP:ApplicationFaultMessage namespace="" />
      <SAP:Stack>HTTP response contains status code 403 with the description Forbidden Error while sending by HTTP (error code: 403, error text: Forbidden)</SAP:Stack>
      <SAP:Retry>M</SAP:Retry>
      </SAP:Error>
    Please give me the sloution.
    Thanks,
    Bharathiraja R

    Hi
    Look into this blog where you have solutions for all Errors.
    /people/krishna.moorthyp/blog/2006/07/23/http-errors-in-xi
    Error: HTTP 403 Forbidden
    Description: The server understood the request, but is refusing to fulfill it
    Possible Tips:
    Path sap/xi/engine not active
    • HTTP 403 during cache refresh of the adapter framework - Refer SAP Note -751856
    • Because of Inactive Services in ICF –Go to SICF transaction and activate the services. Refer SAP Note -517484
    • Error in RWB/Message Monitoring- because of J2EE roles – Refer SAP Note -796726
    • Error in SOAP Adapter - "403 Forbidden" from the adapter's servlet. –Because of the URL is incorrect or the adapter is not correctly deployed.
    Reward points if usefull..........

  • Java Server Proxy

    Hi all,
    I need to implement Java server proxy.
    Could you please suggest the possible scenarios that can be implemented.
    Thanks,
    Neha

    Hello Neha,
    How to create proxy.
    http://help.sap.com/saphelp_nw04/helpdata/en/14/555f3c482a7331e10000000a114084/frameset.htm
    How to Activate Proxy.
    /people/vijaya.kumari2/blog/2006/01/26/how-do-you-activate-abap-proxies
    Java Proxy
    /people/rashmi.ramalingam2/blog/2005/06/25/an-illustration-of-java-server-proxy
    /people/prasad.ulagappan2/blog/2005/06/27/asynchronous-inbound-java-proxy
    /people/siva.maranani/blog/2005/04/03/abap-server-proxies
    http://sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/a068cf2f-0401-0010-2aa9-f5ae4b2096f9
    https://sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/f272165e-0401-0010-b4a1-e7eb8903501d
    Thanks,
    Satya Kumar
    Reward points if it is useful to you..
    Edited by: SATYA KUMAR AKKARABOYANA on Apr 17, 2008 11:07 AM
    Edited by: SATYA KUMAR AKKARABOYANA on Apr 17, 2008 11:09 AM

  • Problem in registering the java server proxy interface...

    Hi All,
    I have created a java server proxy(in PI 7.1) using the below mentioned blog:
    /people/prasad.ulagappan2/blog/2005/06/27/asynchronous-inbound-java-proxy
    But the problem comes when i am trying to register the interface( on non central j2ee adapter engine) and ends up with getting unauthorization error even though i am having piappluser access. I am trying to register it using below mentioned URL:
    http://ISVSAPPISB:51000/ProxyServer/register?ns=xxxxx&interface=SI_Proxy_IA&bean=localejbs/sap.com/EARServerProxy/SIProxyIA_PortTypeBean&method= sIProxyIA
    xxxx-namespace
    So ,please anyone can tell me what authorization should i have in order register my server proxy interface.
    Thanks

    hi,
    >>>2) Plz tell me how to check whether my java server proxy interface got registered successfully or not.
    use listAll option form this page:
    http://help.sap.com/saphelp_nw04/helpdata/en/a4/d5b3b0b16843b3867c0245d9847ae5/content.htm
    Regards,
    Michal Krawczyk

  • Java Server Proxy Monitoring

    hi......All
    let me explain my scenario.Client java proxy connect to the JMS Server and receive the Messages and send through the XI and Java Server Proxy send that messages to the multiple Queues based on that message ROUTE ID.now the SXMB-Moni showing successful flag but how can we monitor the  java server proxy
    with warm regards,
    madhu

    hi
    ref this
    Re: Java Proxy Monitoring
    Java Server Proxy
    XI Configuration for Java Server Proxy

  • How to use fault message for error handling.

    HI
    Anybody has an idea about how we use fault messages to handle errors in XI
    Thanks
    Debraj

    Hi,
    Refer this link. This pdf file has descriptions about fault message types and how to use it.
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/4cdfc390-0201-0010-2197-da4ada09f281
    Regards,
    Uma

  • Execute Fault Message in Java Proxy

    Hello,
    I Call my Java Inbound Proxy and catch an exception.
    How can i send now a Faul Message back to XI ?
    } catch (Exception ex4) {
                   ExchangeFaultData_Type faultData = new ExchangeFaultData_Type();
                   faultData.setFaultText(ex4.getMessage());
                   ErrorReturn_Type errorReturn = new ErrorReturn_Type();
                   errorReturn.setStandard(faultData);
    What should i do ?
    Regards,
    Robin

    Hi Robin:
    Without knowing your complete code, I think what your are missing is "gluining" everything together, something like this:
    Somewhere in your code, define some variables:
          ExchangeFaultData_Type      faultData                   = null;
          FmJpAviso_Type              fmJpAviso_Type              = null;
          FmJpAviso_Message           fmJpAviso_Message           = null;
          FmJpAviso_Message_Exception fmJpAviso_Message_Exception = null;
          catch( HibernateException ehibernate )
           mensajeError = new StringBuffer();
           mensajeError.append(DataComercial.PED_XI_BDI_DMS_DC_001).append("\n\n")
                                .append(ehibernate.toString());
           catAPPL.fatalT(logger,mensajeError.toString());
              // Default Integration Scenario ExchangeFault Message
           faultData = new ExchangeFaultData_Type();
           faultData.setFaultText(mensajeError.toString());
               // My Fault Message Type for the inbound Message Interface
           fmJpAviso_Type = new FmJpAviso_Type();
           fmJpAviso_Type.setStandard(faultData);
               // My Fault Message
           fmJpAviso_Message = new FmJpAviso_Message();
           fmJpAviso_Message.setFmJpAviso(fmJpAviso_Type);
              // My Fault Message Exception
           fmJpAviso_Message_Exception = new FmJpAviso_Message_Exception();
           fmJpAviso_Message_Exception.setFmJpAviso_Message(fmJpAviso_Message);
           ehibernate = null;     
           mensajeError = null;           
              // Inform XI about this situation in the Java Proxy
           throw fmJpAviso_Message_Exception;
    Hope this helps,
    Regards, Pedro

Maybe you are looking for