Uploading BI role in EP:com.sap.portal.pcd.rolemigration.RoleMigrationExcep

i am getting follwing error while uploading BI role in portal.can anybody suggest us.
com.sap.portal.pcd.rolemigration.RoleMigrationException: Access denied (Object(s): portal_content/com.sap.portal.migrated/SAPComponentSystems/roles/BIDCLNT900) - save(aibw03). Access denied (Object(s): portal_content/com.sap.portal.migrated/SAPComponentSystems/roles/BIDCLNT900) at com.sap.portal.pcd.rolemigration.RoleMigrationObject.save(RoleMigrationObject.java:5715) at com.sap.portal.pcd.rolemigration.RoleMigrationObject.save(RoleMigrationObject.java:5179) at com.sap.portal.pcd.rolemigration.RoleMigrationObject.migrate(RoleMigrationObject.java:1857) at com.sap.portal.pcd.rolemigration.RoleMigrationObject.migrate(RoleMigrationObject.java:782) at com.sap.portal.pcd.rolemigration.RoleMigrationThread.run(RoleMigrationThread.java:523) Original exception: com.sapportals.portal.pcd.gl.PermissionControlException: Access denied (Object(s): portal_content/com.sap.portal.migrated/SAPComponentSystems/roles/BIDCLNT900) at com.sapportals.portal.pcd.gl.PcdFilterContext.filterCreateSubcontext(PcdFilterContext.java:242) at com.sapportals.portal.pcd.gl.PcdProxyContext.createSubcontext(PcdProxyContext.java:147) at com.sapportals.portal.pcd.gl.PcdGlContext.createSubcontext(PcdGlContext.java:440) at com.sapportals.portal.pcd.gl.PcdGlContext.bind(PcdGlContext.java:369) at com.sapportals.portal.pcd.gl.PcdProxyContext.bind(PcdProxyContext.java:524) at com.sap.portal.pcd.rolemigration.RoleMigrationObject.createContexts(RoleMigrationObject.java:171) at com.sap.portal.pcd.rolemigration.RoleMigrationObject.save(RoleMigrationObject.java:5612) at com.sap.portal.pcd.rolemigration.RoleMigrationObject.save(RoleMigrationObject.java:5179) at com.sap.portal.pcd.rolemigration.RoleMigrationObject.migrate(RoleMigrationObject.java:1857) at com.sap.portal.pcd.rolemigration.RoleMigrationObject.migrate(RoleMigrationObject.java:782) at com.sap.portal.pcd.rolemigration.RoleMigrationThread.run(RoleMigrationThread.java:523)

Hi,
It seems you don't have the necessary rights to create content in the portal_content/com.sap.portal.migrated/SAPComponentSystems/roles/ directory.
You should check the permissions on the Portal Content > Migrated Content > SAPComponentSystems > roles directory (right click on the folder then Open > Permissions). With the default permissiosns, I think you need the super_admin_role or content_admin_role to import roles in the portal.
Regards,
Pierre

Similar Messages

Com.sap.portal.pcm.UMENamespaces role property

Dear All
This must be easy for someone...
We have built a series of EP6 SP20 portals based on content imported from pre existing systems. Subsequently there seem to be some new properties available for all the roles.
com.sap.portal.pcm.UMENamespaces and
com.sap.security.core.usermanagement.description
These properties have appeared in only one of the multiple portal environments that been been built and are not present in the source systems.
If anyone is able to shed some light on what causes these properties to appear it would be very helpful.
All the roles are affected, but newly created roles do not have the properties. The affected roles are all last changed by the user ume_service.
Points available
Thanks in advance.
William

Hi Sam,
You can find it in the com.sap.portal.ivs.systemlandscapeervice_core.jar
The location of the file is under
\usr\sap\<SID>\JC00\j2ee\cluster\server0\apps\sap.com\irj\servlet_jsp\irj\root\WEB-INF\portal\portalapps\com.sap.portal.ivs.systemlandscapeervice\private\lib\com.sap.portal.ivs.systemlandscapeervice_core.jar
Regards
Prakash

Why I upload com.sap.portal.usermanagement.admin.par,Portal can't modify?

Hi,
I change jsp in com.sap.portal.usermanagement.admin.par ,then upload it to PCD,but the portal can't change?
what can i do?
Thanks.

Login with System Admin user and then Goto
System Admin---> Support --> Portal Runtime --> Admin Console
Now you have to clean the existing Add with the name
com.sap.portal.usermanagement.admin.par
if you come down to Admin Console you can find all the Par App by DropDown Box
select the com.sap.portal.usermanagement.admin.par and clean it
Now upload you updated com.sap.portal.usermanagement.admin.par to Pcd
Thanks,
Sreeni.

Com.sap.portal.appintegrator.sap doesn't work

