RFC - Java Proxy (Synchronous) invoking method

Hi,
I have problems to call my inbound java proxy.
My scenario consist of send RFC -> Java Proxy (Synchronous)
Proxy this registered
http://hcp095.intra.csc.es:50100/ProxyServer/register?ns=http://csc.es/xi/rca&interface=Z_RCA_SCS&bean=ZRCASCS_PortTypeBean&method=zRCASCS
ejb-jar.xml:
<ejb-jar>
    <description>EJB JAR description</description>
    <display-name>EJB JAR</display-name>
    <enterprise-beans>
        <session>
            <ejb-name>ZRCASCS_PortTypeBean</ejb-name>
            <home>com.sap.aii.proxy.xiruntime.core.AbstractProxyInboundHome4</home>
            <remote>com.sap.aii.proxy.xiruntime.core.AbstractProxyInboundRemote4</remote>
            <local-home>com.sap.aii.proxy.xiruntime.core.AbstractProxyInboundLocalHome4</local-home>
            <local>com.sap.aii.proxy.xiruntime.core.AbstractProxyInboundLocal4</local>
            <ejb-class>es.csc.xi.rca.ZRCASCS_PortTypeBean</ejb-class>
            <session-type>Stateless</session-type>
            <transaction-type>Container</transaction-type>
        </session>
    </enterprise-beans>
</ejb-jar>
Class Impl:
package es.csc.xi.rca;
public class ZRCASCS_PortTypeImpl extends AbstractProxy implements ZRCASCS_PortType {
public ZRCASCSResponse_Type zRCASCS(ZRCASCS_Type parameters) throws ZRCASCSException_Message_Exception, SystemFaultException,  ApplicationFaultException{
        //throw new RuntimeException();
        Rca_ws a = new Rca_ws();
        return a.zRCASCS(parameters);
Error: XI_Monitor 
<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 zRCASCS of proxy bean $Proxy305: cannot assign instance of com.sap.guid.GUID to field com.sap.aii.proxy.xiruntime.core.MessageSpecifierImpl.guid of type com.sap.guid.IGUID in instance of com.sap.aii.proxy.xiruntime.core.MessageSpecifierImpl: com.sap.aii.proxy.xiruntime.core.XmlInboundException: Error invoking method zRCASCS of proxy bean $Proxy305: cannot assign instance of com.sap.guid.GUID to field com.sap.aii.proxy.xiruntime.core.MessageSpecifierImpl.guid of type com.sap.guid.IGUID in instance of com.sap.aii.proxy.xiruntime.core.MessageSpecifierImpl</SAP:AdditionalText>
  <SAP:ApplicationFaultMessage namespace="" />
Error: defaultTrace
#hcp095.intra.csc_XID_19271950#ANGUZMAN#ec20b7f019f611de98340011259e6830#
SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain##
#com.sap.aii.proxy.xiruntime.core.XmlProxyException: Error invoking method zRCASCS of proxy bean $Proxy366:
cannot assign instance of com.sap.guid.GUID to field com.sap.aii.proxy.xiruntime.core.MessageSpecifierImpl.guid
of type com.sap.guid.IGUID in instance of com.sap.aii.proxy.xiruntime.core.MessageSpecifierImpl
     at com.sap.aii.proxy.xiruntime.core.XmlProxyJ2EE.call(XmlProxyJ2EE.java:192)
     at com.sap.aii.proxy.xiruntime.core.XmlProxy$ProxyBeanCaller.call(XmlProxy.java:225)
     at com.sap.aii.proxy.xiruntime.core.XmlProxy.processRequest(XmlProxy.java:194)
     at com.sap.aii.proxy.xiruntime.core.XmlInbound.processRequestMessage(XmlInbound.java:126)
     at com.sap.aii.proxy.xiruntime.core.XmlInbound.processMessage(XmlInbound.java:83)
     at com.sap.aii.proxy.xiruntime.sbeans.JPRBean.onMessage(JPRBean.java:158)
     at com.sap.aii.proxy.xiruntime.sbeans.JPRLocalLocalObjectImpl0_0.onMessage(JPRLocalLocalObjectImpl0_0.java:175)
     at com.sap.aii.af.ra.ms.impl.ServicesImpl.deliver(ServicesImpl.java:276)
     at com.sap.aii.adapter.xi.ms.XIEventHandler.onDeliver(XIEventHandler.java:1049)
     at com.sap.aii.af.ra.ms.impl.core.queue.RequestConsumer.onMessage(RequestConsumer.java:119)
     at com.sap.aii.af.ra.ms.impl.core.queue.Queue.run(Queue.java:850)
     at com.sap.aii.af.ra.ms.runtime.MSWorkWrapper.run(MSWorkWrapper.java:56)
     at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
     at java.security.AccessController.doPrivileged(AccessController.java:180)
     at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:102)
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)
If somebody can help me.
Thank you very much

