Problems while implementing ESS on EP 6.0

[Former Member]

Hello all,

I'm trying to implement the ESS 60.2 business package on EP 6.0 but, when trying to access any iView from the package, another logon screen appears in it and no registered SAP user seem to be able to surpass it.

Has anyone ever had this kind of issue?

We're also using ECC 5.0 and the SLD is centralized on the XI system.

Thanks in advance,

Simone

[Former Member · Accepted solution]

Simone,

Kindly check the blog;

There is a link at the bottom for installing ESS.

James

[Former Member]

Hi James,

Thanks for the tip on the Weblog but, unfortunately, i pretty much followed those same steps and it still doesn't work. i awarded you some points tho.

And hello Siddhartha,

Thanks for the reply.

i did perform user mapping as well as the ticket option for some tests. both ended up with the logon page appearing inside the iview and no user being authenticated in it (tried with all possible portal and ECC users i could).

i went through the WebDynpro Content Administrator again, made some changes and now, when clicking in an iview, i get the following error:

java.lang.NoClassDefFoundError: com/sap/tc/webdynpro/progmodel/api/IWDEventId

at java.lang.Class.getDeclaredConstructors0(Native Method)

at java.lang.Class.privateGetDeclaredConstructors(Class.java:1618)

at java.lang.Class.getConstructors(Class.java:865)

at com.sap.tc.webdynpro.progmodel.generation.ControllerHelper.createDelegate(ControllerHelper.java:68)

at com.sap.tc.webdynpro.progmodel.generation.DelegatingComponent.<init>(DelegatingComponent.java:38)

at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.doInit(ClientComponent.java:775)

at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.init(ClientComponent.java:329)

at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.init(ClientApplication.java:352)

at com.sap.tc.webdynpro.clientserver.task.WebDynproMainTask.execute(WebDynproMainTask.java:593)

at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:59)

at com.sap.tc.webdynpro.clientserver.cal.ClientManager.doProcessing(ClientManager.java:249)

at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doWebDynproProcessing(DispatcherServlet.java:154)

at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:116)

at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doGet(DispatcherServlet.java:48)

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

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

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

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

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

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

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

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

at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:37)

at com.sap.engine.core.cluster.impl6.session.UnorderedChannel$MessageRunner.run(UnorderedChannel.java:71)

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

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

i came across this thread:

but my webdynpro and webas versions are the same (SP15).

Any other ideas?

Currently our setup is

- WebAS 6.4 SP 15, ECC 5.0 SP 15 with SAP_HR 17

- WebAS 6.4 SP 15, EP 6.0 SP 15

Any tip will be valuable.

Thanks,

Simone.

Message was edited by: Simone Teshirogui

[Former Member]

HI Simone,

Such kind of issue might arise if you have performed user mapping for the system created in EP with a userid/password which is not valid for the ECC backend.

Have you performed user mapping for the systems?

"We're also using ECC 5.0 and the SLD is centralized on the XI system"

Please elaborate on this.What is your setup?

Regards,

Siddhartha