Cognos Analytics

 View Only

  • 1.  iFrames execution time

    Posted Mon June 28, 2021 11:05 AM

    Hi,

     We are replacing our legacy portal pages by a normal Cognos Report.  To do so, we replace:

    ·         The Navigator Portlet with a table, containing hyperlinks

    ·         The IBM Cognos Viewer Portlet with a hyperlink in an iFrame.

    The first part works great, but we are experiencing problems with reports that are executed in an iFrame.  It takes a long time before they are displayed, especially when we compare it to the time in which the viewer portlet in the legacy portals displayed a report.

    We also tried to change the link in the iFrame to an executed version of the report.  This speeds up the process, but it is still very slow.

    Does anyone have experience with iFrames?  Any suggestions?

     

    Thank you for your answer,

    Stephan


    #CognosAnalyticswithWatson


  • 2.  RE: iFrames execution time

    Posted Tue July 06, 2021 02:25 PM

    Hi Stephan,
    We dealt with similar issues in our environment. Storing charts within iFrames certainly improved overall latency of our reports (as opposed to simply running reports/charts normally) however it took longer for iFrames to "kick-off" than we would like. After investigating with our representatives and IBM support team, we found it to be an issue with the way Cognos handles its "GLASS" codes, which cannot run in parallel. So the more charts/iFrames on a page, the more distinct GLASS codes are needed to run, and this exponentially increases report runtime. Steps were taken to "remove" GLASS codes and bypass these loads, but they were still triggered, as our single-sign-on environment required re-authentication and re-running of the GLASS codes in each iFrame window.
    We found that the solution was iFraming the Cognos charts in a non-Cognos reporting site. Our company has a HTML web "portal" page, which we use to input parameters and store iFramed Cognos charts, which works quite well and bypasses the GLASS code and Cognos-driven latency issues. Reports now take < 5 seconds to run fully, and are able to run successfully in parallel.
    Hope this helps!



    ------------------------------
    Cole Brandt
    ------------------------------

    Original Message


  • 3.  RE: iFrames execution time

    Posted Tue July 06, 2021 02:26 PM
    Hi Stephan,
    We dealt with similar issues in our environment. Storing charts within iFrames certainly improved overall latency of our reports (as opposed to simply running reports/charts normally) however it took longer for iFrames to "kick-off" than we would like. After investigating with our representatives and IBM support team, we found it to be an issue with the way Cognos handles its "GLASS" codes, which cannot run in parallel. So the more charts/iFrames on a page, the more distinct GLASS codes are needed to run, and this exponentially increases report runtime. Steps were taken to "remove" GLASS codes and bypass these loads, but they were still triggered, as our single-sign-on environment required re-authentication and re-running of the GLASS codes in each iFrame window.
    We found that the solution was iFraming the Cognos charts in a non-Cognos reporting site. Our company has a HTML web "portal" page, which we use to input parameters and store iFramed Cognos charts, which works quite well and bypasses the GLASS code and Cognos-driven latency issues. Reports now take < 5 seconds to run fully, and are able to run successfully in parallel.
    Hope this helps!

    ------------------------------
    Cole Brandt
    ------------------------------

    Original Message


  • 4.  RE: iFrames execution time

    Posted Wed July 07, 2021 03:32 PM
    Hi Cole,

    Can you please explain on how you were able to bypass GLASS code and retrieve Cognos charts?

    Thanks!

    ------------------------------
    Dhanush
    ------------------------------

    Original Message