Solved!!!
to assign library references to the project application-j2eeengine.xml
com.sap.aii.proxy.xiruntime
com.sap.aii.messaging.runtime
com.sap.xi.util.misc
com.sap.guid

Similar Messages

  • Getting Inbound Java Proxy Exception in method "onMessage"

    I have built an Inbound Java proxy, deployed the EJB, viewed it in the J2EE admin tool, registered the JPR settings (also listAll, reviewed results, looks OK), configure the XI scenario.  When I run the XI scenario using the Runtime workbench I get the following error in the BPM Synchronous Send step (calling the Java Proxy)
    "com.sap.aii.af.ra.ms.api.DeliveryException: Exception in method onMessage".
    Does anyone have any suggestions?
    What causes an "onMessage" Exception?

    Thanks Sudhir  Here is the process I am following to deploy my Proxy, would you please validate it.  Created EJB Project in NWDS, unziped XI gened proxies into ejbModule folder, renamed *PortTypeImpl.template to *PortTypeImpl.java (will add real code later), compiled all code (no errors), edited ejb_jar.xml to match your suggested format, can view EJB Candidates (and see my Proxy Bean), built EJB.JAR file (via Wizard), created new Enterprise Application Project and pointed build path to my EJB Project, within the Enterprise Application Project  I built an EAR file (which includes the "EJB Project JAR File",  Deployed Enterprise Application Project to the XI J2EE Engine.  I can log into XI J2EE Admin and see my EJB Project and the Proxy Bean I am trying to execute.  Is this the process you used to deploy the proxy bean?
    Also you you turn on JPR Tracing to see what parameters are passed into the JPR engine?

  • Java Proxy error: Exception in method methodExists

    Hello all!
    We are doing the following synchronous scenario:  CRM->XI->JavaProxy--->Third party....
    Here is the process we are following to deploy our Proxy:
    1.Created EJB Module Project in NWDS
    2.Import the files generated by XI into ejbModule folder from ZIP file.
    3.Renamed *PortTypeImpl.template to *PortTypeImpl.java
    4.Compiled all code (no errors)
    5.Added all the references to the SAP libraries required (taken from our XI server):
    com.sap.aii.proxy.xiruntime
    com.sap.xi.util.misc
    com.sap.aii.messaging.runtime
    com.sap.guid
    6.Codified Java Proxy – codified the method <interfacename> in the <intefacename>_PortTypeImpl class.
    7.Edited ejb_jar.xml to add EJBs.
    8.Provided a JNDI name in the file ejb-j2ee-engine.xml.
    9.Built EJB archive (no errors).
    10.Created a new Enterprise Application Project and pointed build path to our EJB Project.
    11.Added our EJB to the Enterprise Application project.
    12.Created the references to the SAP libraries in the Enterprise Application Project in the application-j2ee-engine.xml file:
    com.sap.aii.proxy.xiruntime
    com.sap.xi.util.misc
    com.sap.aii.messaging.runtime
    com.sap.guid
    13.Within the Enterprise Application Project we built an EAR file.
    14.We deployed our .ear file to the J2EE Engine via Visual Admin (no errors).
    15.We registered our Java Proxy  on the ProxyServer, using
    /register?ns=<interface_namespace>&interface=<XI_Interface_Name>&bean=<EJB_JNDI_name> &method=<name of the method implemented by you on the _PortTypeImpl>
    Actually, we did the following:
    url for registering the EJB:
    http://ithpsrq0:50200/ProxyServer/register?ns=http://banco.popular.com.pr/xi/crm&interface=mi_AccountInfo_is&bean=popularinc.com/MiAccountInfoIs_Default&method=miAccountInfoIs
    Message displayed when listing interfaces (http://ithpsrq0:50200/ProxyServer/listAll)
    http://banco.popular.com.pr/xi/crm#mi_AccountInfo_is = popularinc.com/MiAccountInfoIs_Default:miAccountInfoIs
    1 interfaces found
    When running the interface we get the following error:
    com.sap.aii.af.ra.ms.api.DeliveryException: Error checking method name miAccountInfoIs of remote inbound proxy bean $Proxy250: Exception in method methodExists.: com.sap.aii.proxy.xiruntime.core.XmlInboundException: Error checking method name miAccountInfoIs of remote inbound proxy bean $Proxy250: Exception in method methodExists.
    Does anyone have any suggestions?
    What causes a "methodExists" Exception?
    Please help us,
    Thanks a lot!!!

    Hi,
      Is this a runtime of "com.sap.aii.proxy.xiruntime.core"
    please check the jars used, adding this jars will solve this i guess.
    aii_utilxi_misc.jar
    ejb20.jar
    exception.jar
    jARM.jar
    sapj2eeclient.jar
    sapxmltoolkit.jar
    aii_msg_runtime.jar
    aii_proxy_xirt.jar
    Also check, application-j2ee-engine.xml  and see if,
    com.sap.aii.proxy.xiruntime
    com.sap.aii.messaging.runtime
    com.sap.xi.util.misc
    com.sap.guid
    You wil get the jars in XI servers, you can ftp and get the jars, but you may need to search them.
    Anotherthing, always take the jars from the xi servers to be sure you are compatible with the upgrades .
    Hope this solves your problem.
    Anirban.

  • Call Client Java Proxy from Server Java Proxy

    Hi Gurus!!
    I'm trying to call a Client Java Proxy from a Server Java Proxy.
    Is possible to do this? I think must be possible.
    I have called this Client Java Proxy from another application, and run ok.
    I have tried to call it following the Guide to call Java Client Proxies:
                    es.navantia.xi.mm.dispositivosRobotizadosKasto.MIRobotOut_PortTypeHome queryOutHome = null;
                    es.navantia.xi.mm.dispositivosRobotizadosKasto.MIRobotOut_PortTypeRemote queryOutRemote = null;                     
                    try {
                         //      Get naming context
                         Properties p = new Properties();
                         p.put(
                              Context.INITIAL_CONTEXT_FACTORY,
                              "com.sap.engine.services.jndi.InitialContextFactoryImpl");
                         p.put(Context.PROVIDER_URL, "myurl:50104");
                         p.put(Context.SECURITY_PRINCIPAL, "MMIGUEZ");
                         p.put(Context.SECURITY_CREDENTIALS, mypasswrod);
                         Context ctx = new InitialContext(p);
                         Object ref = ctx.lookup("RobotOut");
                         //      Look up jndi name of proxy bean
                        try {
                         queryOutHome =
                              (MIRobotOut_PortTypeHome) PortableRemoteObject.narrow(
                                   ref,
                                   MIRobotOut_PortTypeHome.class);
                        } catch (Exception e) {
                             throw new RuntimeException(e + "1");
                         //        Get Remote interface
                         queryOutRemote = queryOutHome.create();
                    } catch (Exception e) {
                        throw new RuntimeException(e + "2");
    but I get this error
    "com.sap.aii.af.ra.ms.api.DeliveryException: Error invoking method mIRobotIn of proxy bean $Proxy351: es.navantia.xi.mm.dispositivosRobotizadosKasto.MIRobotOut_PortTypeHome: com.sap.aii.proxy.xiruntime.core.XmlInboundException: Error invoking method mIRobotIn of proxy bean $Proxy351: es.navantia.xi.mm.dispositivosRobotizadosKasto.MIRobotOut_PortTypeHome"
    es.navantia.xi.mm.dispositivosRobotizadosKasto.MIRobotOut_PortTypeHome is the corresponding PortTypeHome to the Client Java Proxy.
    I have tried to call too calling directly from the server Java Proxy to the method correcponding to the Client Java Proxy. The error I get is:
    "com.sap.aii.af.ra.ms.api.DeliveryException: Error invoking method mIRobotIn of proxy bean $Proxy351: es/navantia/xi/mm/dispositivosRobotizadosKasto/DTRobot_Type: com.sap.aii.proxy.xiruntime.core.XmlInboundException: Error invoking method mIRobotIn of proxy bean $Proxy351: es/navantia/xi/mm/dispositivosRobotizadosKasto/DTRobot_Type"
    Tha call to the client is:
    es.navantia.xi.mm.dispositivosRobotizadosKasto.MIRobotOut_PortType clase = null;
    es.navantia.xi.mm.dispositivosRobotizadosKasto.DTRobot_Type client_req = null;
    es.navantia.xi.mm.dispositivosRobotizadosKasto.DTRobotResponse_Type client_res = null;
    client_res = clase.mIRobotOut(client_req);
    Please, any help will be useful.
    Thanks and regards,
    Manuel Míguez.

    Hi,
    Now I get another error message:
    com.sap.aii.af.ra.ms.api.DeliveryException: Error invoking method mIRobotIn of proxy bean $Proxy351: es/navantia/xi/mm/dispositivosRobotizadosKasto/MITextoOut_PortTypeRemote: com.sap.aii.proxy.xiruntime.core.XmlInboundException: Error invoking method mIRobotIn of proxy bean $Proxy351: es/navantia/xi/mm/dispositivosRobotizadosKasto/MITextoOut_PortTypeRemote
    Now, my source is:
      MITextoOut_PortTypeHome queryOutHome = null;
      MITextoOut_PortTypeRemote queryOutRemote = null;
      try {
    //     Get naming context
    Context ctx = new InitialContext();
    //     Look up the EJB name in the environment
    Object ref = ctx.lookup("java:comp/env/ejb/TextoOut");
    // Object ref = ctx.lookup("java:comp/env/ejb/MITextoOut_PortTypeBean");
    //     Cast to Home interface
         queryOutHome = (MITextoOut_PortTypeHome)
    PortableRemoteObject.narrow(ref,
    MITextoOut_PortTypeHome.class);
    //     Get Remote interface
    queryOutRemote = queryOutHome.create();
    } catch (Exception e) {
    System.out.println("RemoteException occurred: "+e.getMessage());
    e.printStackTrace();
    //return;
    try {
          queryOutRemote.$messageSpecifier();
    } catch (RemoteException e2) {
          // TODO Auto-generated catch block
          e2.printStackTrace();
    DTTexto_Type Texto_type = new DTTexto_Type();
    Texto_type.setTexto(req_texto);
    DTTextoResponse_Type Texto_response = new DTTextoResponse_Type();
    try {
         Texto_response = queryOutRemote.mITextoOut(Texto_type);
    } catch (SystemFaultException e1) {
          // TODO Auto-generated catch block
          e1.printStackTrace();
    } catch (ApplicationFaultException e1) {
          // TODO Auto-generated catch block
          e1.printStackTrace();
    } catch (RemoteException e) {
          // TODO Auto-generated catch block
          e.printStackTrace();
    I have tryed removing queryOutRemote.$messageSpecifier() and I get the error:
    com.sap.aii.af.ra.ms.api.DeliveryException: Error invoking method mIRobotIn of proxy bean $Proxy351: es/navantia/xi/mm/dispositivosRobotizadosKasto/DTTexto_Type: com.sap.aii.proxy.xiruntime.core.XmlInboundException: Error invoking method mIRobotIn of proxy bean $Proxy351: es/navantia/xi/mm/dispositivosRobotizadosKasto/DTTexto_Type
    Somebody knows what could be the cause of these errors?
    Thanks and regards,
    Manuel.

  • 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 Java Proxy Server template - filling reponse message elements

    Hi !
    I'm writing a java proxy server for a synchronous interface. I'm somehow new in java...and I don't know how should I create elements for my response message inside the java method used to process the request message.
    The response message format is something like this:
    <field1>abc</field1>
    <field2>
    ....<field2a>
    ........<fields2a1>
    ........</fields2a1>
    ....</field2a>
    ....<field2a>
    ....</field2a>
    </field2>
    according to the type "DT_Output_Type" type of the public class MyMethod defined in the java template generated by XI repository..
    I think I should do something like this:
    DT_Output_Type response = new DT_Output_Type();
    DT_Output_Type.field2_List field2values = new DT_Output_Type.field2_List();
    field2values.setfield2a(0,"1234");
    response.setfield1 = "abc";
    response.setfield2(field2values);
    return response;
    But I receive "Error invoking method". If I comment out the code where I assign values to sub-elements, everything works ok.
    Thanks !
    Matias

    Hi Matias,
    >><i>DT_Output_Type.field2_List field2values = new DT_Output_Type.field2_List();</i>
    This will create instance for field2 only.
    Before setting field2a using <i>field2values.setfield2a(0,"1234");</i> you must creat instance of field2a and also for field2a1.
    I guess field2a will be an array.
    so the order of creating instance and setting values can be ...
    1. create instance of field2
    2. create instance of field2a array
    3. create instance of first array element of field2a
    4. create instance of field2a1
    5. set value for field2a1
    6. set field2a1 in first array element of field2a
    repeat steps 3-6 for next elements of field2a
    7. set field2a array object (created in step 2) in field2
    8. response.setfield2(field2values);
    Also,
    as mentioned by Amol, set value for filed1 should be
    response.setfield1("abc");
    Regards,
    Uma

  • RFC lookup with java proxy class, how do I use "fromXml()"?

    Hi,
    I'm trying to do an RFC lookup in XI using java proxy classes (SAP Enterprise Connector).
    The XMLPayload comes from a java proxy class which has been converted to xml using a method called
    .fromXml() for this. I just don't know how to use and I can't find any documentation for it.
    Would very much appreciate if someone could provide me with an example of how to use this class
    Best Regards
    Olof Trönnberg

    http://xstream.codehaus.org/javadoc/com/thoughtworks/xstream/XStreamer.html#fromXML(com.thoughtworks.xstream.io.HierarchicalStreamDriver,%20java.io.Reader)

  • Unable to invoke java proxy in PI 7.1

    Hi ,
    I am using NWDS 7.2 (Trial ver) and using it to deploy java proxy on PI 7.1.
    I also registered the interface using http://<pi>:<port>/ProxyServer url
    But when I invoke the proxy I get the error as
    "Cannot locate proxy bean"
    Please tell me what to do...
    regards,
    Piyush

    Hi,
    This sort of error usually comes when JPR cannot find the deployed java server proxy bean.
    1) Register ur server proxy using this :
    http://host:port/ProxyServer/register?ns=xxx&interface=SI_Proxy_IA&bean=localejbs/Jndi-name&method=method name
    refer this: http://help.sap.com/saphelp_nw04/helpdata/en/a4/d5b3b0b16843b3867c0245d9847ae5/content.htm
    2)Chk whether u have mentioned the corrcet JNDI name while registering the URL.
    3) Chk ur JNDI name under NWA.
    4) Chk ur references under application-j2ee-engine.xml.
    <?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>
      </application-j2ee-engine>
    Thanks
    Amit

  • Difference between invoking a method using reflect.proxy and reflect.Method

    Could any one tell me the difference between invoking a method using reflection java.lang.reflect.Method and java.lang.reflect.Proxy
    using both the class, we can invoke a method at runtime
    1)
    Method mthd=cl.getMethod("methodName",parameterName);
    Integer output=(Integer)mthd.invoke(new RunMthdRef(),input);
    2)
    Proxy.newProxyInstance(super.getClass().getClassLoader(), new Class[] { adapter }, new SomeClass(this));
    Does anybody have any idea?

    The two idioms are fundamentally different. Using java.lang.reflect.Method is how we call a method on a class, using Proxy is how we intercept that method call. An exercise for you, to illustrate that they do not do the same thing: write a simple class with one method, then use java.lang.reflect.Method to invoke that method, and then use a Proxy to invoke that method

  • RFC - XI - Java Proxy HTTP_RESP_STATUS_CODE_NOT_OK

    Hi all,
    I need to work on RFC->XI-> Java proxy.
    While excuting, i am getting an error :
    <SAP:Category>XIServer</SAP:Category>
      <SAP:Code area="INTERNAL">HTTP_RESP_STATUS_CODE_NOT_OK</SAP:Code>
      <SAP:P1>400</SAP:P1>
      <SAP:P2>Bad Request</SAP:P2>
    Can any body please guide?
    Regards,
    Kulwant

    Hi Kulwanth,
    Plz do check the mentioned possibilities for your error one by one:
    1.Did you maintain Client, userid, password, and lang information in SICF transaction -> sap/xi/engine? Double click on service and check whether you have entered correct information.
    2.Then you might check the roles of the XIISUSER in SU01. In some case there are some double roles, i.e., two times the role SAP_XI_IS_SERV_USER assigned. One might have the date of the last update, the other one might have apparently the older version. Delete the older roles manually and the error should disappear.
    3.to send messages to xi you need a service id / pwd which is specific to your landscape usually its xiappluser. Contact your basis group for password.
    4.
    Activated all services on the r3 system.
    Create HTTP connection to XI from r3
    sm59-> http connetons to r3
    let us say you have created a HTTP connection in the integrationserver_XI, make sure in its settings the prefix path is set to /sap/xi/engine?type=entry. Also check its log on credentials, you can use xiappluser.
    IN Integration builder, receiver communication channel make sure you have entered proper
    host service number
    path = /sap/xi/enigne?type = receiver.
    5. It might also be that you have authorization problems with your XISUPER. In the visual administrator and in ABAP SU01, make your XISUPER has all the necessary(SAP_SLD* and SAP_XI*) roles assigned to it. If not, try to assign these and see if this can be of any help.
    6. can you also try the following;
    Visual Admin -> start the service,
    "com.sap.aii.af.ms.app".
    Please go through the followings links also :
    http://help.sap.com/saphelp_nw04/helpdata/en/82/f4993c03e0cd37e10000000a11405a/content.htm
    The specified item was not found.
    http://help.sap.com/saphelp_nw04/helpdata/en/39/83682615cd4f8197d0612529f2165f/frameset.htm
    http://help.sap.com/saphelp_nw04/helpdata/en/39/83682615cd4f8197d0612529f2165f/frameset.htm
    I hope the info provided help you solve your error.
    Regards,
    Vinod.

  • RFC - XI - Java Proxy

    Hi all,
    I need to configure RFC -> XI -> Java proxy.
    While doing so, i am getting below error in SXMB_MONI
    HTTP_RESP_STATUS_CODE_NOT_OK
    following error occurred while parsing the HTTP request: com.sap.engine.services.httpserver.exceptions.ParseException: Incorrect request line: [POST MessagingSystem/receive/AFW/XI HTTP/1.0]..&lt;br&gt;&lt;b&gt; Exception id:
    Can any body please suggest the solution.
    Any help will be appriciated.
    Regards,
    Kulwant

    hi
    port 50000 is the dedicated java-http port. port 8000 is the ICM-port (Internet Communictaion Manager). The ICM distinguishes with the URL-path whether it has to forward the request to the ABAP-stack or to the Java stack.
    ICM port for Java server like http://hostname:80nn/index.html.
    For the J2EE Engine, 20 ports are available for the dispatcher element and 80 are available for the server elements, since five is the maximum number of ports for a server process. Therefore, no more than 16 server cluster elements can be created on one instance.
    The default J2EE Engine ports meet the following requirements:
    ●     The port value is a number over 50000
    ●     For each cluster element the ports begin with 50000+100*instance_number, where instance_number is a two digit number from 00 to 99 specifying the number of central instance and dialog instances.
    You can see the instance number from the directory, where the J2EE Engine is installed. Under /usr/sap/<SID>, there is a directory which name contains the instance name including the instance number, for example, JC40 (where 40 is the instance number).
    ○     For dispatcher cluster elements
    The ports are created from 50000100*instance_numberport_index, where port_index is a number from 0 to 19 inclusive.
    check the below link for
    J2EE Engine Dispatcher Ports
    http://help.sap.com/saphelp_nw04s/helpdata/en/a2/f9d7fed2adc340ab462ae159d19509/frameset.htm
    reward points if helpfull
    regards
    kummari

  • Invoking methods via java.lang.Method.invoke().

    I need to invoke the getter methods that I have defined for a Trade object passed as an argument.
    I am getting the excepion : java.lang.IIlegalArgumentException: wrong number of arguments.
    This is the first time I am invoking methods this way.
    Am I correct to assume that methods on an object can be invoked in this way?
    How can I invoke the getter methods of the trade object.
    Please help.
    public void displayData(Trade trade){
         Method[] m = trade.getClass().getMethods();
         for(int i=0;i<m.length;i++){
              if(m.getName().startsWith("get")){
                        try {
                             m[i].invoke(trade, new Trade[] { trade });
                        } catch (IllegalArgumentException e) {
                             e.printStackTrace();
                        } catch (IllegalAccessException e) {
                             e.printStackTrace();
                        } catch (InvocationTargetException e) {
                             e.printStackTrace();

    bhuru_luthria wrote:
    The getter methods of the trade object require no arguments.
    The three getter methods of the trade object are:
    getTradeId();
    getProductId()
    getReferenceId()Read the Javadoc; use it like this:
    m.invoke(trade);                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           

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

  • Synchronous interfaces missing in Java proxy generation

    Hi,
    In PI 7.1 ESR, in "Java proxy generation" wizard, it only lists the Asynchronous interfaces from the software component version. None of the synchronous interfaces are listed.  how can I solve this? I need to generate a java proxy for a syncronous interface.
    thanks and regards,
    Raghu

    Make sure that the inteface pattern is "stateless (XI 3.0 compatible)".

  • 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

Maybe you are looking for