Deploying ESS/MSS

Question

Hi,
We are having some issues with regards to Self Services. We have done a EP7.01 deployment and updated the J2EE Core components. We also installed the XSS Business Packages. All this was done using JSPM and is visible under deployed components.
Now the issue arose when a apps consultant noticed an error:
   com.sapportals.portal.prt.runtime.PortalRuntimeException: Failed in WD JNDI lookup. javax.naming.NameNotFoundException: No child found in WebDynproContext with name essuspdata
I have had a look at these forums to prevent wasting people's valuable time
Re: ESS IVIEW not working
Re: PortalRuntimeException: Failed in WD JNDI lookup
Re: Error in the Standard MSS iview?
Now it seems that if the XSS services were deployed then they would be visible in Visual Administrator under the "deploy" service ->webdynpro along with the big list there is already. Now i cannot find this "essuspdata" or any other ESS/MSS service there, which suggests that it may not be installed or deployed or started. Now correct me if i am wrong, all deployment should be done via JSPM not SDM? I had a look in SDM for curious reasons and saw ESS/MSS and other Business Packages there in the list under SDM repository but it does not say if it is deployed/installed/started.
Can someone please guide me where i have gone wrong, as i am new to Enterprise Portal?
thanks in advance!
Mani

Answer 1

thanks for your reply.
he has said there is nothing he hasn't forgot to look into and tried.
I had a look into the SAP logviewer and saw some errors come up at the time i tried to start the essuspdata
the application that is causing this is: Application : sap.com/tcwddispwda
i am not sure if this is dependant on other applications/services that are supposed to be started
(sorry for the huge dump of information and badly formatted reply)
in 1st order of error occuring
Exception occured during processing of Web Dynpro application sap.com/pb/PageBuilder. The causing exception is nested.
[EXCEPTION]
com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: Failed to load page
     at com.sap.portal.pb.PageBuilder.init(PageBuilder.java:529)
     at com.sap.portal.pb.PageBuilder.wdDoInit(PageBuilder.java:193)
     at com.sap.portal.pb.wdp.InternalPageBuilder.wdDoInit(InternalPageBuilder.java:150)
     at com.sap.tc.webdynpro.progmodel.generation.DelegatingComponent.doInit(DelegatingComponent.java:108)
     at com.sap.tc.webdynpro.progmodel.controller.Controller.initController(Controller.java:215)
     at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:200)
     at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.init(ClientComponent.java:430)
     at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.init(ClientApplication.java:362)
     at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.initApplication(ApplicationSession.java:783)
     at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:303)
     at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:741)
     at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:694)
     at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:253)
     at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:149)
     at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:62)
     at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doPost(DispatcherServlet.java:53)
     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.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:104)
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)
Caused by: javax.naming.NamingException: Failed in WD JNDI lookup. javax.naming.NameNotFoundException: No child found in WebDynproContext with name essuspdata [Root exception is com.sapportals.portal.prt.runtime.PortalRuntimeException: Failed in WD JNDI lookup. javax.naming.NameNotFoundException: No child found in WebDynproContext with name essuspdata]
     at com.sapportals.portal.pcd.gl.JndiProxy.getObjectInstance(JndiProxy.java:51)
     at com.sapportals.portal.pcd.gl.PcdGlContext.getSemanticObject(PcdGlContext.java:929)
     at com.sapportals.portal.pcd.gl.PcdGlContext.getSemanticObject(PcdGlContext.java:702)
     at com.sapportals.portal.pcd.gl.PcdGlContext.lookup(PcdGlContext.java:73)
     at com.sapportals.portal.pcd.gl.PcdURLContext.lookup(PcdURLContext.java:238)
     at javax.naming.InitialContext.lookup(InitialContext.java:347)
     at com.sap.portal.pb.data.PcdManager.doInit(PcdManager.java:72)
     at com.sap.portal.pb.PageBuilder.init(PageBuilder.java:527)
     ... 31 more
Caused by: com.sapportals.portal.prt.runtime.PortalRuntimeException: Failed in WD JNDI lookup. javax.naming.NameNotFoundException: No child found in WebDynproContext with name essuspdata
     at com.sap.portal.pcm.iview.admin.AdminBaseiView.createAttrSetLayersList(AdminBaseiView.java:357)
     at com.sap.portal.pcm.iview.admin.AdminBaseiView.getAttrSetLayersList(AdminBaseiView.java:205)
     at com.sap.portal.pcm.iview.admin.AdminBaseiView.getCustomImplementation(AdminBaseiView.java:148)
     at com.sap.portal.pcm.admin.PcmAdminBase.getImplementation(PcmAdminBase.java:530)
     at com.sapportals.portal.ivs.iviews.IviewServiceObjectFactory.getObjectInstance(IviewServiceObjectFactory.java:430)
     at com.sapportals.portal.prt.jndisupport.DirectoryManager.getObjectInstance(DirectoryManager.java:56)
     at com.sapportals.portal.pcd.gl.JndiProxy.getObjectInstance(JndiProxy.java:47)
     ... 38 more
2nd
application [webdynpro/dispatcher] Processing HTTP request to servlet [dispatcher] finished with error.
The error is: com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: Failed to load page
Exception id: [0017085D3F2500700000000600001ADC000488AAF4368BB8]
not sure why it is giving this error, as it seems like a general issue but i can't put my finger on it.
I had a check for other errors which i have rectified myself and its looking slightly cleaner than before.
again i have looked all over google, SDN, OSS notes and nothing. Not sure if this is a new problem or am i missing some config somewhere. did find one note which said to apply the latest java component patches which i have but its not sorted anything. My only concern is why i can't see essuspdata or any other ess/mss under  Content Administration -> Webdynpro -> under deployed content -> sap.com which only indicates its not deployed but from here onwards i am truly lost as to why
Any ideas,
Mani