Hi all,
I needed to change the file 'WinGuiRenderLayer.properties'
I found the par under 3 locations:
d:\usr\sap\SPD\jc00\j2ee\cluster\server0\apps\sap.com\irj\servlet_jsp\irj\root\WEB-INF\portal\portalapps\com.sap.portal.appintegrator.sap
d:\usr\sap\SPD\jc00\j2ee\cluster\server0\apps\sap.com\irj\servlet_jsp\irj\root\WEB-INF\deployment\pcd
d:\usr\sap\SPD\jc00\j2ee\cluster\server0\apps\sap.com\irj\servlet_jsp\irj\root\WEB-INF\deployment\temp
I changed the file in those locations (I removed the bak extension and restarted the server).
Also, I made sure that the pars/directory contains the jar files.
After I restarted the server the application integrator iviews doesn't work (Web Dynpro, Transaction...).
Before I did the changes, I backed up the original pars/directory.
Copying the original pars didn't help.
How can I solve this?
Portal is EP6.16
Attched exception details:
Date : 10/25/2007
Time : 13:56:51:765
Message : [PortalNode.fireEventOnNode.toEventListener] event=onNodeReadyEvent, target=com.company.Orders, operation failed
[EXCEPTION]
com.sapportals.portal.prt.component.PortalComponentException: Error in init method
Component : com.sap.portal.appintegrator.sap.WebDynpro
 at com.sapportals.portal.prt.component.PortalComponentContext.init(PortalComponentContext.java:251)
 at com.sapportals.portal.prt.core.broker.PortalComponentContextItem.refresh(PortalComponentContextItem.java:267)
 at com.sapportals.portal.prt.core.broker.PortalComponentContextItem.getContext(PortalComponentContextItem.java:312)
 at com.sapportals.portal.prt.component.PortalComponentRequest.getComponentContext(PortalComponentRequest.java:385)
 at com.sapportals.portal.navigation.workAreaiView.doOnNodeReady(workAreaiView.java:238)
 at com.sapportals.portal.prt.component.AbstractPortalComponent.handleEvent(AbstractPortalComponent.java:388)
 at com.sapportals.portal.navigation.workAreaiView.handleEvent(workAreaiView.java:356)
 at com.sapportals.portal.prt.pom.ComponentNode.handleEvent(ComponentNode.java:252)
 at com.sapportals.portal.prt.pom.PortalNode.fireEventOnNode(PortalNode.java:369)
 at com.sapportals.portal.prt.pom.AbstractNode.addChildNode(AbstractNode.java:340)
 at com.sapportals.portal.pb.PageBuilder.createAndAddEmbeddediView(PageBuilder.java:178)
 at com.sapportals.portal.pb.PageBuilder.createiView(PageBuilder.java:391)
 at com.sapportals.portal.pb.PageBuilder.createAndAddiViews(PageBuilder.java:234)
 at com.sapportals.portal.pb.PageBuilder.doOnNodeReady(PageBuilder.java:576)
 at com.sapportals.portal.prt.component.AbstractPortalComponent.handleEvent(AbstractPortalComponent.java:388)
 at com.sapportals.portal.pb.PageBuilder.handleEvent(PageBuilder.java:725)
 at com.sapportals.portal.prt.component.CachablePortalComponent.handleEvent(CachablePortalComponent.java:685)
 at com.sapportals.portal.prt.pom.ComponentNode.handleEvent(ComponentNode.java:252)
 at com.sapportals.portal.prt.pom.PortalNode.fireEventOnNode(PortalNode.java:369)
 at com.sapportals.portal.prt.pom.AbstractNode.addChildNode(AbstractNode.java:340)
 at com.sapportals.portal.prt.core.PortalRequestManager.runRequestCycle(PortalRequestManager.java:642)
 at com.sapportals.portal.prt.connection.ServletConnection.handleRequest(ServletConnection.java:240)
 at com.sapportals.portal.prt.dispatcher.Dispatcher$doService.run(Dispatcher.java:545)
 at java.security.AccessController.doPrivileged(Native Method)
 at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:405)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
 at com.sap.engine.services.servlets_jsp.server.servlet.InvokerServlet.service(InvokerServlet.java:156)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
 at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:390)
 at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:264)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:347)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:325)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:887)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:241)
 at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
 at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148)
 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:100)
 at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
Caused by: com.sapportals.portal.prt.core.broker.PortalComponentInstantiationException: Could not instantiate implementation class com.sapportals.portal.sapapplication.SAPApplicationIntegratorComponent of Portal Component com.sap.portal.appintegrator.sap.WebDynpro because: Linkage error while loading implementation class
 at com.sapportals.portal.prt.core.broker.PortalComponentItemFacade.getInstanceInternal(PortalComponentItemFacade.java:234)
 at com.sapportals.portal.prt.core.broker.PortalComponentItemFacade.getComponentInstance(PortalComponentItemFacade.java:160)
 at com.sapportals.portal.prt.core.broker.PortalComponentItem.getComponentInstance(PortalComponentItem.java:732)
 at com.sapportals.portal.prt.component.PortalComponentContext.getComponent(PortalComponentContext.java:103)
 at com.sapportals.portal.prt.component.PortalComponentContext.init(PortalComponentContext.java:242)
 ... 41 more
Caused by: java.lang.NoClassDefFoundError: com/sapportals/portal/appintegrator/AbstractIntegratorComponent
Loader Info -
ClassLoader name: [com.sapportals.portal.prt.util.ApplicationClassLoader@72f155]
Parent loader name: [sap.com/com.sap.portal.appintegrator.sap]
References:
 not registered!
Resources:
 D:\usr\sap\SPD\JC00\j2ee\cluster\server0\apps\sap.com\irj\servlet_jsp\irj\root\WEB-INF\portal\portalapps\com.sap.portal.appintegrator.sap\private\classes
 D:\usr\sap\SPD\JC00\j2ee\cluster\server0\apps\sap.com\irj\servlet_jsp\irj\root\WEB-INF\portal\portalapps\com.sap.portal.appintegrator.sap\private\lib\com.sap.portal.appintegrator.sap_core.jar
The error occurred while trying to load "com.sapportals.portal.sapapplication.SAPApplicationIntegratorComponent".
 at com.sap.engine.frame.core.load.ReferencedLoader.loadClass(ReferencedLoader.java:389)
 at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:302)
 at java.lang.Class.forName0(Native Method)
 at java.lang.Class.forName(Class.java:219)
 at com.sapportals.portal.prt.core.broker.PortalComponentItemFacade.getInstanceInternal(PortalComponentItemFacade.java:228)
 ... 45 more
