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

Similar Messages

  • Portal Runtime Error - com.sapportals.portal.appintegrator.ApplicationIntegratorException: Unknown system alias.

    Hi Experts,
    Can anyone please help me on the below Portal Runtime Exception.
    10:59_26/08/14_0043_3937250
    [EXCEPTION]
    com.sapportals.portal.appintegrator.ApplicationIntegratorException: Unknown system alias.
    System Alias:  'SAP_BW',
    User:          'Test',
    Reason:        System Alias is not defined or permission denied for this user
    at com.sapportals.portal.appintegrator.accessor.system.LocalSystemAccessor.<init>(LocalSystemAccessor.java:60)
    at com.sapportals.portal.appintegrator.accessor.system.SystemAccessorFactory$Decider.getAccessor(SystemAccessorFactory.java:178)
    at com.sapportals.portal.appintegrator.accessor.system.SystemAccessorFactory$Decider.getSystemAccessor(SystemAccessorFactory.java:123)
    at com.sapportals.portal.appintegrator.accessor.system.SystemAccessorFactory.getSystemAccessor(SystemAccessorFactory.java:52)
    at com.sapportals.portal.appintegrator.layer.AbstractIntegrationLayer.getLocalOrRemote(AbstractIntegrationLayer.java:624)
    at com.sapportals.portal.appintegrator.layer.TopLayerSwitch.mustRedirectToProducer(TopLayerSwitch.java:105)
    at com.sapportals.portal.appintegrator.layer.TopLayerSwitch.getNextLayer(TopLayerSwitch.java:75)
    at com.sapportals.portal.appintegrator.LayerProcessor.getNextLayer(LayerProcessor.java:293)
    at com.sapportals.portal.appintegrator.LayerProcessor.processActionPass(LayerProcessor.java:183)
    at com.sapportals.portal.appintegrator.AbstractIntegratorComponent.doActionPass(AbstractIntegratorComponent.java:111)
    at com.sapportals.portal.appintegrator.AbstractIntegratorComponent.doOnPOMReady(AbstractIntegratorComponent.java:70)
    at com.sapportals.portal.prt.component.AbstractPortalComponent.handleEvent(AbstractPortalComponent.java:398)
    at com.sap.portal.prt.core.RequestDispatcherFactory$PortalComponentRequestDispatcher$1.service(RequestDispatcherFactory.java:168)
    at com.sap.engine.services.servlets_jsp.server.deploy.impl.module.IRequestDispatcherImpl.dispatch(IRequestDispatcherImpl.java:270)
    at com.sap.portal.prt.core.RequestDispatcherFactory$PortalComponentRequestDispatcher.handleEvent(RequestDispatcherFactory.java:158)
    at com.sap.portal.prt.pom.ComponentNode.handleEvent(ComponentNode.java:242)
    at com.sap.portal.prt.pom.PortalNode.fireEventOnNode(PortalNode.java:342)
    at com.sap.portal.prt.pom.PortalNode.processEventQueue(PortalNode.java:732)
    at com.sap.portal.prt.core.PortalRequestManager.runRequestCycle(PortalRequestManager.java:473)
    at com.sapportals.portal.prt.connection.ServletConnection.handleRequest(ServletConnection.java:202)
    at com.sap.portal.prt.dispatcher.DispatcherServlet.service(DispatcherServlet.java:132)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:847)
    at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.runServlet(FilterChainImpl.java:202)
    at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.doFilter(FilterChainImpl.java:103)
    at com.sap.portal.http.EnrichNavRequestFilter.doFilter(EnrichNavRequestFilter.java:49)
    at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.doFilter(FilterChainImpl.java:79)
    at com.sap.portal.prt.dispatcher.CustomHeaderFilter.doFilter(CustomHeaderFilter.java:58)
    at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.doFilter(FilterChainImpl.java:79)
    at com.sap.portal.http.EnrichNavRequestFilter.doFilter(EnrichNavRequestFilter.java:49)
    at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.doFilter(FilterChainImpl.java:79)
    at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:432)
    at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:210)
    at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:441)
    at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:430)
    at com.sap.engine.services.servlets_jsp.filters.DSRWebContainerFilter.process(DSRWebContainerFilter.java:38)
    at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
    at com.sap.engine.services.servlets_jsp.filters.ServletSelector.process(ServletSelector.java:81)
    at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
    at com.sap.engine.services.servlets_jsp.filters.ApplicationSelector.process(ApplicationSelector.java:278)
    at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
    at com.sap.engine.services.httpserver.filters.WebContainerInvoker.process(WebContainerInvoker.java:81)
    at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)
    at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
    at com.sap.engine.services.httpserver.filters.ResponseLogWriter.process(ResponseLogWriter.java:60)
    at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)
    at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
    at com.sap.engine.services.httpserver.filters.DefineHostFilter.process(DefineHostFilter.java:27)
    at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
    at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
    at com.sap.engine.services.httpserver.filters.MonitoringFilter.process(MonitoringFilter.java:29)
    at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
    at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
    at com.sap.engine.services.httpserver.filters.SessionSizeFilter.process(SessionSizeFilter.java:26)
    at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
    at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
    at com.sap.engine.services.httpserver.filters.MemoryStatisticFilter.process(MemoryStatisticFilter.java:57)
    at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
    at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
    at com.sap.engine.services.httpserver.filters.DSRHttpFilter.process(DSRHttpFilter.java:43)
    at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
    at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
    at com.sap.engine.services.httpserver.server.Processor.chainedRequest(Processor.java:475)
    at com.sap.engine.services.httpserver.server.Processor$FCAProcessorThread.process(Processor.java:269)
    at com.sap.engine.services.httpserver.server.rcm.RequestProcessorThread.run(RequestProcessorThread.java:56)
    at com.sap.engine.core.thread.execution.Executable.run(Executable.java:122)
    at com.sap.engine.core.thread.execution.Executable.run(Executable.java:101)
    at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:328)

    Hi Jelbin,
    Following is the solution of this error,
    Step 1: Check the system alias in application which you are opening and maintain same in system object also, or take system object default system alias and maintain it in iView property named as "System", either of above is valid.
    Step 2: Add every One group to the system object with end user ticked.
    Step 3: Logoff and login again it should work,
    Kindly reply if this works.
    Regards,
    Bhavin Anajwala

  • HT204291 i have a late 2011 macbook pro and i don't have the airplay icon on my menu. Everything is on the same network and i have a black mini apple Tv. it is either 2nd or 3rd generation. The airplay icon comes up in itunes it doesn't works with video j

    i have a late 2011 macbook pro and i don't have the airplay icon on my menu. Everything is on the same network and i have a black mini apple Tv. it is either 2nd or 3rd generation. The airplay icon comes up in itunes it doesn't works with video just music. I want to mirror it on my apple tv. Will you please help me?

    That's why, you will need to upgrade to 10.8

  • Help with Apache Reverse Proxy configuration with SAP Portal and SAP Webgui

    Dear Experts,
    I have an issue configuring Apache to work with SAP Portal and ERP webgui. Accessing Portal through Reverse Proxy is working fine. But the problem arises when we try to open an iView ERP webgui transaction page from Portal with the Reverse Proxy. Have anyone implemented similar requirements and could advice on the configuration required on the Apache side? Thank you

    hi,
    pls check the below links for reference:
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/24396589-0a01-0010-3c8c-ab2e3acf6fe2
    searchsap.techtarget.com/searchSAP/downloads/chapter-december.pdf
    1)Learn to implement the reverse proxy filter and portal gateway in SAP Enterprise Portal 6.0 on Web Application Server 6.40.
    https:/.../irj/sdn/nw-portalandcollaboration?rid=/webcontent/uuid/006efe7b-1b73-2910-c4ae-f45aa408da5b
    .2 )Configuring the Portal for Your Reverse Proxy Filter Solution . ... This document describes the reverse proxy filter mechanism in SAP Enterprise ...
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/32ad9b90-0201-0010-3c8a-c900cd685f8f
    3)have full reverse proxy functionality. Possibly. filter. requests. Internet ... Reverse proxy (optionally with authentication etc.) ...
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/c066c390-0201-0010-3cba-cd42dfbcc8be
    Note:please reward points if solution found helpfull
    Regards
    Chandrakanth.k

  • Open a QueryView from Portal in SAP Analyzer

    Hey guys,
    I have a Query Q1 and a view V_Q1 which was created in SAP Analyzer 7.0.  I know how to publish V_Q1 to Portal, see
    http://help.sap.com/saphelp_nw70/helpdata/en/33/39fa40ee14f26fe10000000a1550b0/content.htm
    But using the tecnique above, V_Q1 always opens in Web Analyzer, but I want to get V_Q1 to be opened in SAP Analyzer.
    I already achieved to publish Q1 to Portal and to be opened in SAP Analyser (using codelink com.sap.portal.appintegrator.sap.Transaction with Parameter QUERY=Q1 and Parameter SAP-GUI-Type = SAP Gui for Windows).
    But how to publish V_Q1 to Portal and to be opened in SAP Analyzer.
    All hints are helpful....
    Cheers,
    Christian

    Hi Krishnan,
    thank you for your response.
    I created the View in BEx. I still can open the query view from BEx. I am able to open the query from Portal. From that config; i tried to change the iView in Portal, so that it opens the query view. But it isn't working. BEx is just opening blank.
    I recognized, that there is also a parameter "Dynamic parameters" which seems to be important. Nevertheless, I didn't managed to open the query from from portal.
    Do you have a working config?
    Rgds,
    Christian

  • SAPGUI iview from SAP Portal = create new session  results in empty screen

    we use ep700 sp10 and sapgui 6.40 compilation 5 . we have a sapgui iview which starts the login to the R/3 system and shows the user menu with some transactions.
    if the user now creates a new session  with the buttom "create new session" in the sapgui screen he gets a new but empty session  ==> i expected , that he gets the normal sap entry screen with the user and sap menu.
    does anybody now how to get that ?
    many thanks hannes toefferl

    Hi,
    Go to the file .../irj/root/WEB-INF/portal/portalapps/com.sap.portal.appintegrator.sap/property/Transaction/WinGuiRenderLayer.properties
    In this file, change -wp=true to -wp=false and also Workplace=true to Workplace=false.
    Restart the portal for the change to take effect.
    Hope this helps.
    Cheers,
    Sunil
    PS: Reward points for helpful answers.

  • Alternative for integrating Portal to Sap Webwas 6.20 (without ITS)

    Hello
    I have a scenario which I should open SAP Transactions from Uwl tasks in Portal, without ITS (as sap Webwas doesnt have embedded ITS).
    I get the following error:
    iView : pcd:portal_content/every_user/general/uwl/com.sap.netweaver.bc.uwl.uwlSapLaunch
    Nome de componente : com.sap.portal.appintegrator.sap.Transaction
    Exception in SAP Application Integrator occured: Application URL ':///sap(ZT01VUxMbEJHNHpWWUIzVyUyQjRZWm5lWnclM0QlM0R1NjYlMkZzcklXQ3Z4WXJPV3g5OXVvVnclM0QlM0Q=)/bc/gui/sap/its/webgui' is not valid! Please check the protocol and host entries for system 'R3_SYSTEM'..
    Is there any alternative for accessing the SAP Transactions in UWL without ITS?
    I tried to change the Uwl XML to call a custom view, but nothing has changed, the result is the same. I changed from:
        <ItemType name="uwl.task.webflow.TS01000096.R3_SYSTEM" connector="WebFlowConnector" defaultView="DefaultView" defaultAction="launchSAPAction" executionMode="default">
          <ItemTypeCriteria systemId="R3_SYSTEM" externalType="TS01000096" connector="WebFlowConnector"/>
          <Actions>
            <Action name="launchSAPAction" groupAction="" handler="SAPIACLauncher" returnToDetailViewAllowed="yes" launchInNewWindow="yes" launchNewWindowFeatures="resizable=yes,scrollbars=yes,status=yes,toolbar=no,menubar=no,location=no,directories=no">
              <Properties>
                <Property name="newWindowFeatures" value="resizable=yes,scrollbars=yes,status=yes,toolbar=no,menubar=no,location=no,directories=no"/>
                <Property name="openInNewWindow" value="yes"/>
                <Property name="display_order_priority" value="5"/>
                <Property name="IAC" value="WS01000060"/>
              </Properties>
              <Descriptions default=""/>
            </Action>
          </Actions>
        </ItemType>
    To:
              <ItemType name="uwl.task.webflow.TS90300030.R3_SYSTEM" connector="WebFlowConnector" defaultView="DefaultView" defaultAction="launchIView" executionMode="default">
                   <ItemTypeCriteria systemId="R3_SYSTEM" externalType="TS90300030" connector="WebFlowConnector"/>
                   <Actions>
                        <Action name="launchIView" handler="IViewLauncher">
                             <Properties>
                                  <Property name="iview" value="pcd:portal_content/myISRDispatcher"/>
                                  <Property name="openInNewWindow" value="yes"/>
                             </Properties>
                             <Descriptions default="launchIView"/>
                        </Action>
                   </Actions>
              </ItemType>
    Thanks

    Hi Vitor,
    This is not possible.
    If you want to call backend transactions you will need to use the ITS: ITS 6.20 for backend releases with kernel 6.20 (and lower) or the Integrated ITS with kernel >= 6.40. SAP notes 709038 and 325616 can give you more information.
    Best regards,
    Cristiano

  • Com.sapportals.portal.prt.runtime.PortalRuntimeException: Exception in SAP

    Hi All,
    I am configuring SSO between EP7 and SRM 7.0
    1) I have created a SRM system in EP system connections works fine with logon ticket.
    2) I have uploaded roles from SRM system
    but content from these roles throws following exception
    Although i have SAP_SRM as system name exception shows System:    &amp;#39;SAP_LocalSystem&amp;#39;,
    what is the root cause for this exception.
    Full Message Text
    12:07_02/04/09_0188_7992050
    [EXCEPTION]
    com.sapportals.portal.prt.runtime.PortalRuntimeException: Exception in SAP Application Integrator occured: Unable to parse template '&lt;System.Access.ITS.protocol&gt;://&lt;System.Access.ITS.hostname&gt;/sap&lt;ESID&gt;/bc/gui/sap/its/&lt;IAC[SAP_ITS_NAMESPACE]&gt;?sap-client=&lt;System.client&gt;&amp;sap-language=&lt;Request.Language&gt;&amp;sap-accessibility=&lt;User.Accessibility[SAP_BOOL]&gt;&amp;DisconnectOnClose=0&amp;DesignBaseUrl=&lt;LAF.BaseUrl[url_ENCODE]&gt;&amp;~design=&lt;LAF.Theme[url_ENCODE]&gt;&amp;&lt;Authentication&gt;&amp;&lt;DynamicParameter[PARAMETER_MAPPING PROCESS_RECURSIVE]&gt;&amp;&lt;ForwardParameters[QUERYSTRING]&gt;&amp;&lt;ApplicationParameter[PROCESS_RECURSIVE]&gt;'; the problem occured at position 121. Cannot process expression &lt;System.client&gt; because Invalid System Attribute:
    System:    &amp;#39;SAP_LocalSystem&amp;#39;,
    Attribute: &amp;#39;client&amp;#39;.
    at com.sapportals.portal.appintegrator.AbstractIntegratorComponent.doContentPass(AbstractIntegratorComponent.java:123)
    at com.sapportals.portal.appintegrator.AbstractIntegratorComponent.doContent(AbstractIntegratorComponent.java:98)
    at com.sapportals.portal.prt.component.AbstractPortalComponent.serviceDeprecated(AbstractPortalComponent.java:209)
    at com.sapportals.portal.prt.component.AbstractPortalComponent.service(AbstractPortalComponent.java:114)
    at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)
    at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)
    at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)
    at com.sapportals.portal.prt.component.PortalComponentResponse.include(PortalComponentResponse.java:215)
    at com.sapportals.portal.sapapplication.bwc.AbstractBWCComponent.doContent(AbstractBWCComponent.java:68)
    at com.sapportals.portal.prt.component.AbstractPortalComponent.serviceDeprecated(AbstractPortalComponent.java:209)
    at com.sapportals.portal.prt.component.AbstractPortalComponent.service(AbstractPortalComponent.java:114)
    at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)
    at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)
    at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)
    at com.sapportals.portal.prt.component.PortalComponentResponse.include(PortalComponentResponse.java:215)
    at com.sapportals.portal.prt.pom.PortalNode.service(PortalNode.java:645)
    at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)
    at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)
    at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)
    at com.sapportals.portal.prt.core.PortalRequestManager.runRequestCycle(PortalRequestManager.java:753)
    at com.sapportals.portal.prt.connection.ServletConnection.handleRequest(ServletConnection.java:240)
    at com.sapportals.portal.prt.dispatcher.Dispatcher$doService.run(Dispatcher.java:523)
    at java.security.AccessController.doPrivileged(Native Method)
    at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:412)
    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: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:1039)
    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)
    Regards,
    Murali

    Hi Murali,
    First of all activate the integrated ITS on backend system , follow the below link to do so
    www.arlati.ch/knowhow/archive/Integrated_ITS_WebGui.pdf
    In EP where you have created SRM system , there you have to maintain the ITS defination and test the ITS defination.
    Also Check the permission of the SRM system which you have created.
    Thanks
    Anil

  • Location of com.sap.portal.dsm.par in SP23 of NW2004

    Hi all,
    For an issue discovered in SP22(SAP Note 1235253), SAP has provided a work around. Thats to take a file com.sap.portal.dsm.par from SP23 and deploy using SDM.
    But i am not sure in which SDA/SCA this particular file is present.
    Please let me know the SDA/SCA file where i can find com.sap.portal.dsm.par.
    Regards
    Venkatesh

    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

  • 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

  • SAP Portal accunts with special characters fail on reconcile

    We connect to the SAP Portal System via the com.waveset.adapter.SAPPortalResourceAdapter in an IDM 8.0.0.5 system.
    On the SAP side the IDMService.par is running.
    When we do a reconcile we fail with an error message.
    We activated the error logging on SAP system and the logfile on SAP and IDM reads like this:
    #com.sap.portal.idm_logger#sap.com/irj#com.sap.portal.idm_logger
    #CPIC_IDM_EP#
    #Info##Plain###got user with uniqueId USER.PRIVATE_DATASOURCE.un:k&Atilde;&para;hler#
    It looks very much like a character set problem but in which system?
    Does anyone have a hint for me on how to configure SAP so that we get:
    - more detailed information on the root cause of the problem. e.g. enable a more detailed logging on SAP*
    - SAP to send UTF-8 encoded data only.
    Does anybody had a problem like this before? It would help if we would know that we are not alone :-)
    Any help is very much apprechated !
    Ugato

    We got an E-Fix and its working now.

  • SAP Portal Runtime Error

    I have been receiving the error below.
    Error Message: SAP Portal|Runtime|Errors|com.sapportals.portal.appintegrator.template_processor.context.ContextException: com.sapportals.portal.appintegrator.template_processor.context.ContextException: Invalid System Attribute: System: 'SAP_LocalSystem', Attribute: 'isABAPSecuritySessionsEnabled'. 

    Hi,
    Please go through the below SAP Note and see if that helps:
    1583111 - Application Integrator Exception for SAP_LocalSystem, Even Though Different System Specified in iView
    BR,
    Anurag

  • I have error while testing the system created from a sap business objects template in SAP portal

    I have error while testing the system created from a sap business objects template in SAP portal. Error text:
    com.sapportals.connector.connection.ConnectionFailedException: Connection Failed: A nested exception occurred. Could not initialize physical connection. Connection Failed: A nested exception occurred. Could not initialize physical connection. Connection Failed: A nested exception occurred. Could not create JCO connection. 'mshost' missing
    I configure integration SAP portal and SAP BW system. All system requirements are complied.
    Environment
    SAP Business Objects 4.0
    SAP BW 7.31
    1.     I configure SSSO between SAP BW and SAP Business Objects Enterprise 4.0
    2.     Next I setting integration SAP PORTAL with SAP BW system
    3.     I download certificate from portal. Select Certificates and key (http://sapserver:port/nwa) – See scren_
    4.     In next window selected Ticketkeystore and Saplogonticketpair-cert( near part window form)
    5. Select Export entry button and binary format file certificate for download. Press download.
    6.     Save certificate file in local PC folder
    In next step need export certificate file to SAP system. Sequence of step:
    1.       Run STRUSTSS02 transaction .
    2.       Chose certificate ->import.
    3.       Select downloaded certificate file
    4.       Select Add to certificate list button and Add to ACL button
    5.       Inter System ID and Client(000)
    6.       In next I download iview sap business objects template into sap portal: System administration->transport->Import. And select and download sap business Objects iview template in .epa format into sap portal.
    7.       Result – downloaded iview.
    8.       In next step I create system from template. System administration->system landscape.
    9. In next step I input parameters for my system in Connector category, Sap business objects and user management categories: See screen _2
    10.   When I created the system and test the connection error occurred: See screen_3
    This issue is important enough. I would be grateful for opinions and ideas. Thanks in advance.

    Did you find a solution?

  • Integration of OrgPublisher with SAP Portal

    Hi,
    I have an issue of integrating an organizational chart published by OrgPublisher in html-format into the SAP Portal using SAP HR Interface for Organizational Charting (HR-OCI) 6.0 (SAP ERP2005 and EP 7.0).
    I start with configuration of URL iviews for several organizational charts displaying different organizational levels. Charts are published by OrgPublisher in html-format.
    Then I would like to use HR-OCI with its Organizational Chart Launcher to launch the relevant URL iView with a relevant organizational chart depending on selected organizational unit (context-sensitive display). I tried this with SAP-provided Organizational Chart Tester iView and it works fine.
    According to the SAP HR-OCI configuration guide the Organizational Chart Launcher uses a set of URL parameters that are passed to the receiving application displaying the chart. 
    My issue is how I can pass those parameters to the relevant OrgPublisher organizational charts published as html-files in order to obtain context-sensitive chart selection.
    Best regards,
    Beata

    Hello Beata,
    We have  SAP ERP 6.0 . For some reason we don't see the new function module. Do you the reason . Pl help
    Thanks,
    Prasad

  • SAP Portal ESS SingleSignOn

    Hi!
    We are facing following Problem in our Sap Portal Environment.
    First of all SSO was working as intended. But after a Windows DC Migration with new computernames and new physical hosts we had to reconfigure SSO on our Portal-Servers. After the reconfiguration, SSO seemed to work again for everyone....but then some users started facing following problem (maybe 1 out of 100): That user cant login to SAP ESS via SSO. But when that person moves to another computer SSO is working there. So basically AD-Useraccount seems to be ok. So we thought "ok maybe a local computer problem". So a user with a working SSO tried to login on that "problem-computer" that had SSO problems. But SSO was working there suddenly with that user. So basically its not working only with that one useraccount on that specific computer. That user can login via SSO on every other computer and also other users can login via SSO on that "problem-computer".  We have several users right now that are facing that problem on their own computers.
    Our Windows group says that they cant see any problem in their Active Directory and point with their fingers on the SAP Portal as error source. So my Question: Is there any chance, that this problem really has his roots in the SAP Portal. i mean SSO is working for like 99% of the users. only for like 1% its not working only on their own specific computers. On other computers those 1% can also login via SSO.
    i would be really thankful for every idea!
    regards Alex

    Hi,
    for SSO, the browser has to get a HTTP 401 from the server. The browser should than get the token and send it to the server:
        Authorization: Negotiate YIIQCQYGKwYBBQUCoII long cryptic text P/TCCDBdxfqo=
    If the browser cannot resolve the SPN, or get it wrong, the browser will ignore the 401 or send a short Authorization answer back.
    What you can check besides the HTTP trace with the user::
    - Check if the computer of the user is in the domain and that the DNS is set correctly on that computer
    - Verify the logon process on the server with diagtool (complex but gives you every detail)
    - The users are using the same userID in the LDAP and UME?
    - All are using IE or some are using Firefox? In both the configuration for SSO has to be enables. IE: Windows integrated authentication + check the security zone. In FF: about:config and enter the correct domain.
    br,
    Tobias

Maybe you are looking for