cancel
Showing results for 
Search instead for 
Did you mean: 

Problem acessing webdynpro applications deployed using SDM

Former Member
0 Kudos

Dear All,

We have two seperate boxes for ECC 5.0 and (WEBAS + EP).

I am trying to run ESS and MSS on portal.

I downloaded BP for ESS/MSS 100(for souce cose) and ESS/MSS 60.1(iview and other content) both.

I deployed them both through SDM.

I maintained all required JCo connection with ECC system as my target system.

I maintained SAP_WEBDYNPRO_XSS system as my WAS system.

I can see ESS/MSS roles and pages etc in portal.

Also in webdynpro content administration i can see all deployed service i.e. ess/ar/pdata etc.

When i select any of the service, and drip down to application node, i get error

"Failed to find classpath for sap.com/ess~ben"

or whatever service i select.

when i run the application i get attached error.

if you have any clue.. what is missing?

thanks for your time,

Regards,

Sudhir

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)

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Hi Sudhir,

I think you have not deployed XSS which is required by ESS and MSS.

Hence when you run a ESS or MSS application is tries to find the classes from XSS package and since its not deployed, it gives you the above Error.

Please deploy the XSS package and then run your application.

Hope this helps.

With Best Regards,

Shubham

Former Member
0 Kudos

Hi Shubham,

Thanks for your reply..

I am

Installations and Upgradesè -> SAP NetWeaverè -> SAP NETWEAVERè -> SAP NETWEAVER 04 -> Business packages -> Portal content

I have deployed ESS, MSS and SAPPCUI_GP files.. and in SDM i can see they are successful deployed..

in ESS deployment there was some error for ess/tra

and other component ess/tra/*

no idea that will cause this issues. check the log in SDM.

Starting Deployment of ess/tra

Finished with warnings: development component 'ess/tra'/'sap.com'/'MAIN_xss04VAL_C'/'114133':

Caught exception during application startup from SAP J2EE Engine's deploy service:

java.rmi.RemoteException: Error occurred while starting application sap.com/ess/tra and wait. Reason: Clusterwide execption: server ID 2107050:<Localization failed: ResourceBundle='com.sap.engine.services.deploy.DeployResourceBundle', ID='com.sap.engine.services.deploy.container.DeploymentException: <Localization failed: ResourceBundle='com.sap.engine.services.deploy.DeployResourceBundle', ID='Failed implicit start for sap.com/esstratrr : Unknown state(5)', Arguments: []> : Can't find resource for bundle java.util.PropertyResourceBundle, key Failed implicit start for sap.com/esstratrr : Unknown state(5)', Arguments: []> : Can't find resource for bundle java.util.PropertyResourceBundle, key com.sap.engine.services.deploy.container.DeploymentException: <Localization failed: ResourceBundle='com.sap.engine.services.deploy.DeployResourceBundle', ID='Failed implicit start for sap.com/esstratrr : Unknown state(5)', Arguments: []> : Can't find resource for bundle java.util.PropertyResourceBundle, key Failed implicit start for sap.com/esstratrr : Unknown state(5)

(message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performAction(DeploymentActionTypes).REMEXC)

Deployment of ess/tra finished with Warning (Duration 11282 ms)

Answers (1)

Answers (1)

Former Member
0 Kudos

Closing old messages, not relevant now.