Severity : Warning
Category : /System/Server
Location : com.sap.portal.portal
Application : sap.com/irj
Thread : SAPEngine_Application_Thread[impl:3]_27
Datasource : 6397450:D:\usr\sap\SPD\JC00\j2ee\cluster\server0\log\defaultTrace.trc
Message ID : 000E7F3049DE005C0000002100001C4000043D4FEE02FB46
Source Name : com.sap.portal.portal
Argument Objs : com.sapportals.portal.prt.component.PortalComponentException: Error in init method
Component : com.sap.portal.appintegrator.sap.WebDynpro
 at com.sapportals.portal.prt.component.PortalComponentContext.init(PortalComponentContext.java:251)
 at com.sapportals.portal.prt.core.broker.PortalComponentContextItem.refresh(PortalComponentContextItem.java:267)
 at com.sapportals.portal.prt.core.broker.PortalComponentContextItem.getContext(PortalComponentContextItem.java:312)
 at com.sapportals.portal.prt.component.PortalComponentRequest.getComponentContext(PortalComponentRequest.java:385)
 at com.sapportals.portal.navigation.workAreaiView.doOnNodeReady(workAreaiView.java:238)
 at com.sapportals.portal.prt.component.AbstractPortalComponent.handleEvent(AbstractPortalComponent.java:388)
 at com.sapportals.portal.navigation.workAreaiView.handleEvent(workAreaiView.java:356)
 at com.sapportals.portal.prt.pom.ComponentNode.handleEvent(ComponentNode.java:252)
 at com.sapportals.portal.prt.pom.PortalNode.fireEventOnNode(PortalNode.java:369)
 at com.sapportals.portal.prt.pom.AbstractNode.addChildNode(AbstractNode.java:340)
 at com.sapportals.portal.pb.PageBuilder.createAndAddEmbeddediView(PageBuilder.java:178)
 at com.sapportals.portal.pb.PageBuilder.createiView(PageBuilder.java:391)
 at com.sapportals.portal.pb.PageBuilder.createAndAddiViews(PageBuilder.java:234)
 at com.sapportals.portal.pb.PageBuilder.doOnNodeReady(PageBuilder.java:576)
 at com.sapportals.portal.prt.component.AbstractPortalComponent.handleEvent(AbstractPortalComponent.java:388)
 at com.sapportals.portal.pb.PageBuilder.handleEvent(PageBuilder.java:725)
 at com.sapportals.portal.prt.component.CachablePortalComponent.handleEvent(CachablePortalComponent.java:685)
 at com.sapportals.portal.prt.pom.ComponentNode.handleEvent(ComponentNode.java:252)
 at com.sapportals.portal.prt.pom.PortalNode.fireEventOnNode(PortalNode.java:369)
 at com.sapportals.portal.prt.pom.AbstractNode.addChildNode(AbstractNode.java:340)
 at com.sapportals.portal.prt.core.PortalRequestManager.runRequestCycle(PortalRequestManager.java:642)
 at com.sapportals.portal.prt.connection.ServletConnection.handleRequest(ServletConnection.java:240)
 at com.sapportals.portal.prt.dispatcher.Dispatcher$doService.run(Dispatcher.java:545)
 at java.security.AccessController.doPrivileged(Native Method)
 at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:405)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
 at com.sap.engine.services.servlets_jsp.server.servlet.InvokerServlet.service(InvokerServlet.java:156)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
 at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:390)
 at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:264)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:347)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:325)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:887)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:241)
 at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
 at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148)
 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:100)
 at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
Caused by: com.sapportals.portal.prt.core.broker.PortalComponentInstantiationException: Could not instantiate implementation class com.sapportals.portal.sapapplication.SAPApplicationIntegratorComponent of Portal Component com.sap.portal.appintegrator.sap.WebDynpro because: Linkage error while loading implementation class
 at com.sapportals.portal.prt.core.broker.PortalComponentItemFacade.getInstanceInternal(PortalComponentItemFacade.java:234)
 at com.sapportals.portal.prt.core.broker.PortalComponentItemFacade.getComponentInstance(PortalComponentItemFacade.java:160)
 at com.sapportals.portal.prt.core.broker.PortalComponentItem.getComponentInstance(PortalComponentItem.java:732)
 at com.sapportals.portal.prt.component.PortalComponentContext.getComponent(PortalComponentContext.java:103)
 at com.sapportals.portal.prt.component.PortalComponentContext.init(PortalComponentContext.java:242)
 ... 41 more
Caused by: java.lang.NoClassDefFoundError: com/sapportals/portal/appintegrator/AbstractIntegratorComponent
Loader Info -
ClassLoader name: [com.sapportals.portal.prt.util.ApplicationClassLoader@72f155]
Parent loader name: [sap.com/com.sap.portal.appintegrator.sap]
References:
 not registered!
Resources:
 D:\usr\sap\SPD\JC00\j2ee\cluster\server0\apps\sap.com\irj\servlet_jsp\irj\root\WEB-INF\portal\portalapps\com.sap.portal.appintegrator.sap\private\classes
 D:\usr\sap\SPD\JC00\j2ee\cluster\server0\apps\sap.com\irj\servlet_jsp\irj\root\WEB-INF\portal\portalapps\com.sap.portal.appintegrator.sap\private\lib\com.sap.portal.appintegrator.sap_core.jar
The error occurred while trying to load "com.sapportals.portal.sapapplication.SAPApplicationIntegratorComponent".
 at com.sap.engine.frame.core.load.ReferencedLoader.loadClass(ReferencedLoader.java:389)
 at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:302)
 at java.lang.Class.forName0(Native Method)
 at java.lang.Class.forName(Class.java:219)
 at com.sapportals.portal.prt.core.broker.PortalComponentItemFacade.getInstanceInternal(PortalComponentItemFacade.java:228)
 ... 45 more
Arguments : com.sapportals.portal.prt.component.PortalComponentException: Error in init method
Component : com.sap.portal.appintegrator.sap.WebDynpro
 at com.sapportals.portal.prt.component.PortalComponentContext.init(PortalComponentContext.java:251)
 at com.sapportals.portal.prt.core.broker.PortalComponentContextItem.refresh(PortalComponentContextItem.java:267)
 at com.sapportals.portal.prt.core.broker.PortalComponentContextItem.getContext(PortalComponentContextItem.java:312)
 at com.sapportals.portal.prt.component.PortalComponentRequest.getComponentContext(PortalComponentRequest.java:385)
 at com.sapportals.portal.navigation.workAreaiView.doOnNodeReady(workAreaiView.java:238)
 at com.sapportals.portal.prt.component.AbstractPortalComponent.handleEvent(AbstractPortalComponent.java:388)
 at com.sapportals.portal.navigation.workAreaiView.handleEvent(workAreaiView.java:356)
 at com.sapportals.portal.prt.pom.ComponentNode.handleEvent(ComponentNode.java:252)
 at com.sapportals.portal.prt.pom.PortalNode.fireEventOnNode(PortalNode.java:369)
 at com.sapportals.portal.prt.pom.AbstractNode.addChildNode(AbstractNode.java:340)
 at com.sapportals.portal.pb.PageBuilder.createAndAddEmbeddediView(PageBuilder.java:178)
 at com.sapportals.portal.pb.PageBuilder.createiView(PageBuilder.java:391)
 at com.sapportals.portal.pb.PageBuilder.createAndAddiViews(PageBuilder.java:234)
 at com.sapportals.portal.pb.PageBuilder.doOnNodeReady(PageBuilder.java:576)
 at com.sapportals.portal.prt.component.AbstractPortalComponent.handleEvent(AbstractPortalComponent.java:388)
 at com.sapportals.portal.pb.PageBuilder.handleEvent(PageBuilder.java:725)
 at com.sapportals.portal.prt.component.CachablePortalComponent.handleEvent(CachablePortalComponent.java:685)
 at com.sapportals.portal.prt.pom.ComponentNode.handleEvent(ComponentNode.java:252)
 at com.sapportals.portal.prt.pom.PortalNode.fireEventOnNode(PortalNode.java:369)
 at com.sapportals.portal.prt.pom.AbstractNode.addChildNode(AbstractNode.java:340)
 at com.sapportals.portal.prt.core.PortalRequestManager.runRequestCycle(PortalRequestManager.java:642)
 at com.sapportals.portal.prt.connection.ServletConnection.handleRequest(ServletConnection.java:240)
 at com.sapportals.portal.prt.dispatcher.Dispatcher$doService.run(Dispatcher.java:545)
 at java.security.AccessController.doPrivileged(Native Method)
 at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:405)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
 at com.sap.engine.services.servlets_jsp.server.servlet.InvokerServlet.service(InvokerServlet.java:156)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
 at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:390)
 at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:264)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:347)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:325)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:887)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:241)
 at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
 at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148)
 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:100)
 at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
