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 file

Yes 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

Similar Messages

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 file

User 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

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.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

How to restrice ananymous user access to portal link /irj/servlet/prt/portal/prtroot/com.sap.portal.navigation.portallauncher.default?

Hi experts,
We had an issue with portal access. I wonder if portal is venerable for security threats?
Could you please let me how to restrict the unauthorized users (anonymous user) to the portal URL.
https://HOST:50001//irj/servlet/prt/portal/prtroot/com.sap.portal.navigation.portallauncher.default .
Appreciate your help.
Regards
Maruti

Hi Maruti,
Hope you are doing good.
Can't you just amend the portal permissions so that this access is not possible.
The PCD location should be:
com.sap.portal.system/security/sap.com/NetWeaver.Portal/no_safety/com.sap.portal.navigation.portallauncher....
Hope this helps.
Thank you and have a nice day!
Kind Regards,
Hemanth

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)

Failed to start dependent service com.sap.portal.usermapping

Hi
I am trying to retrieve the User mapping information from my Webdynpro application. I added PORTAL:sap.com/com.sap.portal.usermapping to my service references in the web dynpro application. However, I am getting an error while deploying the application. The error message says
Failed to start dependent service ''com.sap.portal.usermapping'' of application ''local/materialtemplateapp''. Status of dependent component: STATUS_MISSING. Hint: Is the component deployed correctly on the engine?
I know this is a pretty old problem that many other Web Dynpro developers encountered. I searched a lot on the forums and SDN. There are similar posts but I didn't find solution. I would appreciate any help in fixing this problem.
Thanks

Hi,
Goto http://<servername>:<port>/webdynpro/welcome-->content Adminsitration
Now, expand sap.com and search for the usermapping service. Check what is the status of that particular service. If its in the stopped state then start it and try redeploying your application.
Regards,
Murtuza

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

Can't See com.sap.portal.runtime.logon in list of PAR Files in Iview Wizard

Hello All,
I am trying to create an iview from PAR file com.sap.portal.runtime.logon which is the logon par file that has the logon page. But when I right click a folder in the PCD and click on New From PAR Iview I try to find on the list of available par files and I don't find the one named com.sap.portal.runtime.logon
Can anyone tell me if this has to do with the portalapp.xml file from com.sap.porta.runtime.logon.par file.? or with the Security Zones defined in portalapp.xml? Or does someone know why this PAR file doesn't appear on the list and how can I make it appear on this list of par files?
Any helpful ideas to solve this issue will give rewarding points.
Thanks
Luis

Hello,
What I want to do is to put the logon page in the light framework page so that the users can login from the anonymous portal. After I customize the logon page I want to create aniview in the detailed navigation.
If you want to see the jsp files that the com.sap.portal.runtime.logon.par file you have to go to the file system and copy the .par.bak file , rename it to .zip and all the files are there.
But my question is if this is a par file that is deployed in the portal , why I cant create an iview from this par file? From other forums I have read they say that creating an iview from this par file it will put the logon page where you want. But when I try to create an iview from PAR File the com.sap.portal.runtime.logon doesn't appear in the list of available par files.
Please help me on this and will give rewarding points.
Thanks
Luis

Access denied (Object: com.sap.portal.system/security/no_safety)

We are implementing EP 6.0, currently with SP11. We have developed some iViews, which are using RFC functions to get information from backend system, in this case SRM.
Everything worked fine, till the day weve transported those developments into other systems (production and testing systems). We are getting the following error Access denied (Object: com.sap.portal.system/security/no_safety). This error only comes out if the iView is called from inside another one, if called isolated it works fine.
Does any one have any idea about how to solve this?

Hi AA, you can find in the log file in order to identify what is the object that you need to add in the security zone.
You can find information for the security zones on:
http://help.sap.com/saphelp_nw04/helpdata/en/25/85de55a94c4b5fa7a2d74e8ed201b0/content.htm
Regards.

Cannot find the class file for com.sap.portal.services.api.connectorgateway

