cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 

SAP Portal 7.4 WD Java ESS problem

Former Member

on ‎02-05-2016 2:50 PM

0 Kudos

Hi all,

Information:

  • We are in upgrade process, we have a old portal in versión 7.0 and a new portal (new installation) in versión 7.4.

  • Our R3 system is a copy or productive environment but the same system we had updated to version 7.4

  • We had transport all content and configuration from old portal to new portal.

Problem:

We have a problema with a portal role: Employed Self-Service and this role have a WD Java iview to call a external link of R3:

webdynpro:java/sap.com/pcui_gp~xssutils/com.sap.xss.ser.xssmenu.XssMenuArea/base

it is reproducing the next error (we delete roots and names confindencial):

Note: In old portal is working correctly

com.sapportals.portal.prt.runtime.PortalRuntimeException: Failed to lookup External Link for: portal_content/******



500 Internal Server Error is returned for HTTP request [http://host:8127/webdynpro/resources/sap.com/pb/PageBuilder]:
  component [dispatcher],
  web module [webdynpro/resources/sap.com/pb],
  application [sap.com/pb],
  DC name [sap.com/pb],
  CSN component[EP-PIN-WD],
  problem categorization [],
  internal categorization [-718345040].

[EXCEPTION]
com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: Exception was thrown in preprocessing phase of application session P1n*fv0A3yq0BAWdbA0FOQ--wYI1XWgO7qpqNlJI1o94*w--. The causing exception is nested. RID=e6ce7804c59c11e59d0d000000f6270a
at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doPreprocessing(ApplicationSession.java:663)
at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:349)
at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:326)
at com.sap.tc.webdynpro.serverimpl.core.AbstractDispatcherServlet.doContent(AbstractDispatcherServlet.java:87)
at com.sap.tc.webdynpro.serverimpl.wdc.DispatcherServlet.doContent(DispatcherServlet.java:101)
at com.sap.tc.webdynpro.serverimpl.core.AbstractDispatcherServlet.doPost(AbstractDispatcherServlet.java:62)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:754)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:847)
at com.sap.engine.services.servlets_jsp.server.Invokable.invoke(Invokable.java:152)
at com.sap.engine.services.servlets_jsp.server.Invokable.invoke(Invokable.java:38)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:466)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:210)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:441)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:430)
at com.sap.engine.services.servlets_jsp.filters.DSRWebContainerFilter.process(DSRWebContainerFilter.java:38)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.servlets_jsp.filters.ServletSelector.process(ServletSelector.java:81)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.servlets_jsp.filters.ApplicationSelector.process(ApplicationSelector.java:278)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.WebContainerInvoker.process(WebContainerInvoker.java:81)
at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.ResponseLogWriter.process(ResponseLogWriter.java:60)
at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.DefineHostFilter.process(DefineHostFilter.java:27)
at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.MonitoringFilter.process(MonitoringFilter.java:29)
at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.SessionSizeFilter.process(SessionSizeFilter.java:26)
at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.MemoryStatisticFilter.process(MemoryStatisticFilter.java:57)
at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.DSRHttpFilter.process(DSRHttpFilter.java:43)
at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.server.Processor.chainedRequest(Processor.java:475)
at com.sap.engine.services.httpserver.server.Processor$FCAProcessorThread.process(Processor.java:269)
at com.sap.engine.services.httpserver.server.rcm.RequestProcessorThread.run(RequestProcessorThread.java:56)
at com.sap.engine.core.thread.execution.Executable.run(Executable.java:122)
at com.sap.engine.core.thread.execution.Executable.run(Executable.java:101)
at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:328)
Caused by: com.sap.tc.webdynpro.services.exceptions.ApplicationFaultException: wdDoInit: exception thrown in this user coding area
at com.sap.tc.webdynpro.progmodel.generation.DelegatingComponent.doInit(DelegatingComponent.java:164)
at com.sap.tc.webdynpro.progmodel.controller.Controller.initController(Controller.java:227)
at com.sap.tc.webdynpro.progmodel.components.Component.initController(Component.java:258)
at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:206)
at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.init(ClientApplication.java:590)
at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.doPreprocessing(ClientApplication.java:1457)
at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doPreprocessing(ApplicationSession.java:660)
... 46 more
Caused by: com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: Failed to load the object:


pcd:portal_content/********


at com.sap.portal.pb.data.PcdManager.initialContextLookup(PcdManager.java:129)
at com.sap.portal.pb.data.PcdManager.doInit(PcdManager.java:55)
at com.sap.portal.pb.PageBuilder.init(PageBuilder.java:622)
at com.sap.portal.pb.PageBuilder.wdDoInit(PageBuilder.java:227)
at com.sap.portal.pb.wdp.InternalPageBuilder.wdDoInit(InternalPageBuilder.java:137)
at com.sap.tc.webdynpro.progmodel.generation.DelegatingComponent.doInit(DelegatingComponent.java:161)
... 52 more
Caused by: javax.naming.NamingException: Failed to lookup External Link for: pcd:portal_content/********

[Root exception is com.sapportals.portal.prt.runtime.PortalRuntimeException: Failed to lookup External Link for: pcd:portal_content/********]
at com.sap.tc.pcd.proxies.JndiProxy.getObjectInstance(JndiProxy.java:121)
at com.sapportals.portal.pcd.gl.PcdGlContext.getSemanticObject(PcdGlContext.java:962)
at com.sapportals.portal.pcd.gl.PcdGlContext.getSemanticObject(PcdGlContext.java:742)
at com.sapportals.portal.pcd.gl.PcdGlContext.lookup(PcdGlContext.java:121)
at com.sapportals.portal.pcd.gl.PcdProxyContext.lookup(PcdProxyContext.java:1824)
at com.sapportals.portal.pcd.gl.url.BaseURLContext.lookup(BaseURLContext.java:265)
at javax.naming.InitialContext.lookup(InitialContext.java:392)
at javax.naming.InitialContext.lookup(InitialContext.java:392)
at com.sap.portal.pb.data.PcdManager.initialContextLookup(PcdManager.java:125)
... 57 more
Caused by: com.sapportals.portal.prt.runtime.PortalRuntimeException: Failed to lookup External Link for: pcd:portal_content/********
at com.sap.portal.pcm.iview.admin.PcmIviewCommon.getExternalLinkApplication(PcmIviewCommon.java:277)
at com.sap.portal.pcm.iview.admin.PcmIviewCommon.initLayers(PcmIviewCommon.java:135)
at com.sap.portal.pcm.iview.admin.AdminBaseiView.createAttrSetLayersList(AdminBaseiView.java:177)
at com.sap.portal.pcm.iview.admin.AdminBaseiView.getCustomImplementation(AdminBaseiView.java:131)
at com.sap.portal.pcm.admin.PcmAdminBase.getImplementation(PcmAdminBase.java:642)
at com.sapportals.portal.ivs.iviews.IviewServiceObjectFactory.getObjectInstance(IviewServiceObjectFactory.java:378)
at com.sap.tc.pcd.proxies.JndiProxy.getObjectInstance(JndiProxy.java:69)
... 65 more



Can you help us with this problem?


Thanks and best regards


Mónica González


Show replies
Show replies
Answer

Accepted Solutions (0)

Answers (2)

Answers (2)

former_member183915
Active Contributor
‎02-08-2016 10:35 AM
0 Kudos

Hi,

You can use abap based ESS MSS application.

To use the existing applications, you might have to upgrade the Java packages  because 7.4 runs on a newer Java engine as compared to older portal installations that ran on Java 1.4 or below

You can refer this link for migration of application. This might help.

Regards,

Navya.

Show replies
Show replies
Former Member
‎02-09-2016 2:16 PM
0 Kudos

Hi Navya,

Our basic team confirm that the java componet for ESS applications is in a correct version.

Thanks and best regards

Mónica

sathish_perumal
Active Participant
‎02-09-2016 5:10 PM
0 Kudos

Monica,

       I remember I had the same issue while upgrading Portal to 7.40 and then I came across this note "1812863 - "The Employee Self Service application of travel management you want to use is outdated" Web Dynpro Java services in Travel Management" . I don't know if you are using TEA but my scenario was TEA only and we moved to all WDA after seeing this note. In fact all end users in my company likes it more than WDJ based apps. Hope this would help you.

Thanks

Sathish

former_member183915
Active Contributor
‎02-12-2016 6:36 AM
0 Kudos

Hi,

Can you attach screenshot of the same?

Regards,

Navya.

Former Member
‎02-05-2016 5:23 PM
0 Kudos

Please provide a list of system components from the upgraded portal and the upgraded backend system. You do realize that the Web Dynpro Java applications (such as XssMenu) deployed on the portal are backend dependent? Unless there are supported versions of the WDJ applications for the combination of your portal and backend you are trying to achieve something that isn't supported. Typically what happens when customers upgrade their backend system they migrate the WDJ applications to WDA or even Fiori since the WDJ applications aren't supported on newer version of Business Suite.

Show replies
Show replies
Former Member
‎02-09-2016 2:22 PM
0 Kudos

Hi Samuli,

I attach list of system components:

https://dl.dropboxusercontent.com/u/36047305/TE6_SW_components.rar

Do you have some SAP document with this information:

Unless there are supported versions of the WDJ applications for the combination of your portal and backend you are trying to achieve something that isn't supported. Typically what happens when customers upgrade their backend system they migrate the WDJ applications to WDA or even Fiori since the WDJ applications aren't supported on newer version of Business Suite.


We need oficial documentation for confirm that is necessary to adapt WDJ to WDA.


Thanks and best regards


Mónica González

Ask a Question