Caused by: com.sapportals.portal.prt.core.broker.PortalComponentInstantiationException: Could not instantiate implementation class com.sapportals.portal.sapapplication.SAPApplicationIntegratorComponent of Portal Component com.sap.portal.appintegrator.sap.WebDynpro because: Linkage error while loading implementation class
 at com.sapportals.portal.prt.core.broker.PortalComponentItemFacade.getInstanceInternal(PortalComponentItemFacade.java:234)
 at com.sapportals.portal.prt.core.broker.PortalComponentItemFacade.getComponentInstance(PortalComponentItemFacade.java:160)
 at com.sapportals.portal.prt.core.broker.PortalComponentItem.getComponentInstance(PortalComponentItem.java:732)
 at com.sapportals.portal.prt.component.PortalComponentContext.getComponent(PortalComponentContext.java:103)
 at com.sapportals.portal.prt.component.PortalComponentContext.init(PortalComponentContext.java:242)
 ... 41 more
Caused by: java.lang.NoClassDefFoundError: com/sapportals/portal/appintegrator/AbstractIntegratorComponent
Loader Info -
ClassLoader name: [com.sapportals.portal.prt.util.ApplicationClassLoader@72f155]
Parent loader name: [sap.com/com.sap.portal.appintegrator.sap]
References:
 not registered!
Resources:
 D:\usr\sap\SPD\JC00\j2ee\cluster\server0\apps\sap.com\irj\servlet_jsp\irj\root\WEB-INF\portal\portalapps\com.sap.portal.appintegrator.sap\private\classes
 D:\usr\sap\SPD\JC00\j2ee\cluster\server0\apps\sap.com\irj\servlet_jsp\irj\root\WEB-INF\portal\portalapps\com.sap.portal.appintegrator.sap\private\lib\com.sap.portal.appintegrator.sap_core.jar
The error occurred while trying to load "com.sapportals.portal.sapapplication.SAPApplicationIntegratorComponent".
 at com.sap.engine.frame.core.load.ReferencedLoader.loadClass(ReferencedLoader.java:389)
 at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:302)
 at java.lang.Class.forName0(Native Method)
 at java.lang.Class.forName(Class.java:219)
 at com.sapportals.portal.prt.core.broker.PortalComponentItemFacade.getInstanceInternal(PortalComponentItemFacade.java:228)
 ... 45 more
Dsr Component : <Server Name>
Dsr Transaction : 5a4c6ec082f111dccf17000e7f3049de
Dsr User : <User>
Indent : 0
Level : 0
Message Code :
Message Type : 1
Relatives : /System/Server
Resource Bundlename :
Session : 44
Source : com.sap.portal.portal
ThreadObject : SAPEngine_Application_Thread[impl:3]_27
Transaction :
User : <User>
Thanks,
Omri

Solved it.
This is what I did:
1) Took par from my production environment (same SP level)
2) Clear the par (by using 'Archive Remover')
3) Clear the pcd cache
4) Upload the par (redploy)\
5) Restart the portal
Thanks,
Omri

GETTING ERROR WHILE DEPLOYING A COM.SAP.PORTAL.RUNTIME.LOGON.PAR FILE

Hi Experts,
I need to change the text in logon screen i.e,
2006-2007 SAP AG ALL RIGHTS RESERVED
for this i changed the copyright and deployed the par file
but it is giving error like this
operation failed:please make sure the server is running or check the log(sap-plugin.log)
what should i do plz suggest me na.....
i searched the file sap-plugin.log in program files -> sap>IDE>eclipse-->plugin but i couldnt find the
plz specify the directory na...
waiting for u r response.....
Regards,
Shilpa

