cancel
Showing results for 
Search instead for 
Did you mean: 

Method to assign custom iViews in the MSS General Info page in NW 7.4

FabricioPereira
Participant
0 Kudos

Hello,

We are migrating the Portal applications from our Portal NW 7.02 to NW 7.4 and we are having issues to integrate some WD Java applications in the MSS General Information page. Our backend is ECC 6.0 EHP4.

These are the steps we are following:

  • Create WD Java application. We can execute it standalone successfully.
  • In the Portal, we created the view for this WD Java app using the Self-Service Administrator
  • We assigned the View to the FPM application “General Information” under Self-Service Administrator >> Portal Content >> Content Provided by SAP >> srvconfig >> com.sap.pct.erp.srvconfig.mss >> Employee Profiles >> FPM Applications >> General Information
  • After restarting the Portal, I can see the view under the application page of the mss~eepro/General information in the Content Administration >> Portal Content Management >> Web Dynpro Java Applications >> mss~eepro >> General information gwd:/mss~eepro/com.sap.xss.hr.eeprofile.GeneralInformation_base
  • We copied the GeneralInformation and pasted it as pcd content under one of our folders.
  • The new iView was not created at that moment. We had to go back to the mss~eepro application, right click on it and select the option “Update PCD Objects” for the iView to appear under the recently created General Information page.
  • The problem happens when we try to preview this page. We receive a HTTP 500 message error
  • Would you have any idea of what might be missing in our configuration or code?
  • In the old NW 7.0x, we were following the blog but on NW 7.4 we cannot create iViews as before. Blog http://wiki.sdn.sap.com/wiki/display/profile/How-to%20add%20a%20custom%20Web%20Dynpro%20iView%20to%2...
  • That’s the error we get:

500   Internal Server Error

SAP NetWeaver Application Server/Java AS

  • The initial exception that caused the request to fail, was:
  • java.lang.ClassNotFoundException: com.sap.pcuigp.xssfpm.wd.interfaces.wdp.IExternalIVAC ------------------------- Loader Info ------------------------- ClassLoader name: [company.com/portal~hr~emrgcontact] Loader hash code: 9ed3cdc Living status: alive Direct parent loaders: [system:Frame] [interface:webservices] [interface:cross] [interface:security] [interface:transactionext] [library:webservices_lib] [library:opensql] [library:jms] [library:ejb20] [service:p4] [service:ejb] [service:servlet_jsp] [library:tc~bl~exception~lib] [library:tc~cmi] [library:tc~aii~base~offline~facade] [library:tc~bl~jco~api] [sap.com/tc~wd~api] [library:tc~bl~logging~api] Resources: /usr/sap/[SID]/J[NN]/j2ee/cluster/apps/company.com/portal~hr~emrgcontact/servlet_jsp/webdynpro/resources/company.com /portal~hr~emrgcontact/root/WEB-INF/lib/company.com ~portal~hr~emrgcontact.jar ---------------------------------------------------------------

Detailed Error Information

  • -

Detailed Exception Chain

  com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: Exception was thrown in preprocessing phase of application session rii7eQgQzCRC0h5ne6FAsQ--Qf0Lhowk2LY36d0raKKqtw--/pcd:portal_content/company.com.CN_f/company.com.HR_f/company.com.MSS_f/company.com.Pages_f/company.com.MSS_f/company.com.mss_gen_info/sap.com/mss~eepro/GeneralInformation/base/. The causing exception is nested. RID=179aac35596311e4987a00000f14d927


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.sessionctx.AbstractExecutionContextDispatcher.delegateToRequestManager(AbstractExecutionContextDispatcher.java:62)
at com.sap.tc.webdynpro.serverimpl.wdc.sessionctx.DispatchHandlerForRequestManager.service(DispatchHandlerForRequestManager.java:39)
at com.sap.tc.webdynpro.serverimpl.wdc.sessionctx.DispatchHandlerForRequestManager.service(DispatchHandlerForRequestManager.java:46)
at com.sap.engine.services.servlets_jsp.server.deploy.impl.module.IRequestDispatcherImpl.dispatch(IRequestDispatcherImpl.java:292)
at com.sap.tc.webdynpro.serverimpl.wdc.sessionctx.ExecutionContextDispatcher.dispatchToAppContext(ExecutionContextDispatcher.java:68)
at com.sap.tc.webdynpro.serverimpl.core.sessionctx.AbstractExecutionContextDispatcher.dispatch(AbstractExecutionContextDispatcher.java:53)
at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:245)
at com.sap.tc.webdynpro.clientserver.embedding.JavaApplicationProxy$Runner.callRequestManager(JavaApplicationProxy.java:1244)
at com.sap.tc.webdynpro.clientserver.embedding.JavaApplicationProxy$Runner.callEmbeddedApplication(JavaApplicationProxy.java:1122)
at com.sap.tc.webdynpro.clientserver.embedding.JavaApplicationProxy$StartCommand.doExecute(JavaApplicationProxy.java:1575)
at com.sap.tc.webdynpro.clientserver.embedding.JavaApplicationProxy$AbstractCommand.execute(JavaApplicationProxy.java:1488)
at com.sap.tc.webdynpro.clientserver.embedding.JavaApplicationProxy$Runner.execute(JavaApplicationProxy.java:1028)
at com.sap.tc.webdynpro.clientserver.embedding.JavaApplicationProxy.execute(JavaApplicationProxy.java:859)
at com.sap.tc.webdynpro.clientserver.embedding.JavaApplicationProxy.start1(JavaApplicationProxy.java:637)
at com.sap.tc.webdynpro.portal.pb.impl.JavaApplicationProxyAdapter.create(JavaApplicationProxyAdapter.java:166)
at com.sap.portal.pb.PageBuilder.updateApplications(PageBuilder.java:1691)
at com.sap.portal.pb.PageBuilder.createPage(PageBuilder.java:411)
at com.sap.portal.pb.PageBuilder.init(PageBuilder.java:655)
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)
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)
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.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)
... 72 more
Caused by: com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: Could not get interface class for generating proxy controller in Component(path=FPMComponent.Z_EmergencyContact/EmergencyContactComp, class=com.sap.tc.webdynpro.progmodel.generation.DelegatingComponent)

  at com.sap.tc.webdynpro.progmodel.generation.DelegatingComponent.getInternalControllerInterface(DelegatingComponent.java:372)