Hi,
I was trying the "How to BI JAVA SDK in a Portal iView and get the following error.
The project was not built since its classpath is incomplete. Cannot find the class file for com.sap.portal.services.api.connectorgateway.IConnectorGatewayService. Fix the classpath and try rebuilding this project.
I have the following in my portalapp.xml file
<property name="SharingReference" value="com.sap.portal.ivs.connectorservice"/>
and i have also added the jar file "com.sap.portal.ivs.connectorservice_api" in the set of lib's
Has some faced a similar issue? or can someone suggest how I could possibly resolve this.
Thanks,
Smitha

Hi Smitha:
My webdynpro dc was build failed for "This compilation unit indirectly references the missing type com.sap.engine.services.webservices.espbase.client.dynamic.content.GenericObject (typically some required class file is referencing a type outside the classpath)".
How should i do? Thank you!

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

IViewTrayColor and com.sap.portal.iview.family

I am looking to do a custom layout to control the tray colour of an iView and folowing the documentation (http://help.sap.com/saphelp_nw04/helpdata/en/43/6dfbbbac847100e10000000a1553f7/frameset.htm) on creating a custom layout it mentions to go to the default_iView in the core objects and look at the com.sap.portal.iview.family attribute.
The issue is I can not find this attribute in either the standard iView dislpay editor of the PCD editor.
We are running Portal 6 6.40 SP15...
Does anyone know where to set this value??
Cheers,
D.

Hi Derek,
I don't have any SPS15 at hand, but on the first SPS16 I checked the attributed is to be found at exactly the place described on help.sap.com (it's name is "Family", the technical name is as described).
Re-check, otherwise consider patching.
Hope it helps
Detlev

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,

Portal runtime error : com.sap.portal.pcm.Title

Hi All
I have the problem in the Portal , in time whe I open the portal y all tabs there are this message:
Portal runtime error.
An exception occurred while processing your request. Send the exception ID to your portal administrator.
Exception ID: 12:29_12/02/09_2357150
Refer to the log file for details about this exception.
And I found this information in the logs
Caused by: com.sapportals.portal.prt.core.broker.PortalComponentInstantiationException: Could not instantiate implementation class com.sapportals.portal.navigation.CollaborationNavTree of Portal Component com.sap.netweaver.coll.appl.ui.room.CollaborationDetailedNavigation because: Could not instantiate implementation class
     at com.sapportals.portal.prt.core.broker.PortalComponentItemFacade.getInstanceInternal(PortalComponentItemFacade.java:269)
     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)
     ... 35 more
Caused by: com.sapportals.portal.prt.core.broker.PortalApplicationNotFoundException: Could not find portal application com.sap.portal.activityreportingframework
     at com.sapportals.portal.prt.core.broker.PortalApplicationItem.prepare(PortalApplicationItem.java:415)
     at com.sapportals.portal.prt.core.broker.PortalApplicationItem.prepare(PortalApplicationItem.java:387)
     at com.sapportals.portal.prt.core.broker.PortalApplicationItem.prepare(PortalApplicationItem.java:387)
     at com.sapportals.portal.prt.core.broker.PortalApplicationItem.prepare(PortalApplicationItem.java:387)
     at com.sapportals.portal.prt.core.broker.PortalApplicationItem._refresh(PortalApplicationItem.java:507)
     at com.sapportals.portal.prt.core.broker.PortalApplicationItem.getCoreLoader(PortalApplicationItem.java:1360)
     at com.sapportals.portal.prt.core.broker.PortalComponentItem.getClassLoader(PortalComponentItem.java:569)
     at com.sapportals.portal.prt.core.broker.PortalComponentItemFacade.getClassLoader(PortalComponentItemFacade.java:102)
     at com.sapportals.portal.prt.core.broker.PortalComponentItemFacade.getInstanceInternal(PortalComponentItemFacade.java:228)
     ... 39 more
And in this time I have a problem in deployment the EP server SP16.
I don't Know What's the problem exactly??
thanks
Danny

Hi Shrikant thanks for your answer
I solved this problem with these notes:
Activity Data Collector on NW04
SAP Note Number: 1178889
Activity Data Collector stops generating files
SAP Note Number: 1251041
Thanks I will hope this help someone
Danny

SolMan in Portal - com.sap.portal.epsolman.EPSolman

Similar Messages

Maybe you are looking for