HI SHILPA....really sorry for the late response.
here is the error log which i m getting...(its not 500 error)
[13.08.08 / 16:49] #DEBUG LEVEL# com.sap.portal.developmentTools.ideSpecific.eclipse.PortalPlugin > Startup in progress
[13.08.08 / 16:49] #DEBUG LEVEL# com.sap.portal.developmentTools.ideSpecific.eclipse.PortalPlugin > Factory initialized !
[13.08.08 / 16:50] #ERROR LEVEL# com.sap.portal.developmentTools.ideSpecific.eclipse.wizards.sapmakepar.SAPMPWizard$1 > No Information
java.io.IOException: Server returned HTTP response code: 502 for URL: http://hostname:50000/irj/servlet/prt/portal/prteventname/upload/prtroot/com.sap.portal.runtime.system.console.ArchiveUploader?login_submit=on&j_user=Administrator&j_password=EPDJ2EEADM&j_authscheme=default&uidPasswordLogon=Log%20on
     at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:808)
     at com.sap.portal.developmentTools.general.wizards.upload.DeployEngine.readResponse(DeployEngine.java:363)
     at com.sap.portal.developmentTools.general.wizards.upload.DeployEngine.uploadPar(DeployEngine.java:435)
     at com.sap.portal.developmentTools.general.wizards.upload.DeployEngine.deploy(DeployEngine.java:221)
     at com.sap.portal.developmentTools.ideSpecific.eclipse.wizards.sapmakepar.SAPMPWizard$1.processUpload(SAPMPWizard.java:416)
     at com.sap.portal.developmentTools.ideSpecific.eclipse.wizards.sapmakepar.SAPMPWizard$1.run(SAPMPWizard.java:350)
     at org.eclipse.jface.operation.ModalContext.runInCurrentThread(ModalContext.java:302)
     at org.eclipse.jface.operation.ModalContext.run(ModalContext.java:252)
     at org.eclipse.jface.wizard.WizardDialog.run(WizardDialog.java:758)
     at com.sap.portal.developmentTools.ideSpecific.eclipse.wizards.sapmakepar.SAPMPWizard.performFinish(SAPMPWizard.java:531)
     at org.eclipse.jface.wizard.WizardDialog.finishPressed(WizardDialog.java:608)
     at org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDialog.java:321)
     at org.eclipse.jface.dialogs.Dialog$1.widgetSelected(Dialog.java:423)
     at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:89)
     at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:81)
     at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:840)
     at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:2022)
     at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:1729)
     at org.eclipse.jface.window.Window.runEventLoop(Window.java:583)
     at org.eclipse.jface.window.Window.open(Window.java:563)
     at com.sap.portal.developmentTools.ideSpecific.eclipse.wizards.actions.WizardInvokeAction.invokeWizardInANewDialog(WizardInvokeAction.java:179)
     at com.sap.portal.developmentTools.ideSpecific.eclipse.wizards.actions.WizardInvokeAction.run(WizardInvokeAction.java:84)
     at org.eclipse.ui.internal.PluginAction.runWithEvent(PluginAction.java:251)
     at org.eclipse.ui.internal.WWinPluginAction.runWithEvent(WWinPluginAction.java:207)
     at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:456)
     at org.eclipse.jface.action.ActionContributionItem.handleWidgetEvent(ActionContributionItem.java:403)
     at org.eclipse.jface.action.ActionContributionItem.access$0(ActionContributionItem.java:397)
     at org.eclipse.jface.action.ActionContributionItem$ActionListener.handleEvent(ActionContributionItem.java:72)
     at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:81)
     at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:840)
     at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:2022)
     at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:1729)
     at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:1402)
     at org.eclipse.ui.internal.Workbench.run(Workbench.java:1385)
     at com.tssap.util.startup.WBLauncher.run(WBLauncher.java:79)
     at org.eclipse.core.internal.boot.InternalBootLoader.run(InternalBootLoader.java:858)
     at org.eclipse.core.boot.BootLoader.run(BootLoader.java:461)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:324)
     at com.sap.ide.eclipse.startup.Main.basicRun(Main.java:291)
     at com.sap.ide.eclipse.startup.Main.run(Main.java:789)
     at com.sap.ide.eclipse.startup.Main.main(Main.java:607)

Portal Runtime error when modifying: com.sap.portal.runtime.logon.par

Hello,
We need some help because we get 'Portal Runtime error: iView: N/A Component Name:N/A' error when trying to access portal logon screen.
This is what we've done:
We've modified com.sap.portal.runtime.logon.par file and we've uploaded it but it doesn't work. Because of the error, we've overwritten this file with the original one but now it's imposible to access portal.
The situation it seems to be like before the modification of the .par file but we get the same error and can't access portal.
Please, do you know what could be the problem?
Thanks in advance

Hi Belen,
Here are the steps you would need to take
1. import the original par file into the NWDS and name the project as
    com.sap.portal.runtime.logon
2. Make sure the project name is com.sap.portal.runtime.logon
3. use winzip/winrar to extract the com.sap.portal.runtime.logon.par file in
    a local directory
4.Under the lib you would find two jar files copy them and paste them in your project
   under dist>PORTAL-INF>lib directory
5.move the files cert....till umResetPass....jsp into the PORTAL-INF directory
6. export the par to the server in question
7. restart your server
This should solve your problem..
Thanks,
Gokul

Custome login module:SDA can't reference com.sap.portal.usermapping_api.jar

I made my own j2ee custom login module and one of the things I wanted the custom login module to do is to clear out the UME roles for the user logging in, "download" the role assignments from an ABAP WAS system, and reassign those roles in UME. I got the coding done and created my JAR file. In building the SDA file, I can't figure out how to add com.sap.portal.usermapping_api.jar to the provider.xml file. I tried specifying it on thru "create new" and tried looking for it in the list from "Select library/interface/service, but I still get an error when loading the login module.
Does anyone know how to do this?
TIA.
Mel Calucin
Bentley Systems, Inc.

Hi Mel,
why do you think you need to reference the portal's user mapping service API? I'm not sure whether you can reference Portal services at all from J2EE level.
If you need to use user mapping in your login module, you don't need the Portal's user mapping service. Instead, you can directly use the user mapping interfaces and methods of the UME, which are contained in a J2EE library.
You can use something like the following reference to get runtime access to the UME API library:
<reference reference-type="weak">
<reference-target target-type="library">
com.sap.security.api.sda
</reference-target>
</reference>
Accessing user mapping is possible via com.sap.security.api.UMFactory.getUserMapping() which returns an object implementing com.sap.security.api.umap.IUserMapping. This is the main entry point for all user mapping related features.
Please check the Javadoc for details:
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/javadocs/nw04/sp12/user management engine - version 4.0/index.html
I hope this helps.
Best regards
Heiko

Com.sap.portal.navigation.masthead.par.bak

I have been given the task of creating a new masthead of the portal but do not have access to the files, could someone please send me: com.sap.portal.navigation.masthead.par.bak
I have tried to get this through Portal Runtime -> Browse Deployment but I always get an error when I try to upload the PAR file into NWDS.
Thank you in advance, if anyone sends it to me please post here also so others know (And so i can reward points)
Michael
[email protected]

Hi Michael,
it's quite dangerous just to use "some" navigation.masthead, maybe different from you SPS/Patch version.
The question is:
> I always get an error
> when I try to upload the PAR file into NWDS
Why that? Have you been aware that the downloaded file is a ZIP which contains the PAR in question?! (So you first have to unpack the PAR, which you want to import afterwards).
If yes, did you choose File -> Import -> PAR-File?!
If yes, what kind of error came up?
Hope it helps
Detlev

Com.sap.portal.connectivity.destinations.PortalDestinationsServiceException

