Documentation missing about iView properties of com.sap.portal.masthead

Hi,
I configure the available links in the portal masthead. When switching "Show Link in Masthead: Help Center" (property ID: ShowHelpCenterLink) from "No" to "Yes" I get the link "Help Center" in the portal header, but when clicking the link nothing happens.
Is there any documentation how to use/implement this feature?
Best regards,
Johannes

Hi Keshari
I already provided a valid URL but this URL is only being launched when I  choose the property "Show Link in Masthead: Help" (ID: ShowHelpLink).
What I noticed is that when I click on the "Help Center" link in the header, the currently displayed page gets compressed creating about 1/3rd empty space on the page on the right hand side.
How can I configure that help gets displayed in this area?
For "help center" I only found some ABAP-related documentation (http://help.sap.com/saphelp_nw70ehp1/helpdata/en/c2/00976e34ef4397b082acb7d934d373/frameset.htm) which does not contain any Portal related configuration.
Regards, Johannes

Similar Messages

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

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

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

  • Com.sap.portal.htmlb in SSL

    Hello,
    We have implemented SSL on the portal platform (on the J2EE) and it seems to be working for the most part.  We are using it with Kerberos authentication.  We have noted that there are some issues and they mostly revolve around the com.sap.portal.htmlb "portalapp".  Firstly, when using SSL on port 50001, items in the HTMLB component are being called without SSL VIA port 50000.
    Also, we noted that there are a few files physically missing from the ../com.sap.portal.htmlb/jslib directory (for example: refresh.gif and pagerror.gif).  When we manually created them, those particular errors have disappeared but we also see the:
    "http://bnpdsapepc1d.corp.brucepower.com:50000/irj/portalapps/com.sap.portal.htmlb/jslib/emptyhover.html"
    and
    "http://bnpdsapepc1d.corp.brucepower.com:50000/irj/portalapps/com.sap.portal.pagebuilder/html/emptydocument.html"
    In the trace - but we are using HTTPS for everything else...?
    Is there something that points the HTMLB component to a static URL or to pick up the http with 50000?  We have not made any custom changes here.
    Any help would be humbly appreciated,
    Judson

    We seem to have figured it out.  It turns out that the registration of the ktpass is very case sensative.  We registered the FQDN of the host with the hostname part in UPPERCASE.  Now the portal - Kerberos with SSL works fine when using the https://HOSTNAME.company.com:50001/irj.  Otherwise, we receive "Action Cancelled" from the TLN and down.  We checked the SSL cert and it looked lowercase so we checked the keytab and found the HTTP/[email protected] - we will try to resolve the UPPERCASE by re-running that part of the process.
    Thanks,
    Judson

  • 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

  • IView not found: com.sap.ip.bi.web.portal.integration.launcher

    Hi!
    I am about to integrate SAP BI into SAP EP 7.0.
    All the necessary steps with the program "RSPOR_SETUP" I already executed.
    Unfortunately when I try to execute a Query on Portal I get the following error:
    iView not found: com.sap.ip.bi.web.portal.integration.launcher
    Can some one help me to solve this error?
    Thank you very much!
    regards
    Holger Thomasson

    hi Thom,
      Make sure that you have already installed the BI 7.0 web templates as per the oss note 990321.
      If not, install the BI 7.0 web templates according the note. BI 7.0 templates are :
    0ANALYSIS_PATTERN
    0ANALYSIS_PATTERN_EXPORT
    0INFO_CONSUMER_PATTERN
    0ANALYSIS_PATTERN_ICP
    0ANALYSIS_PATTERN_INFO
    0QUERY_TEMPLATE_BROADCAST_PDF
    0ANALYSIS_PATTERN_HEADER
    0ANALYSIS_PATTERN_FOOTER
    0ANALYSIS_PATTERN_FILTER
    Web Item
    0PATTERN_BARCHART_STANDARD
    Thanks.

  • IView not found: com.sap.pct.mdm.tech.systems.MDMSystemWizard

    Hello Experts!
    I've installed MDM 5.5 SP6 along with the portal content that came from the same download. The portal content files I installed are listed below.
    BPMDMAPPLI06_0.sca
    BPMDMTECHN06_0.sca
    MDM_WEB_UI550.sca
    MDMJAVAAPI06_0.sca
    When I try to get a new MDM system I get the exception below. I've looked and searched the portal content and this iView (com.sap.pct.mdm.tech.systems.MDMSystemWizard) does indeed appear to be missing. Is there something else I need to install? The SCA files all deployed without errors.
    Steps to recreate this error:
    System Administration => System Configuration => Portal Content => (landscape directory)
      => Right-Click => New System (from template) => choose MDM System template => Next
    Thanks,
    John
    [EXCEPTION]
    #1#com.sapportals.portal.prt.runtime.PortalRuntimeException: iView not found: com.sap.pct.mdm.tech.systems.MDMSystemWizard
            at com.sapportals.portal.prt.deployment.DeploymentManager.getPropertyContentProvider(DeploymentManager.java:1937)
            at com.sapportals.portal.prt.core.broker.PortalComponentContextItem.refresh(PortalComponentContextItem.java:222)
            at com.sapportals.portal.prt.core.broker.PortalComponentContextItem.getContext(PortalComponentContextItem.java:316)
            at com.sapportals.portal.prt.component.PortalComponentRequest.getComponentContext(PortalComponentRequest.java:387)
            at com.sapportals.portal.prt.connection.PortalRequest.getRootContext(PortalRequest.java:488)

    Restarting the J2EE engine resolved this problem.

  • Old iView of EP 6 (com.sap.portal.persoUserPassword) not accessible in EP 7

    Hi Experts,
    I am using EP 7. My requirement is to create change password screen for EP 7 users. This can be done using the iView of EP 6.  I am trying to access old iView of EP 6 (com.sap.portal.persoUserPassword) from EP 7. For this I have made following changes:
    set ume.admin.wdactive=false in the ume properties using the configtool
    restart j2ee server
    After doing this I am trying to access the iView. However I am  getting message that see SAP note 869852 etc. Could you pls let us know what is going wrong with us.
    Regards,
    RK

    Problem sorted out.

  • 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

  • Com.sap.portal.runtime.logon_api.jar and umelogonbase.jar missing

    Hi All,
    I am trying to customize the portal login page . and i got the steps how to do it. But when i import the par file com.sap.portal.runtime.logon.par into NWDS , i could not find com.sap.portal.runtime.logon_api.jar and umelogonbase.jar jar files under dist\PORTAL-INF\lib . These files are missing.
    Where could i retreive these files . I checked all the other subfolders i am unable to find these files.
    Can anyone please guide me
    That would be great.
    Thanks
    Sowmya

    Hello,
    Can u tell me how to import that .par file in nwds ,
    mean i want to know the procedure
    1)which project is to pe created in Nwds
    2)how and wher to import that .jar file
    3) in some sap blocks i read that convert that .par file to zip n then extract it  is this really to be done
    Would really appreciate your reply!!
    Thanks In advance!

  • 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

  • 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

  • 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 we’ve 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!

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

Maybe you are looking for

  • 17" and 15" MBpro Keyboards Interchangeable?

    Are the two keyboards interchangeable because I plan on buying a used keyboard from a 17" MBpro and wanted to make sure it will be a direct fit? TIA

  • "[Microsoft][ODBC Microsoft Access Driver] Syntax error in field definition

    I am creating a program in Java which has a Database reference application.The Database I am using is MS Access.But whenever I am trying to run the program from DOS Prompt(ie executing the program:java <program name>) I am unable to connenct to the d

  • Change the WebApp menu language to English

    Hi,<o:p></o:p> From some reason all of the menu language (when preview a document for example and click the bottom menu) shows in French. how can i change it to English?<o:p></o:p> Thanks a lot in advance<o:p></o:p>

  • Tutor Wanted

    I am looking for a tutor to help me using the Oracle Developer to build web applications. I have some knowledge of Forms and Reports with client/server environment. I want to learn more about web project. The location is in New York City. If you have

  • MVC Application

    Hi All, Iam ramkumar,iam new to BSP technology. I create two views 1.main1.htm and another 2.page.htm i put a button in main1.htm, and another button in page.htm. and also i created a controller.my task is if i press the button in main1.htm that will