at com.sap.tc.webdynpro.progmodel.generation.DelegatingComponent.getControllerOfInterface(DelegatingComponent.java:345)
at com.sap.tc.webdynpro.progmodel.components.ComponentUsage.getControllerOfInterfaceInternal(ComponentUsage.java:680)
at com.sap.tc.webdynpro.progmodel.components.ComponentUsage.getInterfaceControllerInternal(ComponentUsage.java:658)
at com.sap.tc.webdynpro.progmodel.components.ComponentUsage.getInterfaceController(ComponentUsage.java:642)
at com.sap.pcuigp.xssfpm.wd.FPMComponent.doProcessEvent(FPMComponent.java:586)
at com.sap.pcuigp.xssfpm.wd.FPMComponent.doEventLoop(FPMComponent.java:460)
at com.sap.pcuigp.xssfpm.wd.FPMComponent.wdDoInit(FPMComponent.java:215)
at com.sap.pcuigp.xssfpm.wd.wdp.InternalFPMComponent.wdDoInit(InternalFPMComponent.java:105)
at com.sap.tc.webdynpro.progmodel.generation.DelegatingComponent.doInit(DelegatingComponent.java:161)
... 78 more
Caused by: java.lang.ClassNotFoundException: com.sap.pcuigp.xssfpm.wd.interfaces.wdp.IExternalIVAC


------------------------- Loader Info -------------------------
ClassLoader name: [cn.ca/portal~hr~emrgcontact]
Loader hash code: 9ed3cdc
Living status: alive
Direct parent loaders:
[system:Frame]
[interface:webservices]
[interface:cross]
[interface:security]
[interface:transactionext]
[library:webservices_lib]
[library:opensql]
[library:jms]
[library:ejb20]
[service:p4]
[service:ejb]
[service:servlet_jsp]
[library:tc~bl~exception~lib]
[library:tc~cmi]
[library:tc~aii~base~offline~facade]
[library:tc~bl~jco~api]
[sap.com/tc~wd~api]
[library:tc~bl~logging~api]
Resources:
/usr/sap/ED8/J25/j2ee/cluster/apps/cn.ca/portal~hr~emrgcontact/servlet_jsp/webdynpro/resources/cn.ca/portal~hr~emrgcontact/root/WEB-INF/lib/cn.ca~portal~hr~emrgcontact.jar
---------------------------------------------------------------
at com.sap.engine.boot.loader.MultiParentClassLoader.loadClass(MultiParentClassLoader.java:280)
at com.sap.engine.boot.loader.MultiParentClassLoader.loadClass(MultiParentClassLoader.java:249)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:249)
at com.sap.tc.webdynpro.progmodel.generation.DelegatingComponent.getInternalControllerInterface(DelegatingComponent.java:370)
... 87 more

Accepted Solutions (0)

Answers (2)

Answers (2)

Former Member
0 Kudos

Hello,

We are facing the same problem.

Could you,please, share with us how you managed to fix it.

Thank you.

siddharthrajora
Product and Topic Expert
Product and Topic Expert
0 Kudos

if you can execute it successfully in standalone, then you need to check the URL  or roles, You can do a HTTP trace and see what URL getting generated