Hi
I am getting this error for some users in the portal.
com.sap.portal.connectivity.destinations.PortalDestinationsServiceException:User is missing credentials for connecting to alias SAP_R3_humanResources.
This is only happenning for some of the users at the moment and I cannot figure out what is causing it.
We have:
EP7 for Online Expenses
ECC6
I have re-registered the WebFlowConnector just to see if thats the problem.
I have checked the users portal roles and his backend roles and all are OK
I have also checked the Web Dynpro connector for SAP_R3_HumanResources.
Can anybody help me out on this please.
Many Thanks
Steve

Got this from SAP
1st reply
The UWL_service was introduced in NW 700. So, 1133821 will not be relavant for NW 6.40. However, in 640 system we use Basis plugins.
So, to check that please provide me the complete backend system version. The UWL uses functions from the Basis plug in instead of the Enterprise Portal plug in (WP-PI 6.0) for back end systems using Release 640. Support Package 12 makes the necessary functions available in the Basis. You can make the necessary changes in the Basis plug in (PI_BASIS) using notes or Support Packages.
Could you please check which release are you on? Remember after you applies this (SP12), you will need to reregister the UWL system in the system admin on the portal. *This is not only for substitution, but for other functionality as well* We recommend this for 640 systems in general that the PI_BASIS is maintained at the highest level.
This warning message will occur for users that do not have access to the systems that are configured in the UWL UI. For example, if we have 1. BW system 2. SRM system, and you 'steve', are able and have access to the BW system, but do not have a Userid in SRM backend, you will receive this msg. This is normal behaviour for the Universal worklist. So your option there would be to create a dummy id for you on the backend system so that your id can connect but that you don't have auth to.
2nd reply
You seems to be on lower version for Basis Plug-ins. The basis plug in should be at version 12 or higher and is at version 9. You will need to ensure that the users exist in both systems to get rid of the warning messages. Details for the Basis Plug-ins can be found on Note:883558.
3rd reply
If I am right then you are talking about the solution provided to get rid of the warning message.
So, in this regard as Steve already mentoned The Portal is an EP7 portal running on NW 7.0 SP20. It has to connect to {2 different R3 backends}.
1. ECC 6 running on NW 7.0 and UWL is configured with a SAP_ECC_TRAVEL WebFlow Connector (this works perfectly)
2. ECC 5 running on NW 6.40 and UWL is configured with a SAP_R3_HumanResources WebFlowConnector (please see attachment for error)
So, In reply to this I mentioned that to get rid of the warning message you have create users in both the systems. May be you do not grant authorization as per your requirement.
because these warning message are been displayed because the UWL UI havebeen configured to pull tasks from 2 backends. and User logging in mighthave access to only one backend system so, that's the reason for other R3 system they get the warning message.
Or if there is a concern with basis Plug-ins then it will be adviced to refer to the Notes, as those are system requirement.

Com.sap.portal.runtime.logon.par information in Authschemes.xml

Hello Portal gurus,
I am trying to customize the Portal logon page by modifying the com.sap.portal.runtime.logon.par file. I modified the par file. But after this change, I wanted to change the authschemes.xml file to reflect the par file changes.
When I downloaded the .xml file, I only found occurences of <frontendtarget>com.sap.portal.runtime.logon.certlogon</frontendtarget>, <frontendtarget>com.sap.portal.runtime.logon.basicauthentication</frontendtarget> and <frontendtarget>com.sap.portal.runtime.logon.header</frontendtarget>
Could anybody confirm, whether I have to rename these occurrences of com.sap.portal.runtime.logon with my customized logon .par file name between <frontendtarget> and </frontendtarget>?
Points will be awarded for correct answers and useful suggestions.
Thanks,
~~LB

Hi
Here is the procedure
1. Start the Config Tool by executing <SAPJ2EEEngine_installation>\j2ee\configtool\configtool.bat.
2. Navigate to cluster_data>server>persistent>com.sap.security.core.ume.service.
3. Switch to edit mode by clicking on the pencil which is at the upper right area.
4. In the tree, select authschemes.xml and choose Download. Save the file to your local directory
5. Edit the local file: To select the new PAR file as the Logon page change the occurrence of all substrings com.sap.portal.runtime.logon to your
project/PAR file name. All com.sap.portal.runtime.logon should be substituted with something like com.company.portal.runtime.logon (or whatever you project name is). Dont remove the part behind it.
(These are the profiles in the portalapp.xml and have the names default, certlogon, basicauthentication, header, and anonymous).
6. Create a new node in the configuration tree in the Config-Tool for the edited file as follows:
a.Select the node com.sap.security.core.ume.service.
b. Choose the symbol for Creating a node below the selected node.
c. Select the type File-entry.
d. Choose Upload and select the custom file from your local directory.
e. Enter a name for the entry, for example, authschemes_myHR.xml. By default, the name of the uploaded file is used.
f. Choose Create.
g. Choose Close window.
h. The new node appears in the configuration tree.
i. Go to Global server configuration>services> com.sap.security.core.ume.service and edit the property login.authschemes.definition.file.
The value needs to be changed from authschemes.xml to authschemes_myHR.xml
j. Restart the Portal. That is often not done and the changes will not appear.
Rgds
Srikanth

Portal is blank after modifying com.sap.portal.layouts.framework

Hi Experts,
Using SAP EP 7.0 SPS 18 and NWDS 7.0.18
I downloaded the par file com.sap.portal.layouts.framework because I wanted to increase the width of the detailed navigation panel. I imported it into NWDS and in the WAandNavPanel.jsp I modified this line
<hbj:page title="Portal Page">
 <hbj:gridLayout id="GridLayout1" width="100%" cellSpacing="2">
 <hbj:gridLayoutCell rowIndex="1" columnIndex="1" width="20%" verticalAlignment="top">
 <lyt:container id="navPanelContainer" />
 </hbj:gridLayoutCell>
 <hbj:gridLayoutCell rowIndex="1" columnIndex="2" width="80%" verticalAlignment="top">
 <lyt:container id="workAreaContainer" />
 </hbj:gridLayoutCell>
 </hbj:gridLayout>
</hbj:page>
To this:
<hbj:page title="Portal Page">
 <hbj:gridLayout id="GridLayout1" width="100%" cellSpacing="2">
 <hbj:gridLayoutCell rowIndex="1" columnIndex="1" width="25%" verticalAlignment="top">
 <lyt:container id="navPanelContainer" />
 </hbj:gridLayoutCell>
 <hbj:gridLayoutCell rowIndex="1" columnIndex="2" width="75%" verticalAlignment="top">
 <lyt:container id="workAreaContainer" />
 </hbj:gridLayoutCell>
 </hbj:gridLayout>
