Java Proxy Client Error

I write a EJB client to call the deployed java proxy, but I got the following exception, sounds like
authorization error, but I have already used the xiappluser to access.
Exception in thread "main" com.sap.aii.proxy.xiruntime.core.BaseProxyException:
Error sending MS message. Exception: Received HTTP response code 401.
at com.sap.aii.proxy.xiruntime.core.AbstractProxy.send$(AbstractProxy.ja
va:146)
Here is the my code:
Properties p = new Properties();
p.put(Context.INITIAL_CONTEXT_FACTORY,
"com.sap.engine.services.jndi.InitialContextFactoryImpl");
p.put(Context.PROVIDER_URL, "<sid>:50104");
p.put(Context.SECURITY_PRINCIPAL, "xiappluser");
p.put(Context.SECURITY_CREDENTIALS, "****");
Context ctx = new InitialContext(p);

Hi,
  We have the almost the same problem, we write a Java Application to call the deployed java proxy, but I got the following exception:
...com.sap.aii.proxy.xiruntime.core.BaseProxyException:
Error sending MS message. Exception: Received HTTP response code 404: Not found.
Anyone have an idea what's happing?
Regards,
Luis Diego

Similar Messages

  • Java proxy client logical port transport to Q and prod issue in target addr

    Hi All,
    I have a java proxy client having a logical port (configured using NWDS) to consume a web service in the provider system.
    In the logical port, I have given target address, and logical port name. While moving this client proxy NWDI dev track to Q and prod,
    how do I change this target address to point to Q and prod respectively. In other words, even though I am using Visual admin to configure the destination url for the logical port, to point to Q and prod, its still referring to the dev environment provider service after moving the proxy client to Q and prod. What is the suggested approach to take care of this issue
    Thx
    mike

    Hi Michael,
    I can only help from that point of view that I believe this question belongs to the forum
    Service-Oriented Architecture (SOA) and SAP
    Please try to raise this question there.
    Thanks and Regards,
    Ervin

  • Dynamic proxy client error

    hello,
    im running a dynamic proxy client for a simple web service. I have the web service up and running but when i run the client i get the following error:
    run-client:
    [java] java.lang.NoClassDefFoundError: dynamicproxy/BookClient
    [java] Exception in thread "main"
    [java] Java Result: 1
    run:
    BUILD SUCCESSFUL
    Total time: 2 seconds
    My client code is as follows:
    package dynamicproxy;
    import java.net.URL;
    import javax.xml.rpc.Service;
    import javax.xml.rpc.JAXRPCException;
    import javax.xml.namespace.QName;
    import javax.xml.rpc.ServiceFactory;
    import dynamicproxy.BookIF;
    public class BookClient{
    public static void main(String[] args){
    try{
    String UrlString = args[0] + "?WSDL";
    String nameSpaceUri = "urn:Foo";
    String serviceName = "MyBookService";
    String portName = "BookIFPort";
    System.out.println("UrlString = " + UrlString);
    URL bookWsdlUrl = new URL(UrlString);
    ServiceFactory serviceFactory = ServiceFactory.newInstance();
                   Service bookService = serviceFactory.createService(bookWsdlUrl,
                   new QName(nameSpaceUri, serviceName));
    dynamicproxy.BookIF
    myProxy = (dynamicproxy.BookIF)
    bookService.getPort(new QName(nameSpaceUri, portName),
    dynamicproxy.BookIF.class);
                   System.out.println("The sum of the 2 numbers is:");
    System.out.println(myProxy.add(1, 2));
    catch (Exception ex)
    ex.printStackTrace();
    Any ideas??

    thnx kwalsh1 i got it working. It was the targets.xml file in jaxrpc/common, i edited the package-dynamic to include all class files!

  • Unable to invoke WebLogic 8.1 sp2 web service from a java proxy client...

    I am not able to invoke a web service deployed on WebLogic 8.1 SP2 via a client using the proxy jar provided by WebLogic's JWS > Overview > Generate Java Proxy tool.
    I am getting a java.net.ConnectException.
    Both the client and the WebService are on the same server.
    Thanks!!
    Inder./

    Please see the instructions below. If this does not help, please open a case with customer support and tell them it may be related to CR235479
    DESCRIPTION:
    When a platform domain is created, the admin server can be started without
    any issues and a managed server can also be started without any errors if
    using startManagedWebLogic.sh. But when a managed server is started using the
    nodemanager, the managed server fails to start with the following error.
    The WebLogic Server did not start up properly.
    java.lang.NoClassDefFoundError: com/bea/wsrp/util/debug/Debug
    (Complete stack trace with be added as a note)
    The reason for this is that:
    startWebLogic.sh(cmd) and startManagedWebLogic.sh(cmd) for platform domains
    call <User domain>/setDomainEnv.sh which includes all the jars necessary for
    a platform domain in the CLASSPATH.
    Whereas startNodeManager.sh calls <WL_HOME>/common/bin/commEnv.sh, which is
    the same for both platform and server installations of weblogic and has only
    weblogic.jar in the CLASSPATH.
    Looking at historical cases, the steps to start NodeManager successfully in a
    platform domain are:
    1.
    a. Copy admin server classpath (from <user Domain>/startWebLogic.sh) to
    that of all managed servers in the 'Remote Start' tab of the WLS Console
    OR
    b. Copy admin server classpath to <WL_HOME>/server/bin/startNodeManager.sh
    (If the same nodemanager is used to manage server domain servers and platform
    domain servers, will there be any issue with this approach??)
    2. Copy the wsrpKeystore.jks file from your domain directory to the
    nodemanager directory (the parent of the directory where all the server
    directories are replicated in the node manager. By default: <WL
    HOME>/common/nodemanager)
    But these steps are not publicly documented in edocs.
    CONFIGURATION:
    Weblogic Platform Domain 8.1 (all service packs)
    WORKAROUND:
    Steps 1 and 2 above.

  • Generating WEB SErvice proxy client error: (type octet-stream)

    HI,
    I'm trying to generate a proxy client from a WSDL which has an element defined as "octet-stream" from http://xml.apache.org/xml-soap
    But I'm getting this error: "model error: type {http://xml.apache.org/xml-soap} octet-stream not found"
    Some suggestion...what can i do.
    thanks

    HI,
    I'm trying to generate a proxy client from a WSDL which has an element defined as "octet-stream" from http://xml.apache.org/xml-soap
    But I'm getting this error: "model error: type {http://xml.apache.org/xml-soap} octet-stream not found"
    Some suggestion...what can i do.
    thanks

  • Change Business System for Java Proxy Client

    I have created Web AS Java business system for Java proxy.
    Is it possbile to send message from client Java Proxy as another business system (Third party)?
    For example to specify this system
    MessageSpecifier messageSpecifier = proxy.$messageSpecifier();
    messageSpecifier.setSenderService("MY_BUSINESS_SYSTEM");
    proxy.$messageSpecifier(messageSpecifier);

    Yes, it is.
    That's the way to do it.
    Stefan

  • Beehive Conferencing Java-based Client Error: Cannot grant permissions to unsigned jars

    Hi,
    When I start a Beehive online web conference via the Java-based client on Ubuntu 12.04, I get the following error:
    net.sourceforge.jnlp.LaunchException: Fatal: Initialization Error: Could not initialize application.
        at net.sourceforge.jnlp.Launcher.createApplication(Launcher.java:778)
        at net.sourceforge.jnlp.Launcher.launchApplication(Launcher.java:552)
        at net.sourceforge.jnlp.Launcher$TgThread.run(Launcher.java:889)
    Caused by: net.sourceforge.jnlp.LaunchException: Fatal: Application Error: Cannot grant permissions to unsigned jars. Application requested security permissions, but jars are not signed.
        at net.sourceforge.jnlp.runtime.JNLPClassLoader.setSecurity(JNLPClassLoader.java:289)
        at net.sourceforge.jnlp.runtime.JNLPClassLoader.<init>(JNLPClassLoader.java:209)
        at net.sourceforge.jnlp.runtime.JNLPClassLoader.getInstance(JNLPClassLoader.java:323)
        at net.sourceforge.jnlp.Launcher.createApplication(Launcher.java:770)
        ... 2 more
    Caused by:
    net.sourceforge.jnlp.LaunchException: Fatal: Application Error: Cannot grant permissions to unsigned jars. Application requested security permissions, but jars are not signed.
        at net.sourceforge.jnlp.runtime.JNLPClassLoader.setSecurity(JNLPClassLoader.java:289)
        at net.sourceforge.jnlp.runtime.JNLPClassLoader.<init>(JNLPClassLoader.java:209)
        at net.sourceforge.jnlp.runtime.JNLPClassLoader.getInstance(JNLPClassLoader.java:323)
        at net.sourceforge.jnlp.Launcher.createApplication(Launcher.java:770)
        at net.sourceforge.jnlp.Launcher.launchApplication(Launcher.java:552)
        at net.sourceforge.jnlp.Launcher$TgThread.run(Launcher.java:889)
    Thanks for your help

    We have an HTTP/HTTPS conflict when downloading the JavaFX client that we have not yet been able to resolve without breaking something else :-)
    We recommend you use the downloadable client - available from the https://beehiveonline.oracle.com/bcentral/action?page=downloadlanding&appId=Oracle+Beehive+Conferencing+Bootstrap%7Cwind…

  • Java Proxy Runtime Error - A remote host refused an attempted connection

    I am able to register my Java server proxy with no errors. However when I message is sent through I get the following error in Xi Adapter:
    <?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>XIAdapterFramework</SAP:Category>
      <SAP:Code area="MESSAGE">GENERAL</SAP:Code>
      <SAP:P1 />
      <SAP:P2 />
      <SAP:P3 />
      <SAP:P4 />
      <SAP:AdditionalText>com.sap.aii.af.ra.ms.api.DeliveryException: Error invoking method someJavaProxyCallIB of proxy bean com.sap.aii.proxy.xiruntime.core.AbstractProxyInboundLocal4LocalObjectImpl0_0: A remote host refused an attempted connect operation.: com.sap.aii.proxy.xiruntime.core.XmlInboundException: Error invoking method someJavaProxyCallIB of proxy bean com.sap.aii.proxy.xiruntime.core.AbstractProxyInboundLocal4LocalObjectImpl0_0: A remote host refused an attempted connect operation.</SAP:AdditionalText>
      <SAP:ApplicationFaultMessage namespace="" />
      <SAP:Stack />
      <SAP:Retry>M</SAP:Retry>
      </SAP:Error>
    Doea anyone know why this is happening?

    I guess, that you have Java proxy libraries in the EAR file. Remove them before deploying.
    Regards
    Stefan

  • Java Proxy Client !!

    Hi Guys,
    I need clarification in regards with " JAVA CLIENT PROXY"
    Questions
    1) Well for sender  (client proxy -- JAVA) what is the CC configuration ? Do we need Sender Agreement?
    2) After i have used the ZIP file in the NWDS and deployed in the JAVA J2EE Server of XI , how to call this ??
    3) What kind of code should i use to invoke the proxy ? kindly elobrate this with some links as am new to JAVA development?
    4) Any walkthrough of the entire process would be helpful>
    kind:ly share u r thoughts on "JAVA CLIENT PROXY"
    Than

    Venkat
    Pls. go through the PDF " How to Work with JAVA Proxy " which will give lot of insight what all requirements & configuration you need to develop Proxy scenario.
    Also go through the document named " Creating First J2EE Application using Dev Studio ".
    All of your questions will be answered by these 2 docs.
    Rgds
    Lalit

  • Java proxy client with HTTP sender

    I have SP15. I have sender agreement with HTTP adapter for system A and Java Proxy Cleint that send message as system A.
    When I send message through Java proxy I see error:
    <i>SOAPFault received from Integration Server. ErrorCode/Category: XIServer/IN_BIND_WRONG_ADPT; Params: HTTP; AdditionalText:  ; ApplicationFaultMessage:  ; ErrorStack: Server agreement found belongs to adapter HTTP; current adapter is 'XI' </i>
    When I deleted sender agreement it worked.
    Could you explain this strange behavior? Is it a bug. Sender agrement for HTTP is necessary since SP16

    I have the same problem with SOAP and file adapter. I've posted this here already.
    XIServer/IN_BIND_WRONG_ADPT
    I have deleted the sender agreement for my soap adapter scenarios, because a sender agreement is not necessary (created by the wizard). After that the soap adapter scenarios work fine. But at scenarios with a sender file adapter you need a sender agreement.
    We had the following situation:
    XI Test, XI SP17, Basis SP16 --> IN_BIND_WRONG_ADPT problem
    XI QA, XI SP17, Basis SP14 --> okay
    XI Prod, XI SP15, Basis SP 16 --> okay
    We patched our XI QA to
    XI QA, XI SP17, Basis SP16
    After that we have the IN_BIND_WRONG_ADPT problem at our XI  QA system too.
    I started a SAPP OSS call two weeks ago but got no solution till now. They checked our systems some times but with no result.
    Our central SLD is on the XI Prod System. Perhaps there is a connection. But I don't want to patch my XI Prod system to SP 17, because it's the only system that works without errors.
    Message was edited by: Gil Ritter

  • 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

  • Synchronous-Asynchronous Interface with Java Proxy

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

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

  • No Class found error in client java proxy

    Hi guys,
    I have configured a java proxy and I'm calling that proxy in a stand alone java program. I'm getting the below error when I execute the program.
    If any one can provide any inputs on the issue it'be great..
    Exception in thread "main" java.lang.NoClassDefFoundError: com/sap/aii/utilxi/sld/XIEntityInSld
         at com.sap.aii.proxy.xiruntime.core.XmlSystemAccess.getProperties(XmlSystemAccess.java:679)
         at com.sap.aii.proxy.xiruntime.core.XmlSystemAccess.getProperty(XmlSystemAccess.java:709)
         at com.sap.aii.proxy.xiruntime.core.XmlSystemAccess.initLogging(XmlSystemAccess.java:471)
         at com.sap.aii.proxy.xiruntime.core.XmlProxy.send(XmlProxy.java:79)
         at com.sap.aii.proxy.xiruntime.core.AbstractProxy$XmlProxyHelper.send(AbstractProxy.java:181)
         at com.sap.aii.proxy.xiruntime.core.AbstractProxy.send$(AbstractProxy.java:142)
         at com.unilever.aa.xproc.procComm.file.kalido.MIKalidoTestOutAs_PortType.mIKalidoTestOutAs(MIKalidoTestOutAs_PortType.java:18)
         at com.bcone.FTP.TestFTPClient.main(TestFTPClient.java:60)

    Try following libs:
    From XI:
    aii_adapter_xi_svc.jar, aii_af_cci.jar, aii_af_cpa.jar, aii_af_mp.jar,
    aii_af_ms_api.jar, aii_af_ms_spi.jar,
    aii_af_service_message_security.jar
    From the J2EE client JARs: (/usr/sap/<SID>/JC00/j2ee/j2eeclient/signed):
    ejb20.jar, exception.jar, guidgenerator.jar, jARM.jar, jperflib.jar,
    jta.jar, log_api.jar, logging.jar, sapj2eeclient.jar, sapni.jar,
    sapxmltoolkit.jar
    See also this guide:
    SAP on DB2 for Linux, UNIX, and Windows
    Regards
    Stefan

  • Error invoking client Java Proxy

    I have a scenario with Client Java Proxy in which a JSP gives call to the EJBs generated from the Message interface. Everything is deployed correctly and when I try to invoke the JSP, following error is reported in the defaultTrace file of J2EE engine.
    com.sap.aii.proxy.xiruntime.core.XmlLandscapeAccess.getJPRConfigurationFromSLD()
    Error getting JPR configuration from SLD. Exception: entityNotFound#
    I found pointers to SAP Note # 809420 as a result of SDN search.
    Has anybody faced similar situation?
    Regards,
    Amol

    Stefan,
    Things worked after the business system was created in SLD.
    I dont see the radio buttons for rewarding points against your post. Will try later to reward points.
    Thanks for your help.
    Regards,
    Amol

  • Error in scenario for client Java Proxy

    2006-04-28 15:30:49 Success Java proxy runtime (JPR) is transferring the request message to the messaging System
    2006-04-28 15:30:49 Success Application attempting to send an XI message synchronously using connection JPR.
    2006-04-28 15:30:49 Success Trying to put the message into the call queue.
    2006-04-28 15:30:49 Success Message successfully put into the queue.
    2006-04-28 15:30:49 Success The message was successfully retrieved from the call queue.
    2006-04-28 15:30:49 Success The message status set to DLNG.
    2006-04-28 15:30:50 Error Received XI System Error. ErrorCode: NO_RECEIVER_CASE_BE ErrorText: ErrorStack: No receiver could be determined 
    2006-04-28 15:30:50 Error Returning synchronous error notification to calling application: XIServer:NO_RECEIVER_CASE_BE:.
    2006-04-28 15:30:50 Error Transmitting the message using connection http://<SERVER>:<PORT>/sap/xi/engine?type=entry failed, due to: XIServer:NO_RECEIVER_CASE_BE:.
    2006-04-28 15:30:50 Error The message status set to FAIL.
    2006-04-28 15:30:50 Error Returning to application. Exception: XIServer:NO_RECEIVER_CASE_BE:
    2006-04-28 15:30:50 Error JPR failed to transfer the request message to the messaging system. Reason: XIServer:NO_RECEIVER_CASE_BE:
    I am getting this in the audit log for a Java Proxy <> XI <> RFC scenario. What could be the problem?
    the configuration in integration directory seems to be perfectly fine however the message flow fails giving this error <b>NO_RECEIVER_CASE_BE</b>
    Regards,
    Amol

    HI Amol,
    Did you check the Message type/Message Inetrface names in the Java Proxy ?
    Also check for Receiever Determinations in the configuration.
    I assume that , you have created the Communication Channel under the Business System created as Standalone Java System.. If not check this.
    Go to SXI_CACHE and check for the Receiever Determination created in the Configuration...
    Hope this helps,
    regards,
    Moorthy

Maybe you are looking for