Skip to Content

Archived discussions are read-only. Learn more about SAP Q&A

Trouble with SLD ping.

Hello!

I'm trying to setup a local SLD in standalone J2EE instance of SAP Web AS 7.0.

I've created required roles, assigned actoins to them, created SLDDSUSER and assign LcrWriter to him. I can login to the http://localhost:50000/sld under SLDDSUSER, but in SLD logs I've found following error:

#41 04/08/2010 18:07:23.48 [SAPEngine_Application_Thread[impl:3]_1] INFO com.sap.sld.api.builder.app.DefineHostedSystem: Communication exception in SLD ping (HTTP 403 = FORBIDDEN).
Thrown: 
com.sap.sld.api.wbem.exception.CIMCommunicationException: CIM_ERR_FAILED: HTTP response code: 403 Forbidden
at com.sap.sld.api.wbem.client.WBEMHttpRequestSender.newCommunicationException(WBEMHttpRequestSender.java:414)
at com.sap.sld.api.wbem.client.WBEMHttpRequestSender.processResponse(WBEMHttpRequestSender.java:323)
at com.sap.sld.api.wbem.client.WBEMHttpRequestSender.send(WBEMHttpRequestSender.java:142)
at com.sap.sld.api.wbem.client.WBEMRemoteClient.send(WBEMRemoteClient.java:720)
at com.sap.sld.api.wbem.client.WBEMRemoteClient.send(WBEMRemoteClient.java:694)
at com.sap.sld.api.wbem.client.WBEMRemoteClient.send(WBEMRemoteClient.java:638)
at com.sap.sld.api.wbem.client.WBEMRemoteClient.getClassImpl(WBEMRemoteClient.java:100)
at com.sap.sld.api.wbem.client.WBEMClient.getClass(WBEMClient.java:292)
at com.sap.sld.api.wbem.client.WBEMClient.exists(WBEMClient.java:2447)
at com.sap.sld.api.wbem.client.WBEMClientUtil.checkServer(WBEMClientUtil.java:132)
at com.sap.sld.api.builder.app.DefineHostedSystem.registerJ2EEHostedSystemAtSLD(DefineHostedSystem.java:105)
at com.sap.sld.api.builder.app.DefineHostedSystem.registerHostedSLDSystem(DefineHostedSystem.java:63)
at com.sap.lcr.start.StartDirector.registerSLDatSLD(StartDirector.java:1075)
at com.sap.lcr.start.StartDirector.constructPermanentLcrInstances(StartDirector.java:998)
at com.sap.lcr.start.StartDirector.reconstructPermanentLcrInstances(StartDirector.java:1221)
at com.sap.lcr.webui.CimIO.startCIMServer(CimIO.java:576)
at com.sap.lcr.webui.Admin.actionStartStop(Admin.java:885)
at com.sap.lcr.webui.Admin.doGet(Admin.java:169)
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.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)

How to resolve this issue?

regards, Lev

Former Member
Former Member replied

Hi Lev

Its not completely clear what events cause this error - the way it is described in your thread is that the error occurs when/after logging into SLD UI via SLDDSUSER either directly or by viewing the logs --> In terms of logging into SLD UI - the SLDDSUSER is an "RFC" user for use with SLD JCOs or HTTP connections - not strictly used for ldirect og on to the UI - which is normally done with a SLD administrator user with LCR all - similiarly an Admin user must be used to configured rights to the SLD

Assuming it is perhaps an error from a data supplier trying to register using SLDDSUSER - I would recommend to check

the rights are mapped to the role, the role is mapped to the group and the group is mapped to the user correctly and that

"Assign application roles to user groups" is used for part of this process. If not Ideally scrap the current SLDDSUSER and the associated roles and group/rights assignments (as long as the setup is not productively or successfully used by any other data suppliers or users at the moment) and redo the steps in chapter "Configuring SLD Security Roles" of the SLD Post Installation guide available from System Landscape Directory (SLD)

Best wishes

Stuart

0 View this answer in context

Helpful Answer

by
Not what you were looking for? View more on this topic or Ask a question