</hbj:page>
I then selected 'Quick PAR Upload' from NWDS and selected 'Include the source code of the portal application' and 'Deploy PAR' checkboxes and then deployed.
Now when I login to the portal, its just a blank screen. What did I do wrong, and how can I fix this please?
Regards,
Marshall.

Hi Marshall,
Just a couple of notes for you:
Changing the SAP namespace to your own/client namespace is a good idea, though you'll need to copy all referenced Portal objects if possible. In addition, every support pack or patch will require you to recreate this PAR file using the original SAP source as the underlying code may have changed.
All that said, the easiest way to check out a change is to make a change directly to the PAR file and upload. I do this when working with a local Portal install (not the development one).
Another point, make sure when you upload it via System Admin/Support/Runtime Tools/Administration Console (or something like that); that you get a valid version number when you upload. If you don't, that indicates something is wrong with the PAR file.
Maybe a test for you would be to take the existing PAR file, and upload it again without modification to see if there's a problem; then do it again, but this time just adding some space or something to the file (no code changes). Keep baby stepping till you work out what code is making the screen go blank for you.
Regards,
Matt
ps. I hope you've solved this by now...Otherwise ask your friendly SAP expert (who may be handy) how to do it. Alternatively, publish exactly the change you're making and we can review it.

Exception when using a renamed com.sap.portal.navigation.toolarea.par file

Hi,
I would like to modify the toolarea of our SAP Enterprise Portal. Basically, I just want to move the tools to the right hand side.
Problem Description
According to several threads I found on sdn
- How to modify the header
- copy and rename par-file?
it should be fairly simple to modify the tool area.
- download com.sap.portal.navigation.toolarea.par from portal server
- import the downloaded par file into your NetWeaver Developer Studio
- Change the ToolAreaiView.jsp in project folder dist/PORTAL-INF/jsp
- Save changes
- Deploy project to the portal server (>File>Export>Par File><Name of your project>>Next>...)
- Remove the standard Tool Area iView from your Framework page
- Create a new iView from your uploaded par file (chose default component)
- Add new created iView to your Framework page
Done, you should see your customized tool area. Unfortunately I encounter a Portal Runtime Exception (Page could not create the iView). I did exactly as described above.
- I downloaded the com.sap.portal.navigation.toolarea.par.bak file from >System Administration>Support>Portal Runtime>Browse Deployment>ROOT>WEB-INF/deployment/temp.
- Extracted the com.sap.portal.navigation.toolarea.par after changing the downloaded files file extension to zip
- Imported the extracted par file into Netweaver Developer Studio under a new project name
- Found the ToolAreaiView.jsp in project folder dist/PORTAL-INF/jsp
- Did NO changes
- Exported the project into a par file and deployed the par file to the portal successfully.
- Removed the old Tool Area iView from the Framework page
- Created a new Tool Area iView from my uploaded par file (default component)
- Added the new created iView to the Framework page.
- I logged on again and instead of the Tool Area I see an error message
Portal Runtime Error
An exception occurred while processing a request for :
iView : pcd:portal_content/sdm_Germany/de.sdm.kellermann.folders.home/de.sdm.kellermann.folders.coreobjects/default/frameworkPages/de.sdm.kellermann.coreobjects.frameworkpage/de.sdm.kellermann.iviews.toolarea
Component Name : null
Page could not create the iView.
See the details for the exception ID in the log file
Background information
J2EE Engine: 6.40 PatchLevel 89291.313
Portal: 6.0.11.3.0
Browser: Microsoft Internet Explorer 6 SP2
NWDS: 2.0.11
Any ideas what I did wrong? I appreaciate any kind of help.
Best regards,
Martin

Hi Yoav,
thank you for your swift response. You were right. I do not know why but after I imported the downloaded par file into NetWeaver Developer Studio, the new created project did not contain the jar files, which come with the par file. I added the jar files manually to the project, put them into the project's build path and instructed the NWDS to put them into the par file which I deployed to the portal server.
Afterwards I completed the routine described in my first post and everything worked out. Thanks a lot for that hint.
By the way do you know how to instruct NWDS to include the jar files automatically during an import?
Best regards,
Martin

Error inPortal Header after changing com.sap.portal.navigation.masthead.par

