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

Similar Messages

  • Runtime Workbench - Proxy Runtime

    In the Runtime Workbench, I got an error status in the component "Proxy Runtime".
    Result of Self-Test:
        Can the SLD be reached?   (successful)
        Does the Integration Engine know the business system? (error)
        Are roles in SXMS_CONF_ITEMS and SLD consistent? (error)
    Details:
        Tested: RFC destination, ping, getLCR server, read cache, BS defined
        Function LCR_GET_OWN_BUSINESS_SYSTEM failed (return code = 1)
        No role for business system defined in System Landscape
    Can anyone tell me how to solve this problem?

    Hi,
    This basically means that your back end system where you generate your proxy, was NOT registered in SLD properly.
    Proceed as follows in SLD:
    1. If your system has not been registered as a technical system, you will have to register it using transaction RZ70 (Prior to that, you also need to make sure the RFC destination SLD_UC has been properly configured to point to your SLD program registered in PI gateway )
    2. Create your business system referring to the technical system above, pointing to the client where you want to generate your proxy.
    Hope it helps,
    Lim...

  • Difference between WS runtime and proxy runtime

    HI,
    I'm new to PI/XI. 1) Could anyone please explain about the real difference between WS runtime and Proxy runtime?
    2) How to configure the scenario's for WS communication and proxy communication?
    3) what is the adapter type we should use for this in ID?
    4) How to convert the proxy to webservice? etc.
    Thanks in adavnce
    Regards,
    Baskaran K

    I'm new to PI/XI.
    I would suggest that you first make use of the Search facility of SDN. If I am not wrong all your questions will be answered by a Search.
    Regards,
    Abhishek.

  • 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

  • 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 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/Configuration/Save Configuration

    Hi all,
    In Runtime WorkBench, when i choose "Configuration" tab, and after choose "Save Configuration", i get an error message as below:
    "Configuration saved RFC ping failed for the following RFC destinations (created upon saving) in the system DEV800: PMIDEV800, PMITST910"
    In this case, my XI system has one Integration Server: DEV800 and one Business System TST910. Two RFC (Process Monitoring Infrastructure RFC) created: PMIDEV800, PMITST910 can't not function correctly. And i don't know how i can correct this error.
    Anyone can please help me to correct this error?
    Thanks a lot in advance,
    Vinh Vo

    hi vinh vo,
    do chk this link
    Installing and Configuring SAP Interactive Forms by Adobe for the SAP NetWeaver Composition Environment
    Thanx
    Sampath

  • 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

  • Not able to use Alert Configuration/Alert Inbox in the Runtime Workbench

    Hi Experts,
                      I have installed PI 7.1 on my system. I'm not able to use the Alert Configuration/Alert Inbox in the Runtime WorkBench. It is asking for a logon and the logon which i used for ABAP & Java Stack is not working.
    e.g., For ABAP Stack, the User Id is: "sapuser" & For Java Stack, the User Id is: "pisuper". But, both these User Id's are not working for the Alert Configuration/Alert Inbox in the RWB.
    Can someone pls suggest me, how to proceed?
    Br
    G@nesh

    Hi Preethi,
    Can u pls help me, how to check whether the relevant roles are assigned to this user i.e., pisuper for the JAVA stack in the UME or not? i even tried to use Alert Configuration/Alert Inbox with the User ID: ddic & j2ee_admin, but it too didn't work...
    I would like to use Alert Configuration/Alert Inbox with my User Id: pisuper, which i'm using to logon to the JAVA stack
    while exploring, i logged on to the useradmin page i.e., http://p71:58800/useradmin with the User Id: j2ee_admin... If this is correct, can u pls let me know how can i add the necessary roles to my User Id: pisuper so that i can use Alert Configuration/Alert Inbox with my User Id: pisuper
    Br
    G@nesh

  • Proxy Runtime configuration in Quality

    Dear All,
    I am sending data from XI to BI through server proxy.
    We have link between ERP quality and XI development. Do i have to do Proxy runtime configuration in quality server directly. Do I need to do it manually or transport from development?
    Regards.
    SM.

    > We have link between ERP quality and XI development. Do i have to do Proxy runtime configuration in quality server directly.
    > Do I need to do it manually or transport from development?
    You have to do this manually.

  • Dynamic alert configuration in Runtime Workbench in XI

    Hi All,
    i have a scenario in which i have 3 input flat files to a BPM process.........
    my BPM waits for all the 3 files in a fork and on receiving all the 3 files, it transforms them to output message...........
    i have put a wait condition for 2 minutes so that if in 2 minutes, all the 3 files are not got then an alert is to be generated and then i cancel the BPM process....
    i have made a simple alert...........
    i want a dynamic alert - meaning a alert which will specify out of the 3 files which file did not came. For example, suppose the 3 files are f1, f2, f3...... if f1 and f3 came but f2 did not came, i want a alert mail in alert inbox as "File f2 did not came".....if only f3 came, then i want a alert mail as "File f1,f2 did not came"........
    <b>Can anybody suggest how to generate alerts in alert inbox in runtime workbench dynamically in this situation.....</b>
    Thanks,
    Rajeev Gupta

    Hi All,
    in transaction ALRTCATDEF, i have specified dynamic text for my alert category...........
    but when i am using this alert category in my BPM control step, then the alert message which i am giving is not coming in the alert mail in alert inbox but it gives the common message in long text "Error in PWC" which i gave in long text while defining the alert category......
    <b>So can anybody suggest me why my BPM alert message is not coming in the alert generated by BPM control step in the alert inbox of runtime workbench.</b>
    Thanks,
    Rajeev Gupta

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

  • Problem with Runtime Workbench and with sending data from XI to SLD

    Hello<br>
    <br>
    Could I have a little help, a hint in the two following topics:<br>
    <br>
    1. I run Runtime Workbench -> Component Monitoring -> Display All and I get this error:<br>
    <br>
    Error during communication with System Landscape Directory: User credentials are invalid or user is denied access<br>
    <br>
    In filesystem log I can find like this:<br>
    <br>
    XIRWB.com.sap.aii.mdt.frames.jsp_error [SAPEngine_Application_Thread[impl:3]_40] Fatal: Error during communication with System Landscape Directory: User credentials are invalid or user is denied access<br>
    Thrown:<br>
    MESSAGE ID: com.sap.aii.rwb.agent.server.rb_LCRAgent.landscapeCommunicationError<br>
    com.sap.aii.rwb.exceptions.BuildLandscapeException: Error during communication with System Landscape Directory: User <br>credentials are invalid or user is denied access
            at com.sap.aii.rwb.agent.server.SLDAgentBean.convertException(SLDAgentBean.java:1472)
            at com.sap.aii.rwb.agent.server.SLDAgentBean.buildSLD(SLDAgentBean.java:773)
            at com.sap.aii.rwb.agent.server.SLDAgentBean.provideSld(SLDAgentBean.java:269)
            at com.sap.aii.rwb.agent.server.SLDAgentBean.getXIDomain(SLDAgentBean.java:711)
            at com.sap.aii.rwb.agent.api.SLDAgentObjectImpl0_0.getXIDomain(SLDAgentObjectImpl0_0.java:375)
            at com.sap.aii.rwb.agent.api.SLDAgent_Stub.getXIDomain(SLDAgent_Stub.java:436)
            at com.sap.aii.rwb.agent.client.EJBAgent.getXIDomain(EJBAgent.java:255)
            at com.sap.aii.rwb.util.web.model.AppMainModel.getSelectedDomain(AppMainModel.java:138)
            at com.sap.aii.rwb.util.web.model.DomainRep.build(DomainRep.java:121)
            at com.sap.aii.rwb.web.componentmonitoring.model.ObjectIdentificationTree.getComponentTree(ObjectIdentificationTree.java:117)<br>
            at jsp_component_monitoring1321125174985._jspService(jsp_component_monitoring1321125174985.java:217)
            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:544)
            at com.sap.engine.services.servlets_jsp.server.servlet.JSPServlet.service(JSPServlet.java:186)
            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 com.sap.aii.rwb.web.componentmonitoring.viewcontroller.CmPageProcessor.doGet(CmPageProcessor.java:27)
            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_Secure1321125169379._jspService(jsp_FC_Secure1321125169379.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:544)
            at com.sap.engine.services.servlets_jsp.server.servlet.JSPServlet.service(JSPServlet.java:186)
            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:387)
            at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:365)
            at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:944)
            at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:266)
            at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
            at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:160)
            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(AccessController.java:219)
            at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
            at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)<br>
    Root cause:<br>
    com.sap.lcr.api.cimclient.UnauthorizedUserException: User credentials are invalid or user is denied access<br>
            at com.sap.lcr.api.cimclient.HttpRequestSender.processResponse(HttpRequestSender.java:577)
            at com.sap.lcr.api.cimclient.HttpRequestSender.send(HttpRequestSender.java:341)
            at com.sap.lcr.api.cimclient.CIMOMClient.send(CIMOMClient.java:280)
            at com.sap.lcr.api.cimclient.CIMOMClient.performBatchOperation(CIMOMClient.java:1251)
            at com.sap.lcr.api.cimclient.CIMClient.performBatchOperation(CIMClient.java:2268)
            at com.sap.aii.utilxi.sld.MRSldProxy.stage1(MRSldProxy.java:989)
            at com.sap.aii.utilxi.sld.MRSldProxy.loadComponents(MRSldProxy.java:918)
            at com.sap.aii.utilxi.sld.MRSldProxy.loadSld(MRSldProxy.java:907)
            at com.sap.aii.utilxi.sld.SubSystemFactory.createSldFromSld(SubSystemFactory.java:373)
            at com.sap.aii.utilxi.sld.SubSystemFactory.createSldFromSld(SubSystemFactory.java:434)
            at com.sap.aii.rwb.agent.server.SLDAgentBean.buildSLD(SLDAgentBean.java:764)
            at com.sap.aii.rwb.agent.server.SLDAgentBean.provideSld(SLDAgentBean.java:269)
            at com.sap.aii.rwb.agent.server.SLDAgentBean.getXIDomain(SLDAgentBean.java:711)
            at com.sap.aii.rwb.agent.api.SLDAgentObjectImpl0_0.getXIDomain(SLDAgentObjectImpl0_0.java:375)
            at com.sap.aii.rwb.agent.api.SLDAgent_Stub.getXIDomain(SLDAgent_Stub.java:436)
            at com.sap.aii.rwb.agent.client.EJBAgent.getXIDomain(EJBAgent.java:255)
            at com.sap.aii.rwb.util.web.model.AppMainModel.getSelectedDomain(AppMainModel.java:138)
            at com.sap.aii.rwb.util.web.model.DomainRep.build(DomainRep.java:121)
            at <br>com.sap.aii.rwb.web.componentmonitoring.model.ObjectIdentificationTree.getComponentTree(ObjectIdentificationTree.java:117)
            at jsp_component_monitoring1321125174985._jspService(jsp_component_monitoring1321125174985.java:217)
            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:544)
            at com.sap.engine.services.servlets_jsp.server.servlet.JSPServlet.service(JSPServlet.java:186)
            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 com.sap.aii.rwb.web.componentmonitoring.viewcontroller.CmPageProcessor.doGet(CmPageProcessor.java:27)
            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_Secure1321125169379._jspService(jsp_FC_Secure1321125169379.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:544)
            at com.sap.engine.services.servlets_jsp.server.servlet.JSPServlet.service(JSPServlet.java:186)
            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:387)
            at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:365)
            at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:944)
            at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:266)
            at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
            at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:160)
            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(AccessController.java:219)
            at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
            at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
    <br>
    <br>
    <br>
    I don't know what is wrong.<br>
    I have configured:<br>
    - SLDCHECK work properly,<br>
    - none of the users PI* type not lock,<br>
    - password to the PI* users in exchangeProfile entered correctly,<br>
    - In VA in the JCo RFC Provider I have properly configure: AI_RUNTIME_JCOSERVER, LCRSAPRFC, SAPSLDAPI_SID - from the ABAP I can connect to this programs ID<br>
    - In VA in SLD Data Supplier I have properly configure bookmarks HTTP Settings and CIM Client Generation Settings. CIMClient Test is OK<br>
    <br>
    I do not know what else I can see, what else I have properly configured ... I looked at the notes:: 936093 jak i 721548...<br>
    <br>
    <br>
    2. I can't send data from XI to SLD, ie makes me a system definition in Web As Abap and Web as Java but nothing appear to me in Exchange Infrastructure. Exchange Infrastructure is empty - what is wrong??<br>
    I carried out the recommendation by 764176 and 1031321 notes<br>
    <br>
    I restart below applications (no effect)...<br>
    com.sap.xi.directory (Integration Builder/Configuration)<br>
    com.sap.aii.af.app (Adapter Engine)<br>
    com.sap.xi.rwb (Runtime Workbench)<br>
    com.sap.xi.repository (Integration Builder/Design)<br>
    <br>
    Can I ask for help and guidance in these topics?<br>
    <br>
    Regards<br>
    RP<br>

    I increased logging in the NWA (Configuration -> Log Configuration) - and increased the some things here to log ALL. So that from the NWA (Monitoring -> Logs and Traces) I see a little more information (but does not follow that with which the user is a problem).<br>
    <br>
    Here are some interesting logs ...<br>
    I was most rash or irritation of those that say about the lack of credentials u2013 I must use Viusal Administrator and set good service ...<br>
    <br>
    What do I have done:<br>
    In the Visual Administrator -> Cluster -> Server -> Services -> SLD Data Supplier<br>
    I have set in the HTTP Settings tab the host and port SLD, the user name and password is also entered as it is in the SLD. To be sure, already have set for the user entered here such roles as:<br>
    SAP_SLD_ADMINISTRATOR<br>
    SAP_SLD_CONFIGURATOR<br>
    SAP_SLD_DEVELOPER<br>
    SAP_SLD_GUEST<br>
    SAP_SLD_ORGANIZER<br>
    Maybe we are talking in this place about a different user?<br>
    <br>
    Similarly, when it comes to tab CIM Client Generation Settings - here's all the same thing done. CIMClient test shows that everything is OK.<br>
    When I click the button: This trigger the transfer of data to the SLD gets the message that everything was shipped correctly. Indeed, I received an instance of JAVA in SLD<br>
    Also clicked on this icon: Assign application roles to user group - got information that everything is attached properly.<br>
    <br>
    By ABAP side, the connections: INTEGRATION_DIRECTORY_HMI, SAPSLDAPI, LCRSAPRFC, AI_RUNTIME_JCOSERVER and AI_DIRECTORY_JCOSERVER work correctly, ie I can perform the test - which means that programs ID are properly positioned in JCO Provider in VA.<br>
    <br>
    Puzzling is this message:<br>
    The SLD data is inconsistent.<br>
    <br>
    Strange also that the message (from the ABAP everything is available in SMGW no errors):<br>
    Connect to SAP gateway failed<br>
    <br>
    And what is this error:<br>
    <br>
    could not sync ExchangeProfile: <br>
    Thrown:<br>
    com.sap.rprof.dbprofiles.DBException: Connect to SAP gateway failed<br>
    Connect_PM  TYPE=A ASHOST=saptest2 SYSNR=60 GWHOST=saptest2 GWSERV=sapgw60 PCS=1<br>
    <br>
    LOCATION    CPIC (TCP/IP) on local host with Unicode<br>
    ERROR       partner 'saptest2:sapgw60' not reached<br>
    TIME        Thu Feb 23 07:28:07 201<br>
    RELEASE     700<br>
    COMPONENT   NI (network interface)<br>
    VERSION     38<br>
    RC          -10<br>
    MODULE      nixxi.cpp<br>
    LINE        2513<br>
    DETAIL      NiPConnect<br>
    SYSTEM CALL connect<br>
    ERRNO       79<br>
    ERRNO TEXT  A remote host refused an attempted connect operation.<br>
    COUNTER     2<br>
    <br>
    <br>
    Below is a list of some interesting logs ...<br>
    <br>
    ###########<br>
    <br>
    Insufficient permissions for getting SLD access information. You can add permissions for your application via the SLD service in the 'Visual Administrator'.<br>
    <br>
    #############<br>
    <br>
    SLD is not accessible. Check SLD Data Supplier service settings.<br>
    <br>
    ###########<br>
    <br>
    "Warning","2012-02-22","07:53:50:986","Data get on com.sap.sldserv.data.GetSAPBCCentralServiceInstance class processing failed. htThe SLD data is inconsistent. This is an internal processing problem.","/System/Server/SLDService","com.sap.sldserv.DataCollector","n/a","saptest2","Server 0 60_36694",<br>
    <br>
    #########<br>
    <br>
    com.sap.lcr.api.cimclient.UnauthorizedUserException: User credentials are invalid or user is denied access<br>
    <br>
    ################<br>
    <br>
    Full Message Text
    CPA Cache not updated with directory data, due to: Couldn't open Directory URL (http://saptest2.unx.era.pl:56000/dir/hmi_cache_refresh_service/ext?method=CacheRefresh&mode=C&consumer=af.xit.saptest2), due to: HTTP 503: Service Unavailable
    <br>
    ##################<br>
    <br>
    Full Message Text <br>
    <br>
    could not sync ExchangeProfile: <br>
    Thrown:<br>
    com.sap.rprof.dbprofiles.DBException: Connect to SAP gateway failed<br>
    Connect_PM  TYPE=A ASHOST=saptest2 SYSNR=60 GWHOST=saptest2 GWSERV=sapgw60 PCS=1<br>
    <br>
    LOCATION    CPIC (TCP/IP) on local host with Unicode<br>
    ERROR       partner 'saptest2:sapgw60' not reached<br>
    TIME        Thu Feb 23 07:28:07 201<br>
    RELEASE     700<br>
    COMPONENT   NI (network interface)<br>
    VERSION     38<br>
    RC          -10<br>
    MODULE      nixxi.cpp<br>
    LINE        2513<br>
    DETAIL      NiPConnect<br>
    SYSTEM CALL connect<br>
    ERRNO       79<br>
    ERRNO TEXT  A remote host refused an attempted connect operation.<br>
    COUNTER     2<br>
    <br>
    Connect_PM  TYPE=A ASHOST=saptest2 SYSNR=60 GWHOST=saptest2 GWSERV=sapgw60 PCS=1<br>
    <br>
    LOCATION    CPIC (TCP/IP) on local host with Unicode<br>
    ERROR       partner 'saptest2:sapgw60' not reached<br>
    TIME        Thu Feb 23 07:28:07 201<br>
    RELEASE     700<br>
    COMPONENT   NI (network interface)<br>
    VERSION     38<br>
    RC          -10<br>
    MODULE      nixxi.cpp<br>
    LINE        2513<br>
    DETAIL      NiPConnect<br>
    SYSTEM CALL connect<br>
    ERRNO       79<br>
    ERRNO TEXT  A remote host refused an attempted connect operation.<br>
    COUNTER     2<br>
    <br>
    at com.sap.mw.jco.MiddlewareJRfc.generateJCoException(MiddlewareJRfc.java:457)<br>
    at com.sap.mw.jco.MiddlewareJRfc$Client.connect(MiddlewareJRfc.java:1015)<br>
    at com.sap.mw.jco.JCO$Client.connect(JCO.java:3238)<br>
    at com.sap.rprof.dbprofiles.DBProfiles.getProfile(DBProfiles.java:101)<br>
    at com.sap.rprof.dbprofiles.RemoteProfile.readRemoteProfileFromMedia(RemoteProfile.java:1288)<br>
    at com.sap.rprof.dbprofiles.RemoteProfile.getRemoteProfileFromFactory(RemoteProfile.java:195)<br>
    at com.sap.aii.utilxi.prop.rprof.ExchangeProfilePropertySource.readProfile(ExchangeProfilePropertySource.java:177)<br>
    at com.sap.aii.utilxi.prop.rprof.ExchangeProfilePropertySource.sync(ExchangeProfilePropertySource.java:165)<br>
    at com.sap.aii.utilxi.misc.api.AIIProperties.sync(AIIProperties.java:582)<br>
    at com.sap.aii.af.service.sld.SLDAccess.syncExchangeProfile(SLDAccess.java:43)<br>
    at com.sap.aii.adapter.xi.ms.SLDReader.fire(SLDReader.java:52)<br>
    at com.sap.aii.adapter.xi.ms.SLDReader.run(SLDReader.java:167)<br>
    at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)<br>
    at java.security.AccessController.doPrivileged(AccessController.java:219)<br>
    at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)<br>
    at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)<br>
    <br>
    ##############<br>
    <br>
    Full Message Text <br>
    <br>
    Import of software component version list from component repository  failed<br>
    Thrown:<br>
    com.sap.lcr.api.cimclient.LcrException: User credentials are invalid or user is denied access<br>
    at com.sap.lcr.api.cimclient.HttpRequestSender.processResponse(HttpRequestSender.java:577)<br>
    at com.sap.lcr.api.cimclient.HttpRequestSender.send(HttpRequestSender.java:341)<br>
    at com.sap.lcr.api.cimclient.CIMOMClient.sendImpl(CIMOMClient.java:198)<br>
    at com.sap.lcr.api.cimclient.CIMOMClient.send(CIMOMClient.java:146)<br>
    at com.sap.lcr.api.cimclient.CIMOMClient.enumerateInstancesImpl(CIMOMClient.java:443)<br>
    at com.sap.lcr.api.cimclient.CIMOMClient.enumerateInstances(CIMOMClient.java:747)<br>
    at com.sap.lcr.api.cimclient.CIMClient.enumerateInstances(CIMClient.java:980)<br>
    at com.sap.lcr.api.sapmodel.JavaCIMObjectAccessor.enumerateInstances(JavaCIMObjectAccessor.java:211)<br>
    at com.sap.lcr.api.sapmodel.SAP_SoftwareComponentAccessor.enumerateInstances(SAP_SoftwareComponentAccessor.java:204)<br>
    at com.sap.lcr.api.sapmodel.SAP_SoftwareComponentAccessor.enumerateSAP_SoftwareComponentInstances(SAP_SoftwareComponentAccessor.java:239)<br>
    at com.sap.aii.ibrep.server.sldaccess.interfaces.CRAccess.getSwcLinks(CRAccess.java:82)<br>
    at com.sap.aii.ibrep.server.extobjects.SwcAccessor.getEoLinks(SwcAccessor.java:59)<br>
    at com.sap.aii.ib.server.extobjects.EOAServiceImpl.getEoLinks(EOAServiceImpl.java:75)<br>
    at com.sap.aii.ib.sbeans.extobjects.EOAServiceBean.getEoLinks(EOAServiceBean.java:66)<br>
    at com.sap.aii.ib.sbeans.extobjects.EOAServiceRemoteObjectImpl1_0.getEoLinks(EOAServiceRemoteObjectImpl1_0.java:527)<br>
    at com.sap.aii.ib.sbeans.extobjects.EOAServiceRemoteObjectImpl1_0p4_Skel.dispatch(EOAServiceRemoteObjectImpl1_0p4_Skel.java:232)<br>
    at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:320)<br>
    at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:198)<br>
    at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:129)<br>
    at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)<br>
    at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)<br>
    at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)<br>
    at java.security.AccessController.doPrivileged(AccessController.java:219)<br>
    at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)<br>
    at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)<br>
    <br>
    ##############<br>
    <br>
    Full Message Text <br>
    <br>
    An exception was thrown in the UME/ABAP user management connector. Message: Connect to SAP gateway failed<br>
    Connect_PM  TYPE=A ASHOST=localhost SYSNR=60 GWHOST=localhost GWSERV=sapgw60 PCS=1<br>
    <br>
    LOCATION    CPIC (TCP/IP) on local host with Unicode<br>
    ERROR       partner '127.0.0.1:sapgw60' not reached<br>
    TIME        Thu Feb 23 07:28:06 201<br>
    RELEASE     700<br>
    COMPONENT   NI (network interface)<br>
    VERSION     38<br>
    RC          -10<br>
    MODULE      nixxi.cpp<br>
    LINE        2513<br>
    DETAIL      NiPConnect<br>
    SYSTEM CALL connect<br>
    ERRNO       79<br>
    ERRNO TEXT  A remote host refused an attempted connect operation.<br>
    COUNTER     16<br>
    <br>

  • 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

  • Messages on Holding at Message Monitoring under Runtime Workbench

    Hello Colleagues,
    we have currently the problem that a lot of messages for some interfaces are in status Holding under Message Monitoring at Runtime Workbench for PI 7.1.
    I'm not able to resend the messages with status Holding as well as change status to cancel.
    Quality of Service for the Interfaces are Exactly Once in Order.
    I assume an error message blocks the queue and due to the fact we have Exactly Once in Order configured all following messages be in status Holding.
    Is my assumption right?
    But, I am not abel to find any messages in status error with blocks the queue!
    How can I solve that issue?
    Many thanks in advance!
    Jochen

    I assume an error message blocks the queue and due to the fact we have Exactly Once in Order
    configured all following messages be in status Holding.
    AE should have least number of EOIO messages at a given instance...otherwise Holding is what you get.....and holding is common with EOIO....so see if you can chagne the QoS of some messages to EO
    But, I am not abel to find any messages in status error with blocks the queue!
    Never you will get an error in SXMB_MONI....or the queue blocked....
    When your message goes out of IE...the corresposding message entry is marked with chequered flag...observe in MONI you will see this....however in AE the message can fail if not able to send to the target system....
    For some more understanding refer my answer in this thread:
    Re: Restarting Error's in SXMB_MONI
    Regards,
    Abhishek.

Maybe you are looking for