Unable to log on to Business System with user XIRWBUSER

[Former Member]

Hi ppl,

I am doing proxy to proxy scenario.My client proxy is working fine.It fetches the data to XI.when i execute the scenario, i am getting successfully processed message flag for the scenario in SXMB_MONI.

But my server proxy code is not triggered.

I went into the XI runtime workbench,where i happen to see that proxy runtime for my Business system is in Red flag.

when i happen to see the detail of the error it shows ,

Message: Unable to log on to system XX_030 in language en with user XIRWBUSER

Stacktrace:

com.sap.aii.rwb.exceptions.OperationFailedException: Unable to log on to system XX_030 in language en with user XIRWBUSER

at com.sap.aii.rwb.core.XIAbapRTCComponent.getConnector(XIAbapRTCComponent.java:112)

at com.sap.aii.rwb.core.XIRTCComponent.ping(XIRTCComponent.java:199)

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:298)

at com.sap.aii.rwb.web.componentmonitoring.viewcontroller.CmDynPage.updateTests(CmDynPage.java:372)

at com.sap.aii.rwb.web.componentmonitoring.viewcontroller.CmDynPage.selectNode(CmDynPage.java:388)

at com.sap.aii.rwb.web.componentmonitoring.viewcontroller.CmDynPage.process_treeClick(CmDynPage.java:339)

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:295)

at com.sap.engine.services.servlets_jsp.server.runtime.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:351)

at jsp_FC_Secure1136438726100._jspService(jsp_FC_Secure1136438726100.java:26)

at com.sap.engine.services.servlets_jsp.server.servlet.JSPServlet.service(JSPServlet.java:538)

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:390)

at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:264)

at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:347)

at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:325)

at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:887)

at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:241)

at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)

at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148)

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:95)

at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:160)

waiting for the solution ..

regards,

Sujata

[Former Member · Accepted solution]

Hi Sujatha,

The Communication Channel that you have defined, pointing to the Business System should have the appropriate user in that particular system(receiving the inbound proxy)...Is the user XIRWBUSER the username given in the comm. channel ? Then the XIRWBUSER need to be created in the Business System.

Pls check the blog by Siva..

/people/siva.maranani/blog/2005/04/03/abap-server-proxies

If you have already done this...Pls igonre this...

Thanks,

Renjith

[Former Member]

Hi Sujatha,

regarding the server proxy code: did you have a look at sxmb_moni of the SAP system where the proxy code is not triggered? Does the message show up there and if yes, probably with a green flag?

If so, you need to register the queues on your application system via sxmb_admin.

best regards

Christine

[Former Member]

hi renjith,

i havent given XIRWDUSER name in my communication channel.instead i have given the user name which has the authorisation to enter into the system (where Business System is defined).

i dnt have password for xisuper as specified in shiva weblog.

Am i doing any mistake in that user id part..

regards

Sujata

[Former Member]

Hi Sujata,

Now that i look again, the error that you are getting is not related to the scenario at all. The error is when the runtime workbench tries to ping the proxy runtime of the business system. I donot think this has anything to do with your scenario.

About your scenario, in SXMB_MONI...Is the determined receiver correct? and what is the status on the outbound side ? you said that it had a processed successfully status on the inbiound side of it.

Thanks,

Renjith.

[Former Member]

Hi Sujatha,

XI always uses XIRWBUSER to connect to the proxy runtime of application systems. Therefore this user has to be created in all SAP systems where you have a proxy runtime which you want to monitor from RWB Component MOnitoring.

The installation guide states:

<i>8.4 Creating a User for the Runtime Workbench

The Runtime Workbench monitors business systems by using the default user XIRWBUSER with the role SAP_XI_RWB_SERV_USER. Therefore, create a service user with this role in your business system.</i>

Best regards

Christine