Hi All,
Iam getting this error while trying to change "com.sap.portal.navigation.masthead.par" within portal. I have updated the HeaderiView.jsp and then saved the PAR file and uploaded the file. It was successful upload from Administration console. But after I logged into portal again, I got this error and even though I tried to revert back the changes, it still gives the same error. Has any one faced similar issue? We faced this during the IE8 (Internet explorer 8) upgrade to SP 27 in sap portal.
Thanks.
#1.#0003BA4D72F200540000000300003DEA00049C4FAA821F4E#1297765883836#com.sap.portal.prt.runtime#sap.com/irj#com.sap.portal.prt.runtime#O000001496#192##n/a##bbf9eef438ee11e08722000035d6a152#Thread[PRT-Async 2,5,PRT-Async]##0#0#Error##Java###10:31_15/02/11_903258450
[EXCEPTION]
#1#com.sapportals.portal.prt.component.PortalComponentException: Error in init method
Component :
        at com.sapportals.portal.prt.component.PortalComponentContext.init(PortalComponentContext.java:251)
        at com.sapportals.portal.prt.core.broker.PortalComponentContextItem.refresh(PortalComponentContextItem.java:267)
        at com.sapportals.portal.prt.core.broker.PortalComponentContextItem.getContext(PortalComponentContextItem.java:312)
        at com.sapportals.portal.prt.component.PortalComponentRequest.getComponentContext(PortalComponentRequest.java:385)
        at com.sapportals.portal.pb.PageBuilder.createIviewProfile(PageBuilder.java:418)
        at com.sapportals.portal.pb.PageBuilder.createiView(PageBuilder.java:372)
        at com.sapportals.portal.pb.PageBuilder.createAndAddiViews(PageBuilder.java:234)
        at com.sapportals.portal.pb.PageBuilder.doOnNodeReady(PageBuilder.java:576)
        at com.sapportals.portal.prt.component.AbstractPortalComponent.handleEvent(AbstractPortalComponent.java:388)
        at com.sapportals.portal.pb.PageBuilder.handleEvent(PageBuilder.java:725)
        at com.sapportals.portal.prt.component.CachablePortalComponent.handleEvent(CachablePortalComponent.java:706)
        at com.sapportals.portal.prt.pom.ComponentNode.handleEvent(ComponentNode.java:252)
        at com.sapportals.portal.prt.pom.PortalNode.fireEventOnNode(PortalNode.java:369)
        at com.sapportals.portal.prt.pom.AbstractNode.addChildNode(AbstractNode.java:340)
        at com.sapportals.portal.navigation.PortalLauncher.doOnNodeReady(PortalLauncher.java:218)
        at com.sapportals.portal.prt.component.AbstractPortalComponent.handleEvent(AbstractPortalComponent.java:388)
        at com.sapportals.portal.prt.pom.ComponentNode.handleEvent(ComponentNode.java:252)
        at com.sapportals.portal.prt.pom.PortalNode.fireEventOnNode(PortalNode.java:369)
        at com.sapportals.portal.prt.pom.AbstractNode.addChildNode(AbstractNode.java:340)
        at com.sapportals.portal.prt.core.PortalRequestManager.runRequestCycle(PortalRequestManager.java:642)
        at com.sapportals.portal.prt.connection.ServletConnection.handleRequest(ServletConnection.java:240)
        at com.sapportals.portal.prt.dispatcher.Dispatcher$doService.run(Dispatcher.java:547)
        at java.security.AccessController.doPrivileged(Native Method)
        at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:407)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
        at com.sap.engine.services.servlets_jsp.server.runtime.RequestDispatcherImpl.doWork(RequestDispatcherImpl.java:321)
        at com.sap.engine.services.servlets_jsp.server.runtime.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:377)
        at com.sap.portal.navigation.Gateway.service(Gateway.java:101)
        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:1060)
        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: com.sapportals.portal.prt.core.broker.PortalApplicationNotFoundException: Could not find portal application
at com.sapportals.portal.prt.core.broker.PortalApplicationItem.getDeploymentDescriptor(PortalApplicationItem.java:1622)
        at com.sapportals.portal.prt.core.broker.PortalComponentItem.getConfiguration(PortalComponentItem.java:1022)
        at com.sapportals.portal.prt.core.broker.PortalComponentItem.refresh(PortalComponentItem.java:274)
        at com.sapportals.portal.prt.core.broker.PortalComponentItem.getComponentInstance(PortalComponentItem.java:729)
        at com.sapportals.portal.prt.component.PortalComponentContext.getComponent(PortalComponentContext.java:103)
        at com.sapportals.portal.prt.component.PortalComponentContext.init(PortalComponentContext.java:242)
        ... 42 more

Thanks Raghu.
I have tried that option as well. But, when I uploaded the PAR file from DEV to Sandbox environment, the header did not work, but I identified that the "portalapp.xml" file is only partially deployed (even though the PAR that is used for Upload (using Admin Console) contained all parameters. I could not understand why the portalapp.xml is only partially deployed.
After deployment the portalapp.xml has only 3 properties within it : ClassLoadingPolicy, value 5.0, DeploymentPolicy, value 5.0 and AuthenticationPolicy, value 5.0,
and all other attributes that are part of the uploaded par file are not present after deployment within "PAR directory within portalapps directory".
Edited by: jakk on Feb 16, 2011 5:17 PM
Edited by: jakk on Feb 16, 2011 5:19 PM

How to download com.sap.portal.navigation.contentarea par file

I am trying to download the com.sap.portal.navigation.contentarea par file so that I can modify it and upload it with a new name. I found the file in the Support Desk of the portal, and I downloaded it just fine. However, when I download it it was in the form of com.sap.portal.support.browse.zip. I tried to extract the files from there, and I came up with com.sap.portal.support.browse.
How can I get this in the form of a par file to import into NWDS? I have imported par files into NWDS before, but I nothing I am trying is working, because I can't get it into the .par or .par.bak formats.
Thanks,
Owen

OK done...
I am doing it and explaining you step by step same time...
1. logged in to portal -> system administration -> support -> ROOT/WEB-INF/deployment/pcd
2. clicked download link beside com.sap.portal.navigation.contentarea.par.bak file.
3. downloaded/saved to my desktop
4. Now I have file com.sap.portal.support.browse.default on my local machine.
5. Right click on this . default file and select Add to "com.sap.portal.support.browse.default.rar" --- this is the important step...*
6. Now you have com.sap.portal.support.browse RAR / ZIP file (no extension will be added, you can check it by file format).
7. Keep on double clicking on rar file till you see .bak file.
8. Once you are at / you see com.sap.portal.navigation.contentarea.par.bak then right click on this file and select "Exctract to specified folder" ...
9. Change the path to where you want to store .bak.
10. rename it to .par by removing .bak.
That is it... its all yours to modify/customize...
Hope this is clear to you.... let me know If you see anymore issues.
As you asked for... I have done it in my system and writing it to you....
-PradeeP

IView not found: com.sap.portal.support.browse.default.

When I try to navigate to System Administration -> Support -> Portal Runtime -> Browse deployment, I get the following error:
Portal Runtime Error
An exception occurred while processing a request for :
iView : N/A
Component Name : N/A
iView not found: com.sap.portal.support.browse.default.
Exception id: 04:45_02/10/08_0037_13390350
I referred this thread [https://www.sdn.sap.com/irj/sdn/thread?threadID=188079|https://www.sdn.sap.com/irj/sdn/thread?threadID=188079] and removed the .bak extension from the file com.sap.portal.support.browse.par.bak and uploaded it in System Administration --> Support --> Support Desk --> Portal Runtime --> Administration Console ,in the Archive uploader.
But the problem persists. Could anybody shed some light on this issue?
Regards,
Saurabh.

Hi Saurabh
In order to get more information, you should search for your exception id "04:45_02/10/08_0037_13390350" in the default trace file.
See http://help.sap.com/saphelp_nw70/helpdata/EN/57/5f1140d72dc442e10000000a1550b0/frameset.htm in order to see where the def trace file is found.
Best regards,
Martin Søgaard

Uploading BI role in EP:com.sap.portal.pcd.rolemigration.RoleMigrationExcep

Similar Messages

Maybe you are looking for