Java Proxy Runtime:  failure to locate proxy bean on inbound call

Hello gurus of the SDN,
I have been trying to get an inbound Java Proxy scenario to work in XI 3.0 but have not been able to get the JPR to recognize my generated and deployed java code.  My scenario is set up to call the java proxies generated from a message interface based on the MATMAS Idoc.  I successfully deployed the generated java proxies on the same host box as is running the XI instance.  The objects are named as follows
Message interface on XI = Inbound_MATMAS04
Generated proxy bean = Inbound_MATMAS04_PortTypeBean
Implementing class = InboundMATMAS04_PortTypeImpl
Implementing method = inboundMATMAS04
I used the JPR transport servlet to register the interface and implementing class but am not sure if I did this correctly.  I used the following entry in my web browser:
http://nadcp786:50000/ProxyServer/register?
ns=urn:xiTrainingLabs:groupXX:SAP&
interface=InboundMATMAS04&
bean=InboundMATMAS04_PortTypeImpl&
method=inboundMATMAS04
I also tried using the localejb/ prefix for the bean name in the above step since the code is co-located.  When I trigger the scenario, the Idoc info is passed into XI and the Java Proxy Runtime is called, but I get the following error response back in the SOAP header:
- <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="PARSING">GENERAL</SAP:Code>
  <SAP:P1 />
  <SAP:P2 />
  <SAP:P3 />
  <SAP:P4 />
  <SAP:AdditionalText>com.sap.aii.af.ra.ms.api.DeliveryException: Cannot locate proxy bean InboundMATMAS04_PortTypeImpl: com.sap.aii.proxy.xiruntime.core.XmlInboundException: Cannot locate proxy bean InboundMATMAS04_PortTypeImpl</SAP:AdditionalText>
  <SAP:ApplicationFaultMessage namespace="" />
  <SAP:Stack />
  <SAP:Retry>M</SAP:Retry>
  </SAP:Error>
Finally, appended at the end of this post is the audit log of the messaging system showing that the JPR is called but without being able to locate the bean.  I think I am missing a configuration step somewhere, but can’t figure out what it is!!  Can anyone help me? 
Many thanks in advance.
Regards,
Nick Simon
Time Stamp     Status     Description
2004-10-25 19:47:32     Success     The message was successfully received by the messaging system. Profile: XI URL: http://nadcp786.bcsdc.lexington.ibm.com:50000/MessagingSystem/receive/JPR/XI
2004-10-25 19:47:32     Success     Using connection JPR. Trying to put the message into the receive queue.
2004-10-25 19:47:32     Success     The message was successfully retrieved from the receive queue.
2004-10-25 19:47:32     Success     The message status set to DLNG.
2004-10-25 19:47:32     Success     Java proxy runtime (JPR) accepted the message
2004-10-25 19:47:34     Error     JPR could not process the message. Reason: Cannot locate proxy bean localejbs/InboundMATMAS04_PortTypeImpl
2004-10-25 19:47:34     Error     Delivery of the message to the application using connection JPR failed, due to: Cannot locate proxy bean localejbs/InboundMATMAS04_PortTypeImpl.
2004-10-25 19:47:34     Error     The message status set to FAIL.
2004-10-25 19:47:34     Error     Asynchronous error detected: Cannot locate proxy bean localejbs/InboundMATMAS04_PortTypeImpl. Trying to report it.
2004-10-25 19:47:34     Error     Asynchronous error reported.
Message was edited by: Nicholas Simon

Hi
How do you determine the JNDI naming of the a EJB?
I have following entry in JNDI directory in the root
Object Name FlightQueryIn
Class Name javax.naming.Reference
Context Name 
Object Value Reference Class Name:
Type: clientAppName
Content: sap.com/JavaProxyEAR
Type: interfaceType
Content: remote
Type: home
Content: com.sap.aii.proxy.xiruntime.core.AbstractProxyInboundHome4
Type: ejb-link
Content: FlightSeatAvailabilityQueryIn_PortTypeBean
Type: jndi-name
Content: FlightQueryIn
Type: remote
Content: com.sap.aii.proxy.xiruntime.core.AbstractProxyInboundRemote4
I tried to register the bean with JPR using:
http://ctsapxid01:50100/ProxyServer/register?ns=http://sap.com/xi/XI/Demo/Airline&interface=FlightSeatAvailabilityQuery_In&bean=FlightQueryIn&method=flightSeatAvailabilityQueryIn
I followed the following blog
http://wiki.sdn.sap.com/wiki/display/Java/JavaProxyChangesinPI7.1fromPI7.0
Thanks,
Chris

