Event name in SAP Portal
Dear all,
I need to know what the different event name for allowin iViews to communicate with each other and with the portal environment itself . Example EPCM.subscribeEvent("urn:com.sapportals:navigation", "Navigate", pop);
In above code the "navigation" is the name of the event.
similarly i want to knwo all the event pertaning to portal.
Please help on this.
Regards
Pravesh,
pagebuilder is another event
EPCM.raiseEvent("urn:com.sapportals:pagebuilder", "expand",
Thanks
Bala Duvvuri
Similar Messages
-
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,
OmriSolved 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 -
SolMan in Portal - com.sap.portal.epsolman.EPSolman
Hi Experts
I have implemented the standard Solution Manager reporting iView. When using this iView I often receive the error below.
The error occurs when the iView has been open for a while and fails when I try to submit.
I our DEV and QA environment it fails after about 8-10 minutes and in our prod it is more random like between 2- 7 minutes.
The oddest this is that the same error occurs when I use the Reset button.
First I thought it was a backend issue but when I fail as well when using the Reset button then I looks more like a Portal timeout issue.
Anyone has any ideas on how to solve this issue?
Thanks in advance
Cheers
John
Portal Runtime Error
An exception occurred while processing a request for :
iView : pcd:portal_content/Content/sol_man/iviews/com.webdata.iv.sol_man.i0062_role_application
Component Name : com.sap.portal.epsolman.EPSolman
The exception was logged. Inform your system administrator..
Exception id: 03:29_04/09/07_0089_17936650
See the details for the exception ID in the log fileYes my idea as well, I have looked at some of the iview timeout settings parameter and none of them seems to have a short timeout period, but maybe I am looking at the wrong parameters
Cheers
John -
Solution manager in Portal - com.sap.portal.epsolman.EPSolman
Hi
I have implemented the standard Solution Manager reporting iView. When using this iView I often receive the error below.
The error occurs when the iView has been open for a while and fails when I try to submit.
I our DEV and QA environment it fails after about 8-10 minutes and in our prod it is more random like between 2- 7 minutes.
The oddest this is that the same error occurs when I use the Reset button.
First I thought it was a backend issue but when I fail as well when using the Reset button then I looks more like a Portal timeout issue.
Anyone has any ideas on how to solve this issue?
Thanks in advance
Cheers
John
Portal Runtime Error
An exception occurred while processing a request for :
iView : pcd:portal_content/Content/sol_man/iviews/com.webdata.iv.sol_man.i0062_role_application
Component Name : com.sap.portal.epsolman.EPSolman
The exception was logged. Inform your system administrator..
Exception id: 03:29_04/09/07_0089_17936650
See the details for the exception ID in the log fileUser mapping is only a part of singlesign on process to other systems from portal.
As per my view , It is not possible to connect with only usermapping.
Koti Reddy -
Portal runtime error on com.sap.portal.frameworkpage
Hi friends,
i have an issue with portal 6.0 Production server, we have cluster with port 50000 & dialog instance on other host with port 50600 and also web dispatcher with port 8000.
we got an issue with this port: 50000, when we tried this link: http://<hostname>:50000/irj/portal
we got this error:
Portal Runtime Error
An exception occurred while processing a request for :
iView : pcd:portal_content/every_user/general/com.sap.portal.defaultDesktop/frameworkPages/com.sap.portal.frameworkpage/com.sap.portal.toolAreaiView
Component Name : com.sap.portal.navigation.toolarea.default
The exception was logged. Inform your system administrator..
Exception id: 12:54_12/03/09_0009_9444650
See the details for the exception ID in the log file
But no issues when i tried with links http://<hostname>:8000//irj/portal & http://<hostname>:50600/irj/portal
can any one help to fix this issue please.Hi Udhaya,
Have you checked the entires in Host and Services file.
To check the entires you need to follow folloing steps :
Start --> Run --> Drivers\etc\host
Start --> Run --> Drivers\etc\services
open the file with help of notepad.
check the instance number
http://<hostname>:5(instance number)00/irj/portal
Regards, -
COM.SAP.PORTAL.RESERVED.WD.PB.RESTART
Hello everyone,
I have publish a BI iView into my portal, when I preview this iView(BW Query) it executes fine. But when I add the iView to a Page, and try to preview the Page, I get the following error:
Portal Runtime Error
An exception occurred while processing a request for :
iView : com.sap.ip.bi.web.portal.integration.launcher
Component Name : com.sap.ip.bi.web.portal.integration.launcher
The parameter name "COM.SAP.PORTAL.RESERVED.WD.PB.RESTART" contains the invalid character ".".
Exception id: 09:02_25/10/06_0009_528583550
See the details for the exception ID in the log file
Any idea what it could be?
Rgds
SirahuenHi Jose,
If the BW and EP are not compatible versions , you get this kind of error , where the conversion has some problems.
We had the same issue and upgraded our patch levels and it worked fine.
Cheers
Raja Gopal Gangula -
Hi all,
I must to deploy the "com.sap.portal.navigation.masthead.par" from Portal 7.0 to Portal 7.30
I'm doing the following steps:
- Convert .par to .ear
- Import .ear to NWDS 7.30
- Deployment perspective > Import > File System > com.sap.portal.navigation.masthead.ear > Start
Results log:
S U M M A R Y
~~~~~~~~~~~~~~~~~~~
Successfully deployed: 0
Deployed with warnings: 0
Failed deployments: 1
~~~~~~~~~~~~~~~~~~~
[ERROR CODE DPL.DCAPI.1031] AllItemsAlreadyDeployedValidationException.
Reason: ASJ.dpl_dc.003456 All batch items are marked as AlreadyDeployed because of Version check.
1. File:D:\Documents and Settings\corellavpd\Escritorio\com.sap.portal.navigation.masthead.ear
+ Name:com.sap.portal.navigation.masthead+
+ Vendor:sap.com+
+ Location:SAP AG+
+ Version:1+
+ Deploy status:AlreadyDeployed+
+ Version:LOWER+
+ Description:+
+ 1. Already deployed component has version:7.3005.20110929162215.0000+
How can I deploy in Portal 7.30 an older version of "com.sap.portal.navigation.masthead.par" ?
Thx!
M.
Edited by: ALL NEW Arinso on Nov 17, 2011 12:54 PMHi Detlev,
Thanks so much for your reply. Regarding "Create Portal Archive (EAR File)" everything is understood, thanks! In NWDS 7.3 everything must be deployed via .ear file
Regarding the libs... yes, of course I know I compile the sources against some libs Then, I'm gonna type it an example:
- NWDS 7.0 > import com.sap.portal.navigation.masthead.par
Everything is ok and working. Now, the same in 7.3:
- NWDS 7.30 > import com.sap.portal.navigation.masthead.par > LogInRedirect.jsp > exactly the same code as NWDS 7.0 (of course), but with errors in lines:
<%@ page import = "com.sapportals.portal.navigation.*" %> >>> The import com.sapportals.portal.navigation cannot be resolved
<%@ page import = "com.sapportals.portal.prt.runtime.PortalRuntime" %> >>> this is resolved correctly into SAP_EP\resources\prtapi.jar
I understand I must to add the corresponding libs for "com.sapportals.portal.navigation.*" to be used... but how I could know which one and where is located? I hope I'm explaining myself clear...
Thx!!
M.
Edited by: All NorthgateArinso on Nov 23, 2011 4:47 PM -
Portal Runtime Error for "com.sap.portal.toolAreaiView"
Hi EP Gurus,
We are using EP6 SP11 Patch3 installed on UNIX and Windows machine as well.
We are getting following error message:
Portal Runtime Error
An exception occurred while processing a request for :
iView : pcd:portal_content/com.lti.I-1192_fldr_01/
com.lti.I-1192_fldr_17/I-1192_desktop/
frameworkPages/frameworkpage/com.sap.portal.toolAreaiView
Component Name : com.sap.portal.navigation.toolarea.default
Each time when we got this message we have to restart the j2ee engine and then everything works fine.
Also we are facing this problem on UNIX machine only(not on windows)
Can anybody help me out with this?
With regards,
AmolHi Dieter,
Thanks for the reply...........
But the log files are not getting generated(which did generate earlier), i dont know whats the problem.
If u can plz help me....
With regards,
Amol. -
This is a bit embarrassing to admit but I had some serious finger trouble here and managed to deploy a new par file with name com.sap.portal.support.browse.par. This of course fu..ed up my browsing functionality in the support area and I need to deploy the original.
I tried to find it in my production portal, but I can't seem to be able to find the right location to download it from. Can anyone help.
I am on portal 7.0 sps 15.
HenningHi,
You can find com.sap.portal.support.browse.par par at ROOT/WEB-INF/deployment/temp on the portal production server. Then you can deploy it to the development system.
Regards,
Nikhil -
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. -
Create custom com.sap.portal.layouts.framework to allow google index
Hello experts,
I can't create a full .par from a copy of the com.sap.portal.layouts.framework component because when I create the .par for upload it in the portal, this .par file just includes the portalapp.xml. I don't know if there is a restriction in the portalapp.xml, so that the .jsp files are not exported to the par file?
I haven't changed the portalapp.xml, just deleted the components for the layouts that I donu2019t need to modify
<?xml version="1.0" encoding="UTF-8"?>
<application>
<!--THIS FILE IS A COPY OF THE ORIGINAL VERSION STORED IN THE PCD. PLEASE DO NOT CHANGE IT!-->
<application-config>
<property name="Vendor" value="sap.com"/>
<property name="SecurityArea" value="NetWeaver.Portal"/>
<property name="SharingReference" value="com.sap.portal.htmlb,com.sap.portal.themes.lafservice,com.sap.portal.useragent,com.sap.portal.pagebuilder"/>
</application-config>
<components>
<component name="framework">
<component-config>
<property name="ClassName" value="com.sapportals.portal.pb.layout.PageLayout"/>
<property name="ResourceBundleName" value="pagebuilder_nls"/>
<property name="SafetyLevel" value="no_safety"/>
</component-config>
<component-profile>
<property name="ComponentType" value="com.sapportals.portal.layout"/>
<property name="com.sap.portal.pcm.Title" value="Framework Layout"/>
<property name="com.sap.portal.pcm.Description" value="Layout displaying one full-width column that encompasses the entire portal desktop and contains scripts"/>
<property name="com.sap.portal.reserved.layout.TagLibLayout" value="/SERVICE/com.sap.portal.pagebuilder/taglib/layout.tld"/>
<property name="com.sap.portal.reserved.layout.TagLibHtmlb" value="/SERVICE/com.sap.portal.htmlb/taglib/htmlb.tld "/>
<property name="com.sap.portal.reserved.layout.TemplateFile" value="framework.jsp"/>
<property name="AuthScheme" value="anonymous"/>
<property name="com.sap.portal.reserved.layout.Cont1" value="frameworkColumn">
<property name="title" value="Framework Column"/>
<property name="orientation" value="vertical"/>
<property name="designClass" value="prtlHeaderCon"/>
</property>
</component-profile>
</component>
<component name="light_framework">
<component-config>
<property name="ClassName" value="com.sapportals.portal.pb.layout.PageLayout"/>
<property name="ResourceBundleName" value="pagebuilder_nls"/>
<property name="SafetyLevel" value="no_safety"/>
</component-config>
<component-profile>
<property name="EPCFLevel" value="0"/>
<property name="ComponentType" value="com.sapportals.portal.layout"/>
<property name="com.sap.portal.pcm.Title" value="Framework Layout"/>
<property name="com.sap.portal.pcm.Description" value="Layout displaying one full-width column that encompasses the entire portal desktop and contains scripts"/>
<property name="com.sap.portal.reserved.layout.TagLibLayout" value="/SERVICE/com.sap.portal.pagebuilder/taglib/layout.tld"/>
<property name="com.sap.portal.reserved.layout.TagLibHtmlb" value="/SERVICE/com.sap.portal.htmlb/taglib/htmlb.tld "/>
<property name="com.sap.portal.reserved.layout.TemplateFile" value="light_framework.jsp"/>
<property name="AuthScheme" value="anonymous"/>
<property name="com.sap.portal.reserved.layout.Cont1" value="frameworkColumn">
<property name="title" value="Framework Column"/>
<property name="orientation" value="vertical"/>
<property name="designClass" value="prtlHeaderCon"/>
</property>
</component-profile>
</component>
</components>
<services/>
</application>I'm trying to do the follow change in framework.jsp so that google can correctly index a external facing portal:
I allready consider the following links:
Note 933452
http://help.sap.com/saphelp_nw70/helpdata/en/44/ccf6bf687f3b9ae10000000a1553f6/frameset.htm
Re: EP and search engine
Re: Portal Page Header <HEAD> Keywords & Title
Re: EP and search engine
Re: New Framework Page From PAR File
Creating framework page from new jsp-file
Any advice will be very helpful
Best Regards,
Ernesto Serrano -
Portal Event name and namespace (ECM)
Hi Experts
I want to register for the Portal Event that gets triggered when an employee is selected.
In the Compensation Information page, there is an employee search iview. I need to know what Portal Event name and namespace is triggered when an employee is selected.
Does somebody already know what the name and namespace is?
thanks in advance
Anton KruseFound the solution here: Parameter Passing from WDJ iview to WDABAP Iview
call function 'HR_ASR_WDA_GET_EMPLOYEE'
exporting
id = 'MSS01' "ABAP Memory ID To get the PERNR Selected.
importing
pernr = gv_pernr. -
Technical folder names in my SAP Portal
Hi Security Experts,
We have an issue wherein user has Technical folder names visible in his SAP Portal page.
Please advice if we can disable that.
PeeyushGive more specifics, please.
Is this happening only for one user ? Which application ? Did you try clearing Cache / CTRL + F5 (Hard Refresh)
Did you compare permissions with another user who doesnt have this issue ?
Have seen similar issue after Portal EPA file import under an existing PCD folder structure. -
Server Names exposed while accessing SAP Portal
We are using FireFox browser to access the SAP Portal application.We are running SAP EnterPrise Portal on NW 7.01. Our Production SAP portal is exposed to
internet.
After the users log into the system, using Firefox browser, the server name is seen in the status bar of the
browser. This is a security threat, as the server names are exposed.
This issue is not there if we access the sameusing Internet explorer.Abdul,
See this:
http://help.sap.com/saphelp_nw04s/helpdata/en/b6/8b9aea8d7c11d5bdd8006094191908/frameset.htm
The suspect is "User Mapping Type". It is probably set to "admin", instead of "admin, user". That is why you do not see the system when logged in as one of the users.
Also make sure users have permissions in PCD to the system.
If does not help, check other suspect as SAP help suggests:
The selected principal does not have end-user permissions for the system.
The system's logon method does not require any user mapping data for the system (such as "SAPLogonTicket" for a system that is not the SAP reference system).
The system's user mapping type is not set correctly or not set at all.
There is no system alias defined for the system.
There is no system landscape registered, for example, the one contained in Enterprise Portal.
Regards,
Slava -
Create SSO on SAP portal to ECC 6.0 EHP4 backend
Hello,
I want to create a SSO connection form my SAP Portal server to my ECC 6.0 EHP4 Backend system.
My JAVA Portal is installed on the same system as the ECC 6.0 backend system.
For the configuration I follow the steps as described in the document: http://www.sap-img.com/basis/configure-the-sso-single-sign-on-for-portal.htm.
At point 5.3 I have to set the Backend System as "ACL" in the Portal. So Iu2019m still in the Visual administrator from point 5.2 but now I go to the path Server --> Services --> Security Provider --> Ticket.
Here I choose the authentication tab and want to add the com.sap.security.core.server.jass.EvaluateTicketLoginModule. Buth when I press the Add button I get a list of available login members. In this list there is no com.sap.security.core.server.jass.EvaluateTicketLoginModule login module available. Does someone know what Iu2019m doing wrong or how I could add the correct login module?
I attach a screen shot from Visual administrator.
Kind regards,
Richard Meijn
Edited by: Richard Meijn on Aug 10, 2011 8:20 AMCahtal,
Thanks for you quick reaction but it's not all clear for me. So could you explain it a little bit more detailed fo me.
If I write something wrong please correct me. I understand the following
So If I am on the "Authentication" tab I press the Add new button
In the list which shows up I select the u201CEvaluateTicketLoginModuleu201D
Here I change the name and option value to trustedsys01=<PORTAL_SID>, <PORTAL_CLIENT>
Kind regards,
Richard Meijn
Maybe you are looking for
-
Error in updating 311 movement using BAPI_GOODSMVT_CREATE
Hi All, I need hlep to understand the problem in doing a transfer. SAP MII is doing a 311 type movement using BAPI_GOODSMVT_CREATE. BAPI is returning the response back to MII. Once the BAPI is commited it shall make transfer inside SAP. But it does n
-
Print profiles no longer working correctly with CS6 64bit to my Epson R2880
Hi, until recently, my print profiles were working correctly with CS6 64bit (Win 7 ultimate 64) to my Epson R2880, they now print washed out/desaturated but the same profiles still print correctly using Lightroom 4. has there been an update that c
-
Hello to all, there are two confliting articles about this topic: 1- http://technet.microsoft.com/en-us/library/upgrade-domain-controllers-to-windows-server-2008-r2(v=ws.10).aspx#BKMK_Whatsnew : this one says that it does not work "The Group Ch
-
Broken Microphone & Dock Connector
Ok i was in the middle of a call on friday, and put the phone down to enoy a ncie meal, rang my mate back and he couldn't here me so i tried again, and still nothing, was really shouting and he couldn't here me, so i rang lots of other mobiles and my
-
CUCIMOC Caller-ID from Outlook Address Book
Hi Everyone, Does anyone know if it is possible to get CUCIMOC to look up the Outlook Address book of a user so that when an incoming call comes through you can see the callers name on the screen pop ? I have looked for some information on this but I