Low_safety/com.sap.ip.bi.web.portal.integration/components/launcher

HI,
I have implemented Federated Portal on SP12
I have publish a Remote Role BI Intelligence once I click on BEx Web analyser from my Consummer I a mgetting the following error
low_safety/com.sap.ip.bi.web.portal.integration/components/launcher
Can anybody help what can be the issue...
Regards
Swapnil

Hi Swapnil
This could be permission issue. Check this link:
Re: BI 7.0 report displaying error
1.Give "Everyone" portal group read permission with end user checked for the "Portal Content" folder.
System Administration --> Permissions --> Right click on Portal Content Folder --> Open Permissions
2. Give "Everyone" portal group read permission with end user checked for the "low safety" folder.
System Administration --> Permissions --> com.sap.portal >low_safety> right click --> Open Permissions
Regards
Prabhakar

Similar Messages

  • BSP Exception: Access to URL /irj/servlet/prt/portal/prtroot/com.sap.ip.bi.web.portal.integration.launcher;jsessionid= not allowed

    Dear all,
    I've created out BI system in our new Portal installation and tested the connection. Everything works fine. I added the certificate of the portal to STRUSTSSO2 in BI ABAP and assigned SAP_ALL and SAP_NEW to my Account.in BI. If I open the iView from the portal I get a BSP Exception with the message:
    The used connection by the iView is to the ABAP-Stack of the BI-system not to the JAVA-Stack. Is that correct?
    BSP Exception: Der Zugriff auf die URL /irj/servlet/prt/portal/prtroot/com.sap.ip.bi.web.portal.integration.launcher;jsessionid=IDBYatWIpt_pX4uc52ChoZqMWkm1RAFW2qsA_SAP ist untersagt.
    What can be the problem/reason?
    Thanks!

    Hi Gerrit
    In both places you have to provide a authorization access to the end users then only it will work. because your are already said that in SAP_All & SAP_New working fine
    Back end BI system access as per the word document as pasted the link
    https://www.google.com/url?sa=t&rct=j&q=&esrc=s&source=web&cd=7&cad=rja&uact=8&ved=0CFIQFjAG&url=http%3A%2F%2Fbasisdsp.f…
    For SAP portal you have to create iview's assign the same to end user
    Assigning an Authentication Scheme to an iView - User Authentication and Single Sign-On - SAP Library
    Portal Authentication Infrastructure - Configuring the Portal for Initial Use - SAP Library
    BR
    SS

  • Access denied:com.sap.ip.bi.web.portal.integration.launcher

    Hi Friends,
    I have installed a Standalone Portal ( EP, EP core, BI Java) , configured LDAP as data source and imported the Portal content from Source system . ( in Development, Quality, Production)
    I completed all configuration and testing completed.
    But the portal user created with customized  iviews roles are working fine in Development and Production.
    But ....Access denied:com.sap.ip.bi.web.portal.integration.launcher error is encountered in Quality system.
    In QAS system, while installation I have selected EP, EP core as Usage type.. and after Insatllation I have installed additional Usage tye BI JAVA using JSPM
    Whereas in DEV, PRD ( EP, EP core, BI Java) were taken as Usage types while installation only..
    Above reason may effect the Test user for access denied error.
    Please suggest.
    Thanks
    Venkat

    Ramana,
    It looks like a permissions issue, right click on the system created for BI under System Admin-System Configuration-System landscape and open the permissions and ensure you have the everyone group added there and enduser checked.
    Good Luck!
    Sandeep Tudumu

  • Com.sap.ip.bi.web.portal.integration.launcher slow in Portal

    Hi experts,
    com.sap.ip.bi.web.portal.integration.launcher is consistently showing as one of the slowest-running in our NW2004s SP16 Portal (non-Federated).  Even the report variable screen is slow to load especially on first-time access. E.g., 31.8 seconds first time, 5.9 seconds second access in same session.
    But what is curious is that it sometimes the variable screen load time goes as low as 350ms if you keep trying within the same session.
    We've done the obvious - patching the BI Web App components, tuning the portal & Java runtime, checking the JCOs, load-balancing, tweaked the BI backend... but without being able to impact the performance of this application substantially.
    So I would value any suggestions for improvement!  Any tables we can cache?  Any SAP Notes to shed some light on this area?  Any Portal settings to tweak?
    Thanks, Marc

    Hi Marc,
    Slow point are to com.sap.ip.bi.web.portal.integration.launcher and
    JCO connection. Would you please check CPIC_MAX_CONV in SAP Note 314530?
    -Regarding of BI java on Web performance, would you please check the
    SAP Note 1022930?
    SAP Note 1025307 is a summary notes for performance on Web.
    Do you use antivirus software with a javascript  scanner, but still would you please also check the SAP Note 983066 because sometime this also may responsible for slow performance.
    SAP Note 948158:  Performance problems/measuring BI Java Web runtime
    One more thing would like to highlight:
    In first acess it's slow because OLAP cache was not in use, but after the first execution it's loading the variable from the cache so it's comperatively fast then the previous acess.
    Let me know, incase any confusion..
    Thank you,
    Tilak

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

  • Webi Portal Integration

    Hi:
    Is it possible to "schedule" a webi report from the portal iview?
    In my case, I am able to create an iview and link the report ID with it. This lets me see the webi report. Upon clicking EDIT I can go to edit mode (as of now I am investigating the warning netscape.javascript.JSException, but still it works on saing OK) as well and even save it in the Infoview with a different name. Now I am interested in exploring if I can also schedule the webi to run a certain time of the day via Portal.
    Any technical help on this would be really appreciated.
    Thanks,
    Sudipt

    Hi,
    We will be publishing a Crystal Report, WebIntelligence report and one Xcelsius dashboard. The Crystal report we already have the mechanism for (as you know, since you wrote the book on it!). With the WebI and Xcelsius documents we would like to consider the following scenarios:
    1. Publish them as actual, visible reports in the portal. IViews?
    >>> The steps would be the same - it is just a different ID for a different object. Make sure you use the option BusinessObjects Enterprise from the iView template.
    2. Publish them as hyperlinks in a list of reports
    >> You would have to create your own little application offering that or you could use Dashboard Builder as well. Logon to InfoView, go to Dashboards > corporate dashboard > where you have the option of Navigation List and Viewer.
    3. Link the portal to InfoView and use it as the presentation medium for the reports and navigation between the reports.
    >> possible but you might want to open InfoView in a new window because InfoView is not "made" to run in a frame.
    >> Did you look at the KM Integration ? sounds like it would solve lots of items for you.
    Since these reports will be interactive and the possibility exists that the WebI report will have to "run on open", what SAP portal complications might that present?

  • COM.SAP.PORTAL.RESERVED.WD.PB.RESTART

    Hello everyone,
    I have publish a BI iView into my portal, when I preview this iView(BW Query) it executes fine. But when I add the iView to a Page, and try to preview the Page, I get the following error:
    Portal Runtime Error
    An exception occurred while processing a request for :
    iView : com.sap.ip.bi.web.portal.integration.launcher
    Component Name : com.sap.ip.bi.web.portal.integration.launcher
    The parameter name "COM.SAP.PORTAL.RESERVED.WD.PB.RESTART" contains the invalid character ".".
    Exception id: 09:02_25/10/06_0009_528583550
    See the details for the exception ID in the log file
    Any idea what it could be?
    Rgds
    Sirahuen

    Hi Jose,
    If the BW and EP are not compatible versions , you get this kind of error , where the conversion has some problems.
    We had the same issue and upgraded our patch levels and it worked fine.
    Cheers
    Raja Gopal Gangula

  • Anonymous com.sap.km.cm.xmlformpreview - urgent (goinglive)

    Hi gurus!
    We are to publish some news in our NW2004s Portal. News considered to be available for anonymous users. We use com.sap.km.cm.navigation based ivew in NewsExplorer fromat and anonymous authetification type. News details are shown with application com.sap.km.cm.xmlformpreview. Please advise me how to make this application runnable under anonymous user.
    Thanks.

    Hi Ivan,
    Maybe this helps you, I documented a few years ago when I had to create a EFP with KM news. It then implemented it on a NW2004...
    But after looking at it it could still do the trick, So its worth looking at it I guess...
    To allow full anonymous access to the KM News a custom setting needs to be made to this default SAP portal module. If this customized settings is not made the portal will give a logon screens for the KM News pop-ups that are located on every market overviewpage. We do this in 9 steps.
    Step 1: Login to the portal as an administrator. When logged in go to:
    System Administration>Support > Support Desk > Portal Runtime
    Go to: Browse deployment
    Step 2: Go to: root/web-inf/deployment/pcd and locate the file: com.sap.km.cm.par.bak
    Click: download to download the file to your local computer.
    Step 3: The file will not download with the .par.bak file-extension because the portal zips it first (so donu2019t wory on that). Accept the file download by pressing save. Select a location on you local computer where you want to put the file.
    Step 4: Unpack the file with your WinZIP compatible zip-extractor.
    Step 5: Start SAP NetWeaver Developer Studio (from now on short: NWDS) and import a file by: File > Import
    Select Import Source PAR file, and confirm with Next
    Browse for the file. Donu2019t forget to set the filter option to .par.bak. or you wonu2019t find the file.
    Select it and confirm.
    Copy the first part of the file name from u201Ccom.u201D Till u201C.par.baku201D and Paste it as the
    Project Name. Select a folder where to create the project. Confirm by pressing Finish.
    The .par.bak file is imported in to a newly made NWDS Project.
    By default none of the libraries are imported into the NWDS Project so we have to copy them manually into the proper folder.
    For that we need to open the Windows File Exploreru2026
    Step 6: Browse to the folder that contains the .par.bak file that you unpacked under step 4.
    Select the .par.bak file > RightClick > Open with > Choose Programu2026
    Choose your WinZIP compatible extracter as the executable to open this file. In addition you can check the ckeckbox: u201CAlways use the selected program to open this kind of fileu201D. Confirm
    After you confirmed a WinZIP window will pop-up. It shows the content of the .par.bak file.
    Cascade the NWDS behind the WinZIP pop-up and start a Drag & Drop action on the *.jar file(s). Drag it to the /dist/PORTAL-INF/private/lib folder and Drop it
    The Project is made and all files are imported. We can continue to the next step and Edit the moduleu2026
    Step 7: Within NWDS browse to: com.sap.km.cm/dist/PORTAL-INF
    Look for the file: portalapp.xml
    DoubleClick it and open the tab u201CSourceu201D.
    For the componentu2026
    <component name="xmlformpreview">
    We have to add the following tag inside the <component-profile> tag:
    <property name="AuthScheme" value="anonymous"/>
    Save the file.
    Step 8: Within NWDS RightClick on: the project and Select: Export
    This will initiate the Export Wizard. Go trough this steps:
    u2022     Select Par File (selected by default) > Confirm with Next.
    u2022     Select the project  (selected by default) > Confirm with Next.
    u2022     Export location will be the Module folder by default (leave it like it is) > Confirm with Finish
    The module is exported as .par file and ready for re-deploymentu2026
    Step 9: Again login to the portal as an administrator. When logged in go to:
    System Administration>Support > Support Desk > Portal Runtime
    Go to: Administration Console
    Browse tot the NWDS Project directory and select the current Project folder.
    Select the .par file and confirm this action.
    Last but not least confirm the re-deployment by clicking Upload
    The customized module is now re-deployed on the portal.
    Good Luck!
    Benjamin Houttuin

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

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

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

  • How to work web portal with sap rfc

    Hi,
    This is prasad my question is
    my project architecure includes:
    BEA web portal platform as frontend
    web methods as the middle ware
    and SAP CCS
    the data handling will be done using SAP RFC
    how to handle the validation of fields in the web portal using sap?
    Thaks in advance!

    Sandip,
    The forum that you have posted your question in is for questions related to the SAP Business One Integration for SAP NetWeaver.  Your question is SDK related and should be posted in the SAP Business One SDK Discussion forum.
    That being said ... here are the answers to your questions ...
    1. As far as the SDK goes, it does not provide an IDE.  Since the API's are COM, then you can use any IDE that can communicate with COM objects such as VB6, VB.Net, C#, C++, etc.
    2. As stated above, the SDK does not provide an IDE.  You would need to purchase one or you can get a free one from Microsoft on there website such as Visual Basic 2005 Express Edition.
    3. The Screen Painter is an SAP tool (independant of any IDE) that allows you to graphically create new SAP Business One looking forms and then save them to an XML format.  You would then in your code use the LoadBatchActions method to load your XML form.  Documentation on the Screen Painter and the LoadBatchActions method is in the SAP Business One SDK Help Center Documentation that comes with the SDK as well as there is eLearning available for the SDK on this portal as well as the SAP PartnerEdge Portal if you are an SAP Business One partner.
    4. If you are an SAP Business One partner and have an "S" number, you can log into the SAP PartnerEdge Portal and then under SAP Business One and "Installations & Updates" you can download the SAP Business One product as the SDK installation is part of the overall installation package.  If you are not a partner you would need to contact your local SAP Business One sales representative.
    Other tools available that work with the SAP Business One SDK are located on the SDN Portal under this link ...
    SAP Business One Tools [original link is broken]
    HTH,
    Eddy
    P.S. please give points for helpful answers!

  • Outlook Web Access - Integration into portal

    Hello All,
    Could you please let me know if there is any specific iview to integrate OWA (Microsoft Outlook Web Access) into portal.
    I did go thru the docs on configuring OWA into Portal -which specifies to use App Integrator iview and http system (with user mapping), but the result is i am redirected back to the logon page only.
    Kindly help.
    Regards,
    venkat.

    Hi Venkat,
    Please go through the following PDF document..
    http://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/ep/_g-i/integration%20of%20outlook%20web%20access%20into%20sap%20enterprise%20portal.pdf
    Hope this will help you.
    Regards
    Kris

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

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

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

  • Web Dynpro ABAP Stylesheet - Portal Integration

    We have a Web Dynpro ABAP being displayed through a Portal iView.  The Portal server and the Web Dynpro ABAP server are separate.  Our problem is in getting the Web Dynpro ABAP to use the stylesheet of the Portal.
    We can make this work by forcing an external stylesheet (via application parameters, global Dynpro settings, or passed on the end of the URL), but we have to hard-code the full URI of the Portal stylesheet.  This would be very hard to manage if we hard-code every iView's CSS location (or set every individual Web Dynpro's application parameters), and we want instead for the Portal to supply whatever the user's stylesheet is dynamically. 
    So what we want is: if we change the Portal stylesheet, the Portal would just pass the new stylesheet URI to our ABAP Web Dynpro iViews without manual modification of the iViews.
    Here is an example of what works:
    http://our-abap-server.com/sap/bc/webdynpro/sap/cprojects?sap-ep-themeroot=https://our-portal-server.com/irj/portalapps/com.sap.portal.design.portaldesigndata/themes/portal/ourportalstylesheetname
    Shouldn't the Portal iView automatically pass sap-cssurl or sap-ep-themeroot to Web Dynpro ABAP?  We have "Supply Portal Stylesheet" checked on the iView… it just doesn't pass anything to the Web Dynpro ABAP.  Why wouldn't SAP pass this parameter dynamically to the Web Dynpro ABAPs?  Is this a product error? 
    There seems to be a great deal of confusion about this on the SDN message forums... I think this may be the core issue.
    We are using a 7.0 SP13 Portal with an ECC 6.0 SP12 backend.

    Now that you mention it, I ran into that exact same issue  -- the application parameters didn't work for hard-coding the theme.  The fix ended up being the web server semicolon thing I mentioned earlier (that was why the parameter didn't make it to the backend). 
    The themeroot is automatically sent to the backend from the portal, so you shouldn't really have to manually send it as a parameter anyways.
    I'd suggest talking to your network guys.  Also this could be the result of the SP you are on (we're on 13 for the portal and the backend system -- maybe this feature doesn't work in some earlier SP's?).  There are also some options to force the theme as a WD application parameter on the backend side, which you could check into.  Details on those are here:
    [http://help.sap.com/saphelp_nw2004s/helpdata/en/7b/fb57412df8091de10000000a155106/frameset.htm]
    Also you could look at the requests being made by installing HttpAnalyzer in your browser.  You can inspect "post" parameters going from the portal to the backend system.  One of those posts (the first one to the backend system) should contain the parameter sap-cssurl (same kind of thing as sp-ep-themeroot).  This is where our problem turned up as this parameter was not being posted.
    Lastly, make sure that your frontend portal and backend portal are in the same domain.  For instance:
    frontend.domain.com
    backend.domain.com
    If your backend and frontend are in different domains it messes all kinds of things up, including stylesheets I think.  If you can't get around this, then read about domain relaxing (but I highly recommend getting the domains the same).
    When we started, ours were:
    portal.dx.company.com
    sap.company.com
    This created all kinds of problems.  Putting our systems in the same domain with the same protocol and fixing our little semicolon web server problem fixed basically all of our portal complaints.  Up until that time, we had also had many problems with session management (backend sessions were getting stuck until the HTTP timeout).
    That's all I know.   Good luck.

  • Problem integrating BI analysis in web portal using HtmlViewServiceSoap

    GOAL:
    We have a web portal that is built using JSF and RichFaces and we want to integrate BI analysis using Oracle BI EE web services.
    We use Oracle BI EE 11g and tested with both 11.1.1.5 and 11.1.1.6).
    SOLUTION:
    Because Oracle BI server will not be accessible outside for the end web user we need to implement a proxy servlet acting as a bridge.
    Oracle BI web services provides a nice way of doing this: setBridge method in HtmlViewServiceSoap interface.
    In order to achieve our goal we use the HTML produced from oracle BI web service directly into a new created jsp page.
    This whole jsp page content is:
    <%
    String biReport = (String)request.getAttribute("biReport");
    MyServiceUtils.writeBiContent(request, out, biReport);
    %>
    writeBIContent method is listed here: http://pastebin.com/ndVt3HBu
    Our proxy/bridge servlet code is listed here: http://pastebin.com/NibVnBLb
    THE FIRST PART WORKS:
    The first HTML content retrieved from web service looks OK: all js and css files are prefixed with our bridge url.
    Example:
    <script type="text/javascript" src="/AbsWeb/bridgeservlet?RedirectURL=http%3a%2f%2f127.0.0.1%3a9704%2fanalytics%2fres%2fb_mozilla%2fcommon%2fobips.JavaScriptExtensions.js"></script>
    Complete html code generated can be viewed at: http://pastebin.com/DGRwTjaz
    Therefore our bridge servlet is used to retrieve resources like:
    http://localhost:8282/AbsWeb/bridgeservlet?RedirectURL=http%3a%2f%2f127.0.0.1%3a9704%2fanalytics%2fsaw.dll%3fajaxGo
    http://localhost:8282/AbsWeb/bridgeservlet?RedirectURL=http%3a%2f%2f127.0.0.1%3a9704%2fanalytics%2fsaw.dll%2fpages/common/ajaxloggedin.html
    These are translated by our servlet into:
    http://127.0.0.1:9704/analytics/saw.dll?ajaxGo&NoCookie=1&SearchID=jloq2nea8i290a6c9knifttj86&urlGenerator=qualified&_scid=XjlySz0yuAMz1rjOZZ4Y&ContainerId=m%3Aportlet%7Er%3ATestrevenuebydistrict&NQID=s0vbq5q6u2ijee3s9arnmmbsgtldhghfdlq6lc2&icharset=utf-8
    http://127.0.0.1:9704/analytics/saw.dll/pages/common/ajaxloggedin.html
    FINALLY OUR PROBLEM:
    The html code retrieved with ajaxloggedin.html does not use our bridge servlet for all js and css files...
    we expect this:
    example: <link rel="Stylesheet" href="/AbsWeb/bridgeservlet?RedirectURL=http%3a%2f%2f127.0.0.1%3a9704%2f/analytics/res/s_blafp/uicomponents/blafplus.css" type="text/css">
    but we get this:
    example: <link rel="Stylesheet" href="/analytics/res/s_blafp/uicomponents/blafplus.css" type="text/css">
    The first part is missing.
    Complete html code of ajaxloggedin.html can be viewed at: http://pastebin.com/gKTMfPSR
    We end up with a rotating clock displaying in our web page...
    Does anybody see what we are doing wrong, or has anybody had the same problem and a solution or work around?
    Thanks,
    Hans

    Hi,
    Can you go to RSA1 and check in BI Content - Bex Web Template - Select Objects and Transfer Selection - and see if the 0Analysis_Pattern is active or not and is transported to QA.
    And the second thing is to check the SPRO Config for the Template which is maintained:
    To Do this navigate in BW System:
    SPRO -  SAP NetWeaver - Business Intelligence - Settings for Reporting and Analysis - BEx Web - Set Standard Web Template - and see if Web Template is maintained as it is in Dev.....
    Since when you run the Query from Query Designer it will check in SPRO for this setting and show the report with that template.
    Hope this helps.
    Cheers-
    Pramod

  • File does not Upload !   Error in the listener class com.sap.ip.portal...

    Hello.
    Recently, I Add a New Server Node on Java Central Instance.
    And Java Program Upload on Portal, then following error occured.
    Error in the listener class com.sap.ip.portal.admin.portalanywhere.QueryHandler during the process of
    handleTopic
    Original server node can upload successfully.
    But, An error happens in New Additional node.
    Please tell me way to resolve the error.
    Regards.
    Edited by: Masashi Fujita on Dec 24, 2008 5:29 AM
    Edited by: Masashi Fujita on Dec 25, 2008 7:20 AM

    Hi Masashi Fujita,
    Check this Link for Uploading and Downloading files using Web Dynpro Java.
    [Uploading and Downloading Files in Web Dynpro Java|https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/00062266-3aa9-2910-d485-f1088c3a4d71]
    [Upload Files Using Web Service in Web Dynpro Java Application|https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/c0d9336b-b4cf-2910-bdbf-b00d89bd2929]
    [Uploading and Downloading Files in Web Dynpro Tables|https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/b0e10426-77ca-2910-7eb5-d7d8982cb83f]
    Thanks & Regards,
    Sharma Kvbk.

Maybe you are looking for