Similar Messages

  • Error with JPR(Java Proxy Runtime) in Adapter Monitor of RWB

    Dear Experts,
                 I am implementing scenario with Client Java Proxy(Outbound) and Server ABAP Proxy(Inbound). We have done all the designing in IR and configurations in ID. We have deployed the EAR successfully. But when we go to RWB(Runtime Work Bench) to monitor the inital status of JPR in RWB->Adapter Monitor. It shows the following error.
    Status     Name                                Text
    Error        SLD Access                     SLD host:port = yhsapi01.yashsap.com:50000
    Error getting JPR configuration from SLD. Exception: Connect to SAP gateway failed
    Connect_PM TYPE=A ASHOST=yhsapi01 SYSNR=00 GWHOST=yhsapi01 GWSERV=sapgw00 PCS=1
    LOCATION CPIC (TCP/IP) on local host with Unicode
    ERROR max no of 100 conversations exceeded
    TIME Wed Jun 03 19:42:45 200
    RELEASE 700
    COMPONENT CPIC (TCP/IP) with Unicode
    VERSION 3
    RC 466
    MODULE r3cpic.c
    LINE 10713
    COUNTER 5521
    No access to get JPR configuration

    Hi!
    Obviously there are more than 100 connections opened in your system.
    ERROR max no of 100 conversations exceeded
    Please check your gateway settings (in ABAP you can check the parameters using transaction SMGW).
    Regards,
    Volker

  • Give me description about JAVA Proxy Runtime and JAVA Proxy Server

    Give me description about JAVA Proxy Runtime and JAVA Proxy Server with some examples.

    Hi,
    Java proxy runtime :
    Using the Java proxy runtime you can receive messages or send messages to the Integration Server.
    This will help you
    http://help.sap.com/saphelp_nw04/helpdata/en/64/7e5e3c754e476ee10000000a11405a/frameset.htm
    Java proxy server :
    The connection to the Integration Server by using the Java proxy runtime.
    This will help you
    http://help.sap.com/saphelp_nw04/helpdata/en/87/5305adc23540b8ac7bce08dbe96bd5/frameset.htm
    Regards
    Agasthuri Doss

  • PCK and Java Proxy Runtime

    Hello,
    I am a newbie to XI world and have some questions regarding PCK and Java Proxy Runtime. Is it possible to send the message from PCK by using Java Proxy Runtime as Sender?
    If yes what exactly configuration steps have to be done on PCK side like SLD & ExchangeProfile configuration according to Configuration Guide or XI Receiver Adapter with Receiver agreement creation?
    Thanks in advance,
    Viktar

    Hi Stefan,
    Thanks for information. We successfully checked a simple test scenarion JPR -> PCK -> File. It was necessary to configure properly XI Sender and File Receiver adapters on PCK.
    SLD and Exchange Profile were not required to be configurable but in this case we have to use MessageSpecifier interface in client proxy for sender and receiver determinations.
    Regards,
    Viktar

  • Proxy Runtime Error in RWB.

    Hi All,
    I am getting following error,
    Please, help me to solve this problem
    Message: Neither the messager server nor the application server can be reached for system DSM
    Stacktrace:
    com.sap.aii.rwb.exceptions.OperationFailedException: Neither the messager server nor the application server can be reached for system DSM
    at com.sap.aii.rwb.core.R3System.getJCOPool(R3System.java:863)
    at com.sap.aii.rwb.core.R3System.getJCOPool(R3System.java:726)
    at com.sap.aii.rwb.core.R3System.getJCOPool(R3System.java:698)
    at com.sap.aii.rwb.core.R3System.getRepository(R3System.java:910)
    at com.sap.aii.rwb.core.BusinessSystem.getRepository(BusinessSystem.java:802)
    at com.sap.aii.rwb.core.XIAbapRTCComponent.getConnector(XIAbapRTCComponent.java:97)
    at com.sap.aii.rwb.core.XIRTCComponent.ping(XIRTCComponent.java:209)
    at com.sap.aii.rwb.web.componentmonitoring.model.CompTestModel.doPing(CompTestModel.java:580)
    at com.sap.aii.rwb.web.componentmonitoring.viewcontroller.CmDynPage.doPing(CmDynPage.java:307)
    at com.sap.aii.rwb.web.componentmonitoring.viewcontroller.CmDynPage.updateTests(CmDynPage.java:381)
    at com.sap.aii.rwb.web.componentmonitoring.viewcontroller.CmDynPage.selectNode(CmDynPage.java:397)
    at com.sap.aii.rwb.web.componentmonitoring.viewcontroller.CmDynPage.process_treeClick(CmDynPage.java:348)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:324)
    at com.sapportals.htmlb.page.DynPage.doProcessCurrentEvent(DynPage.java:172)
    at com.sapportals.htmlb.page.PageProcessor.handleRequest(PageProcessor.java:115)
    at com.sapportals.htmlb.page.PageProcessorServlet.handleRequest(PageProcessorServlet.java:62)
    at com.sapportals.htmlb.page.PageProcessorServlet.doPost(PageProcessorServlet.java:22)
    at com.sap.aii.rwb.web.componentmonitoring.viewcontroller.CmPageProcessor.doPost(CmPageProcessor.java:35)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
    at com.sap.engine.services.servlets_jsp.server.runtime.RequestDispatcherImpl.doWork(RequestDispatcherImpl.java:321)
    at com.sap.engine.services.servlets_jsp.server.runtime.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:377)
    at jsp_FC_Secure1221049856634._jspService(jsp_FC_Secure1221049856634.java:24)
    at com.sap.engine.services.servlets_jsp.server.jsp.JspBase.service(JspBase.java:112)
    at com.sap.engine.services.servlets_jsp.server.servlet.JSPServlet.service(JSPServlet.java:566)
    at com.sap.engine.services.servlets_jsp.server.servlet.JSPServlet.service(JSPServlet.java:190)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
    at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
    at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
    at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)
    at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
    at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039)
    at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
    at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
    at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
    at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
    at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
    at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
    at java.security.AccessController.doPrivileged(Native Method)
    at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:102)
    at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)
    Thanks In Advance
    Mahesh

    Hi Seshagiri,
    Actually, i am getting this error in message Monitoring dropdown, i have Proxy Runtime Receiver System option. when i am selecting the same i am getting the following error.
      javax.ejb.CreateException: Neither the messager server nor the application server can be reached for system DSM
    javax.ejb.CreateException: Neither the messager server nor the application server can be reached for system DSM
         at com.sap.aii.mdt.server.integrationengine.IntegrationEngineMonitoringBean.ejbCreate(IntegrationEngineMonitoringBean.java:456)
         at com.sap.aii.mdt.api.server.IntegrationEngineHomeImpl1_0.create(IntegrationEngineHomeImpl1_0.java:195)
         at com.sap.aii.mdt.api.server.IntegrationEngineHome_Stub.create(IntegrationEngineHome_Stub.java:57)
         at com.sap.aii.mdt.util.MonitoringBeanCache.getMonitoringBean(MonitoringBeanCache.java:305)
         at com.sap.aii.mdt.util.WebUtil.getMonitor(WebUtil.java:351)
         at jsp_monitor_new1221049881372._jspService(jsp_monitor_new1221049881372.java:140)
         at com.sap.engine.services.servlets_jsp.server.jsp.JspBase.service(JspBase.java:112)
         at com.sap.engine.services.servlets_jsp.server.servlet.JSPServlet.service(JSPServlet.java:566)
         at com.sap.engine.services.servlets_jsp.server.servlet.JSPServlet.service(JSPServlet.java:190)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.sap.engine.services.servlets_jsp.server.runtime.RequestDispatcherImpl.doWork(RequestDispatcherImpl.java:321)
         at com.sap.engine.services.servlets_jsp.server.runtime.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:377)
         at com.sapportals.htmlb.page.PageProcessorServlet.handleRequest(PageProcessorServlet.java:68)
         at com.sapportals.htmlb.page.PageProcessorServlet.doGet(PageProcessorServlet.java:29)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.sap.engine.services.servlets_jsp.server.runtime.RequestDispatcherImpl.doWork(RequestDispatcherImpl.java:321)
         at com.sap.engine.services.servlets_jsp.server.runtime.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:427)
         at com.sap.engine.services.servlets_jsp.server.runtime.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:358)
         at com.sap.aii.rwb.web.messagemonitoring.viewcontroller.MmDynPage.doProcessBeforeOutput(MmDynPage.java:69)
         at com.sapportals.htmlb.page.PageProcessor.handleRequest(PageProcessor.java:123)
         at com.sapportals.htmlb.page.PageProcessorServlet.handleRequest(PageProcessorServlet.java:62)
         at com.sapportals.htmlb.page.PageProcessorServlet.doGet(PageProcessorServlet.java:29)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.sap.engine.services.servlets_jsp.server.runtime.RequestDispatcherImpl.doWork(RequestDispatcherImpl.java:321)
         at com.sap.engine.services.servlets_jsp.server.runtime.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:377)
         at jsp_FC_Secure1221049856634._jspService(jsp_FC_Secure1221049856634.java:24)
         at com.sap.engine.services.servlets_jsp.server.jsp.JspBase.service(JspBase.java:112)
         at com.sap.engine.services.servlets_jsp.server.servlet.JSPServlet.service(JSPServlet.java:566)
         at com.sap.engine.services.servlets_jsp.server.servlet.JSPServlet.service(JSPServlet.java:190)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
         at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
         at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
         at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
         at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
         at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:102)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)

  • Integration Engine Proxy Runtime Error

    Hello,
    I have  ECC and PI server for my landsacpe. When i ran SXMB_IFR tcode in my ECC server i got the follwing error under Runtime work Bench
    Proxy Runtime - it is shows red color.
    Unable to log on to system ECC120   in language en with user PIRWBUSER  
    Details for Ping Status
    Message: Unable to log on to system ECD210 in language en with user PIRWBUSER
    Stacktrace:
    com.sap.aii.rwb.exceptions.OperationFailedException: Unable to log on to system ECD210 in language en with user PIRWBUSER
    at com.sap.aii.rwb.core.XIAbapRTCComponent.getConnector(XIAbapRTCComponent.java:114)
    at com.sap.aii.rwb.core.XIRTCComponent.ping(XIRTCComponent.java:209)
    at com.sap.aii.rwb.web.componentmonitoring.model.CompTestModel.doPing(CompTestModel.java:581)
    at com.sap.aii.rwb.web.componentmonitoring.viewcontroller.CmDynPage.doPing(CmDynPage.java:425)
    at com.sap.aii.rwb.web.componentmonitoring.viewcontroller.CmDynPage.updateTests(CmDynPage.java:525)
    at com.sap.aii.rwb.web.componentmonitoring.viewcontroller.CmDynPage.selectNode(CmDynPage.java:552)
    at com.sap.aii.rwb.web.componentmonitoring.viewcontroller.CmDynPage.process_treeClick(CmDynPage.java:481)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:324)
    at com.sapportals.htmlb.page.DynPage.doProcessCurrentEvent(DynPage.java:172)
    at com.sapportals.htmlb.page.PageProcessor.handleRequest(PageProcessor.java:115)
    at com.sapportals.htmlb.page.PageProcessorServlet.handleRequest(PageProcessorServlet.java:62)
    at com.sapportals.htmlb.page.PageProcessorServlet.doPost(PageProcessorServlet.java:22)
    at com.sap.aii.rwb.web.componentmonitoring.viewcontroller.CmPageProcessor.doPost(CmPageProcessor.java:35)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
    at com.sap.engine.services.servlets_jsp.server.runtime.RequestDispatcherImpl.doWork(RequestDispatcherImpl.java:321)
    at com.sap.engine.services.servlets_jsp.server.runtime.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:377)
    at jsp_FC_Secure1229621978943._jspService(jsp_FC_Secure1229621978943.java:15)
    at com.sap.engine.services.servlets_jsp.server.jsp.JspBase.service(JspBase.java:112)
    at com.sap.engine.services.servlets_jsp.server.servlet.JSPServlet.service(JSPServlet.java:566)
    at com.sap.engine.services.servlets_jsp.server.servlet.JSPServlet.service(JSPServlet.java:190)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
    at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
    at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
    at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)
    at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
    at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039)
    at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
    at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
    at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
    at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
    at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
    at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
    at java.security.AccessController.doPrivileged(Native Method)
    at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:102)
    at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)
    When i checked  my PIRWBUSER password in abap and poratal level there is no conflicts. Password is correct.
    For integration i have created three RFC also
    LCRSAPRFC,SLDAPIRFC,SAPJ2EE all these RFC are working fine and there is no error.
    Can any one suggest me how to resolve this issue.
    I am waiting for your reply.
    Regards,
    Sankaranarayanan.G
    BASIS CONSULTANT

    Hi Tuhin,
    I have one more problem now. Intially i have configured my PI development portal.But after some days in  my PI server when i ran SXMB_IFR is detecting wrong poral now. I have tried to change from my EXCHANGE Profile under integratrion server parameters i have changed PORT,URL and others.
    but it is not come to effect. can you please help me where do i need to chage the portal?
    I am waiting for your reply.
    Regards,
    Sankar.G

  • Proxy Runtime for Business System not visible in RWB.

    Hi,
    We are running SAP PI 7.10 SP7.
    The current landscape contains currently 2 SAP R/3 application systems and 1 SAP PI systerm that are all registered with the SAP PI SLD.
    There is Business Systems configure for both the Application systems in the SLD from the registration.
    In the ID it was possible to import these Bussiness systems and to use them in scenarios. It is even posible to post messages to both IE on these Business Systems. If tcode SPROXY is executed on both these business systems then it connects to the same ESR. On both business systems I have created a "PIRWBUSER" with the same password and roles as on SAP PI.
    Now my ploblem is that I only see one proxy runtime in the RWB under Integration Engines.
    Please can you assist in this matter?
    Regards
    Willie Hugo

    Hi,
    The problem is solved with patches to the following JAVA components.
    MESSAGING 7.19
    SAP_XIAF7.17
    SAP_XITOOL7.14
    Regards
    Willie Hugo

  • Runtime Workbench Proxy Runtime Configuration

    Hi
    I'm trying to setup the RWB proxy runtime configuration. However our ERP system shows up as an ALE-Logical system and not a Business System in the Configuration tab of the RWB and doesnt appear at all in the Component Monitoring tab so we cant monitor messages from it through the RWB.
    We've tried deleting the business and technical system and re-registering them with RZ70 as well doing a CPA Cache refresh. But that hasnt resolved the issue.
    I have compared this system to another system in the SLD which does show up as a Business System and can be monitored through Component Monitoring. They seem to be exactly the same.
    Is there some kind of setting we are missing on the ERP system?
    Thanks
    Riaz

    Hi Riaz & kesava,
    RWB Proxy runtime setup can be seen from RWB->Component Monitoring under Components section Domain XI->Integration Engine.
    Check the following
    1)Can the SLD be reached?  - RFC destination, ping, getLCR server, read cache, BS defined
    2) Does the Integration Engine know the business system?   - Business system name = BS_100, Role = Application System
    3)Are roles in SXMS_CONF_ITEMS and SLD consistent?   - Role = Application System
    4)Has an Integration Server destination been defined?   Destination 'XIabcd100' to the Integration Server 
    Cheers
    Veera

  • Proxy runtime configuration in PI 7.1

    Hi Experts,
    How to do proxy runtime configuration in PI 7.1?
    Please send any documents or link available for the same.
    Regards,
    Nidhi Kukreja

    Proxy Configuration :
    Create Logical System for ECC & PI both side.
    On PI Configure :
    1. Create RFC Destination from PI to ABAP (Type : H).
    2. Make an entry in SXMB_ADM for Integration server.
    3. Activate Services in SICF.
    On ECC Configure :
    1. Create RFC Destination from ABAP to PI (Type : H).
    2. Make an entry in SXMB_ADM for Application server.

  • Error in Runtime Workbench, Component Monitoring, Proxy Runtime

    Hi,
    I have the following error in the Runtime Workbench, under Component Monitoring->Integration Engines->Proxy Runtime. The error message is Ping Status: “Unable to logon to system xxx in language EN with user XIRWBUSER”. However, I am unable to find out where the account and password are specified in order to correct this. Any help would be appreciated.

    Hi,
    it can be for some system configured on http destination or the sld system configured for this server.
    take a look at tx sxmb_adm for the http destination to discover witch destination is been used. then, on sm59, find the server that is been called for this http destination and check on that server if this user is ok there.
    to check sld, go to tx sld_apicust discover witch is the sld system configured for this server. After log on to sld system and check the user.
    Maybe the user is ok on the destination system, so, check the password on sm59 (if the problem is with an http dest) or sld_apicust (if the problem is the connection to sld).
    regards.
    roberti

  • Proxy Runtime error

    Hello..
         In FILE-XI-BW scenario... I'm getting error in adapter monitoring (integration engine --> Proxy runtime )
    Error is..  "Unable to log on to system D03 (BW system) in language en with user XIRWBUSER...
    Can any one tell me what might be the problem..
    Thanks..

    Hi Padma
    Can you check your configuration Tab in Runtime workbench. If there also you are getting this same error.
    Create a port in your business system using Tcode : we21.
    Also have you set in your proxy System the destination to Integration Server?
    If not:
    Goto sxmb_adm -> Integration Engine configuration -> Role of Business System = Application System with corresponding integration server dest//RFCdestinatio2yourIntegrationServer.
    Best Regards
    - lalit -

  • Proxy Runtime errors in Integration Engines at RWB

    Hi Experts,
    We have configured the point to point configuration scenario in our landscape. I have two ABAP systems exchanges data using PI. I have configured both the ABAP systems as Application Systems and Corresponding Integration server as my PI system.
    In RWB of PI I can see both these systems as proxy run time under Integration Engines, but are in error status.
    Path to the same is Component Monitoring>Components>Integration Engines (here I can my systems as Proxy Runtime BSAB200, Proxy Runtime BSID200).
    When run the test got the below error.
    Can the SLD be reached?  RFC destination LCRSAPRFC does not exist
    Does the Integration Engine know the business system? 
    Are roles in SXMS_CONF_ITEMS and SLD consistent?
    Why do we need to create the RFC destination again when we select the related integration server as PI.
    Can any one throw some light whey are these errors are occured.
    Thanks,
    Chinna

    Can the SLD be reached? RFC destination LCRSAPRFC does not exist
    Reached to SLD but not to exchange profile.
    Does the Integration Engine know the business system?
    Yes.
    Why do we need to create the RFC destination again when we select the related integration server as PI.
    A central SLD scenario involves a central SLD, but not a central exchange profile.
    The exchange profile used is always the one on the Integration Server the
    application system connects to the exchange profile using the SM59 destination
    LCRSAPRFC.
    Regards
    Pothana

  • Java plug-in 1.4.1 proxy configuration issue causes JTextField TAB problems

    I have an applet that has multiple JTextFields in it. I recently updated my Java plug-in to version 1.4.1, and now using TAB to navigate among text fields does not always work when I first bring up a browser and load the applet.
    I've found, however, that if I open the Java Console and hit "p" (reload proxy configuration), and then reload my applet (hit Refresh/Reload on my browser), the Tab key works as expected. I did not have this issue with releases prior to 1.4.1.
    Any clue on how I can ensure proper proxy configuration upon initial instantiation of the browser? I've seen the problem in both IE 6.0 and Netscape 7.0.
    Note that the reloading of the proxy configuration only appears to be necessary once per browser session.

    The navigation isn't working. I click in the first text field to give the initial field focus. I then hit TAB and nothing happens. I have a key listener set up for the ENTER key, and this is also supposed to navigate to the next field via:
    ((JTextField)evt.getSource()).transferFocus();
    To see if there was a problem with my build environment or threads in my application, I came up with the following dummy applet:
    import java.awt.BorderLayout;
    import javax.swing.BoxLayout;
    import javax.swing.JApplet;
    import javax.swing.JPanel;
    import javax.swing.JTextField;
    public class TestApplet extends JApplet {
    public void init() {
    super.init();
    public void start() {
    JPanel myPanel = new JPanel();
    myPanel.setLayout(new BoxLayout(myPanel, BoxLayout.Y_AXIS));
    JTextField textField1 = new JTextField("Text Field 1");
    myPanel.add(textField1);
    JTextField textField2 = new JTextField("Text Field 2");
    myPanel.add(textField2);
    JTextField textField3 = new JTextField("Text Field 3");
    myPanel.add(textField3);
    getContentPane().add(BorderLayout.CENTER, myPanel);
    public void stop() {
    super.stop();
    I then compiled this applet using the following:
    javac TestApplet.java
    I then put together the following HTML file:
    <HTML>
    <HEAD>
    <TITLE>Test Applet</TITLE>
    </HEAD>
    <BODY MARGINWIDTH="0" MARGINHEIGHT="0" BGCOLOR="white">
    <APPLET
    CODE=TestApplet.class
    WIDTH=635
    HEIGHT=500
    ALIGN=left
    VSPACE=10
    HSPACE=10
    >
    </APPLET>
    </BODY>
    </HTML>
    The results are the same. I am not able to navigate using the TAB key until I bring up the Java console and then close it again. I would think that if this was a bug in 1.4.1_01, I would have seen it all over the forums. Any help would be greatly appreciated.

  • Idoc Communication Configurations and Proxy Runtime Configurations for PI

    We have a fresh PI 7.1 system, fresh ECC6 system, and an existing 4.6C system.
    is there any blog/doc with step-by-step instructioins/screenshots for following tasks:
    1. Configuring Abap proxy runtime between ECC6 and PI 7.1 Systems, for using sproxy from ECC6.
    2. Configuring for IDOC communication between ECC6 and PI 7.1
    3. Configuring for IDOC communication between 4.6C system and PI 7.1
    It involves creating of sm59 rfc destination creations, usage of idoc related transactions on PI system and the other system.. I searched on sdn/forum, but it seems to be addressing specific issues faced.
    Pls suggest any step-by-step instructions docs/blogs available.
    thanks in advance.
    Madhu.

    Madhu,
    Refer the links below:
    1. /people/vijaya.kumari2/blog/2006/01/26/how-do-you-activate-abap-proxies
    2& 3 :
    https://wiki.sdn.sap.com/wiki/display/XI/SAPR3%28Idocs%29ToXI--Steps+Summarized
    http://www.riyaz.net/blog/xipi-settings-in-r3-partner-system-to-receive-idocs/
    /people/swaroopa.vishwanath/blog/2007/01/22/ale-configuration-for-pushing-idocs-from-sap-to-xi
    https://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/877c0d53-0801-0010-3bb0-e38d5ecd352c&overridelayout=true
    http://www.riyaz.net/blog/beginners-guide-to-ale-and-idocs-a-step-by-step-approach/
    Also, I  think u hv just started learning XI ..so following link might help:
    http://wiki.sdn.sap.com/wiki/display/NWTech/QAforPI-Onestopforall%28Part-1%29

  • ABAP Proxy runtime is showing status as red

    We have ABAP Proxy runtime for four different ABAP systems. Except one all the other three proxies are showing the status as red. Could you please help me with this regard - Points guaranteed

    Hey,
    Go to <b>SM59 -
    > R/3 connection to ABAP Systems -
    > INTEGRATION_DIRECTORY_HMI</b>
    Now press the Connect Test button, and chek it every thing is ok. You should not get any error!!.
    If above one is ok in all three systems, then second option is
    Go to tcode <b>SICF -
    > default_host --->sap -
    >xi</b> check if all the services are active (if active, will be in pure black color), if not active then activate them, may be you will require authorizations for this work.
    Try the above solution and it will work.
    Regards,
    Sarvesh
    ****Reward points if it helped you.

Maybe you are looking for

  • Multiple display management issues

    I have a projector I use daily for watching stuff. It requires the room to be dark, the darker the better. My desktop computer is placed in the same room, and I would really prefer that its monitor be off when I use the projector. For VLC I can just

  • File sharing in Bridge with Keywords

    We seem to be having trouble getting the Keywording to come up on the 2nd shared machine, listed out in their stair-stepped categories like we have put them into to begin with... The 2nd new imac only seems to give a list of keywords simply sorted in

  • Is there a way to see a breakdown of the largest file on your mac ?

    HI Guys In a bit of a bind I have used up at 60GB on my drive and for the life of me I dont know what I have on there that is so large and takeing up so much space. Is there a way that I can see just what is on there and the largest to smallest files

  • What Cable To i need to connect to Projector?

    I have a macbook and was wondering what cable i need in order to be able to hook my macbook up to my projector/computers at my college. at my college, in every class there is a podium with a computer and a few cable. these 2 cables are there, which i

  • Wireless Keyboard + Apple Cider = Oops!

    Being the dolt that I am, I accidentally spilled apple cider on my Apple Bluetooth Keyboard. It still works, except I think the "Control" button is always activated because whenever I left click on something, it acts as a secondary click. (Very frust