Cognos Analytics

 View Only
Expand all | Collapse all

[QUERYSTUDIO] Cognos Portal prevents starting QS with Microsoft Edge Chromium v88 & Chrome v88

  • 1.  [QUERYSTUDIO] Cognos Portal prevents starting QS with Microsoft Edge Chromium v88 & Chrome v88

    IBM Champion
    Posted Tue February 23, 2021 10:19 AM
    Dear Cognosgurus,

    we still have some 1.500 QS Users on one of our installation. The cognos portal prevents using QS when browsing with Chrome v88.
    It opens the viewer instead of QS and converts reports to Reportstudio reports.

    Is there a way to force the Cognos Portal to open QS instead of viewer and converting?

    Any hint is appreciated. 


    ------------------------------
    Ralf Roeber
    https://linkedin.com/in/ralf-roeber-470425a/
    ------------------------------

    #CognosAnalyticswithWatson


  • 2.  RE: [QUERYSTUDIO] Cognos Portal prevents starting QS with Microsoft Edge Chromium v88 & Chrome v88

    Posted Tue February 23, 2021 10:46 AM
    Edited by System Fri January 20, 2023 04:37 PM
    @Ralf Roeber - Query Studio is now one of IBM's "legacy" studios and, I believe, these can only be opened with Internet Explorer.
    I know Chrome doesn't work, but I am not sure about Edge.

    Hope this helps.

    ------------------------------
    Adam McIlravey
    ------------------------------



  • 3.  RE: [QUERYSTUDIO] Cognos Portal prevents starting QS with Microsoft Edge Chromium v88 & Chrome v88

    Posted Wed February 24, 2021 07:02 AM

    Adam McIlravey – I agree with Ralf Roeber, Chrome doesn't support QS/AS.  I also tested Edge this morning and it also doesn't support QS/AS.  You option for now is to use IE to make any QS report edits or us the other browsers to convert the QS report to Report.

     

     

     

     

     

     

     

     

     

     

     

     

     

     

     

     

     

     

     

    Peter Chan

    613-295--0428

     






  • 4.  RE: [QUERYSTUDIO] Cognos Portal prevents starting QS with Microsoft Edge Chromium v88 & Chrome v88

    IBM Champion
    Posted Wed February 24, 2021 02:39 AM
    Hi Ralf,

    you can force the client to use Internet Explorer even if chrome is the default browser.
    Then Cognos Connection opens in IE.

    One of many samples:
    windows - Open Internet Explorer from Chrome using a protocol handler (ie:url) - Stack Overflow

    As I remember, there is a tool by google to redirect certain urls to IE...
    LBS: https://support.google.com/chrome/a/answer/3062039?hl=en

    cheers
    Martin





    ------------------------------
    Martin Otto
    senior solution expert
    avantum consult AG
    Konstanz area
    ------------------------------



  • 5.  RE: [QUERYSTUDIO] Cognos Portal prevents starting QS with Microsoft Edge Chromium v88 & Chrome v88

    Posted Wed February 24, 2021 07:38 AM
    Hi Ralf,

    Query Studio and Analysis Studio have always been available for FireFox and IE only. 

    Thanks
    Greg

    ------------------------------
    Greg McDonald
    Offering Manager - Cognos Analytics
    IBM
    greg.mcdonald@ca.ibm.com
    ------------------------------



  • 6.  RE: [QUERYSTUDIO] Cognos Portal prevents starting QS with Microsoft Edge Chromium v88 & Chrome v88

    Posted Wed February 24, 2021 08:28 AM
    You can force Query Studio to open in any browser. just create a link. We created a folder called Query Studio and placed a URL link inside. The link forces QS to open in a new window, regardless of which browser.

    http : install_location/Analytics/bi/v1/disp?b_action=xts.run&m=portal%2Flaunch.xts&ui.gateway=%2Analytics%2Fbi%2Fv1%2Fdisp&ui.tool=QueryStudio&ui.object=&ui.action=new&launchinWindow=true&backURL=disp%3Fb_action%3Dxts.run%26m%3Dportal%2Fclose.xts

    ------------------------------
    Will Phillips
    ------------------------------



  • 7.  RE: [QUERYSTUDIO] Cognos Portal prevents starting QS with Microsoft Edge Chromium v88 & Chrome v88

    Posted Wed February 24, 2021 08:32 AM
    Query Studio will only open in IE11 and Firefox.  It is not supported in Chrome or Edge.  It is my understanding from conversations with IBMers that this is not expected to change, as QS is a legacy tool.

    AS and Event Studio have the same browser limitations.

    Rich

    ------------------------------
    Richard Chester
    Director of Business Intelligence
    LPA Software Solutions
    ------------------------------



  • 8.  RE: [QUERYSTUDIO] Cognos Portal prevents starting QS with Microsoft Edge Chromium v88 & Chrome v88

    Posted Thu February 25, 2021 10:58 AM
    Edited by System Fri January 20, 2023 04:34 PM
    Hello Ralf,

    Have you tried this type of url yet?

    In my environment it works, both in Chrome and Edge.

    https://yourserver/yourcognos11/bi/v1/disp?b_action=xts.run&m=portal%2Flaunch.xts&ui.gateway=%2Fcognos11%2Fbi%2Fv1%2Fdisp&ui.tool=QueryStudio&ui.object=&ui.action=new&launch.launchinWindow=true&backURL=disp%3Fb_action%3Dxts.run%26m%3Dportal%2Fclose.xts



    PS for Analysis Studio, this url works: https://yourserver/yourcognos11/explore/explore.htm


    ------------------------------
    Marc van Waardenburg



  • 9.  RE: [QUERYSTUDIO] Cognos Portal prevents starting QS with Microsoft Edge Chromium v88 & Chrome v88

    IBM Champion
    Posted Tue July 27, 2021 08:16 AM
    Hello Cognos Lovers,

    thank you for so many replies to my small question

    Just wanted to share our solutions around QS usage / problems.

    Using actual Chrome/Firefox/Edge version works well for us with CA11.1.5+7+11.2 so far. Being supported or not.

    These are the problems and solutions we found to our issues:

    Problem 1: Opening QS in new Portal
    Solution 1: via Link as stated in this discussion works. We have been using this since 2004 :-) works like a charme.
    Solution 2: Force the Opening of IE in a compatible mode via http headers ... did so for the last 4 month. Last week this stopped working as MFA-authentication page opens in Edge and the OIDC callback Url is opened in Edge, but then directing to Cognos IE opens, which is forced and we receive session mismatch between Edge + IE. Ugly. So removed this from the setup. 

    Problem 2: Clicking on a QueryStudio report in Public Folder opens ClassicViewer which does not permit editing of filters
    Solution 1: Extension of "..." menu add "Run with QueryStudio" as button and hitting that button call the before mentioned URL. Not nice because default action, when clicking on a Querystudio Report still opens the ClassicViewer
    Solution 2: Rewrite rule to force opening in QueryStudio instead of ClassicViewer 

    Here is the RewriteRule for Apache/IHS:
    RewriteCond %{HTTP_REFERER} (crn[^\/]).+classicviewer.+id=(?:XSSSTART)?(.[^&]+)(?=XSSEND) [NC]
    RewriteRule ^/(crn[^\/]+)/bi/v1/disp$ https://%{HTTP_HOST}/$1/cgi-bin/cognos.cgi/bi/v1/disp?b_action=xts.run&backURL=disp\%3Fb_action\%3Dxts.run\%26m\%3Dportal\%2Fclose.xts\%26ui.compid\%3Dps&m=portal/launch.xts&ui.tool=QueryStudio&ui.object=storeID(\%22%2\%22)&ui.action=edit&ui.gateway=/$1/bi/v1/disp&launch.launchinWindow=true [NE,R=301,L]
    ​

     
    Problem 3: QS iFrame height is not properly scaled in chrome/edge. This is a confirmed problem in chrome.
    Solution: insert some javascript into layout.js file to execute, when ever the iFrame needs resizing.

    /** -------------------------------------------------------------- AMVARA ADD ON --------------------------- **/
    /** -------------------------------------------------------------- AMVARA ADD ON --------------------------- **/
    /** -------------------------------------------------------------- AMVARA ADD ON --------------------------- **/
    
    
    /**
    * AMVARA resizeFrame function to set the correct size in iFrame for QS usage
    * Changelog:
    * 2021-03-01 RRO created
    */
    function resizeFrame(timeoutVal=500) {
    
    
        console.log("AMVARA trying to set new height")
    
        // Try getting the iFrame height ... this is just for information.
        var elm_targetIFrame = null
        try {
            elm_targetIFrame = window.parent.document.getElementById("reportIFrame").style.height
        } catch {
            console.log("AMVARA: we could catch this error ... will do so later")
        }
        // Now we check if height can be set
        if (typeof(elm_targetIFrame) != 'undefined' && elm_targetIFrame != null)
        {
            // See if there is a reportFrame ... it's height defines the iFrame height to be set
            var AMVARA_height=window.parent.document.getElementById("reportFrame").scrollHeight-50
            console.log("AMVARA iFrameHeight:", AMVARA_height)
            // Exists.
            console.log("AMVARA windowElement with iFrame exists")
            window.parent.document.getElementById("reportIFrame").style.height=AMVARA_height+"px"
            console.log("AMVARA windowElement set height to ", AMVARA_height)
        } else if ( AMVARA_globaleResizeCounter<AMVARA_ResizeThresholdCounter) {
    
            // iFrame is not there yet ... we should wait a little if retry counter has not been reached
    
            // Add +1 to counter
            AMVARA_globaleResizeCounter++;
            console.log("AMVARA globalCounter: ", AMVARA_globaleResizeCounter)
            // set a timeout and max retries
            AMVARA_resizeTimeout = setTimeout(function() {
                    console.log("AMVARA timeoutResize: ", timeoutVal)
                    resizeFrame(timeoutVal+timeoutVal);
                }, timeoutVal )
        }
    
        // Just for information
        console.log("<====")
        return
    }
    
    /** AMVARA_resizeTimeout is the window.setTimeout result */
    var AMVARA_resizeTimeout = null
    
    /** AMVARA_globaleResizeCounter is a counter to understand howmany times we have looked for the iFrame */
    var AMVARA_globaleResizeCounter=1
    
    /** AMVARA_ResizeThresholdCounter is the threshold where we would like to stop looking for iFrame */
    var AMVARA_ResizeThresholdCounter=10
    
    /** resize the iFrame */
    resizeFrame(500)
    
    /** when window is resized, we would probably also resize the iFrame to something nice */
    window.addEventListener('resize', resizeFrame)
    window.addEventListener('onload', resizeFrame)
    console.log("AMVARA resizing events enabled")
    
    /** -------------------------------------------------------------- AMVARA END --------------------------- **/
    /** -------------------------------------------------------------- AMVARA END --------------------------- **/
    /** -------------------------------------------------------------- AMVARA END --------------------------- **/
    ​

    Hope this helps :-) And thanks again for your feedback on the topic.

    Regards, Ralf


    ------------------------------
    Ralf Roeber
    https://linkedin.com/in/ralf-roeber-470425a/
    ------------------------------



  • 10.  RE: [QUERYSTUDIO] Cognos Portal prevents starting QS with Microsoft Edge Chromium v88 & Chrome v88

    Posted Wed July 28, 2021 08:54 AM
    Hi, i think Problem 2 could be solved by modifying <install_dir>/templates/ps/system.xml. Just add „chrome" to the capability param „canUseQueryStudio" and restart the system (old kb-doc but worked for activating AS for Chrome/Edge in Cognos 11.1: https://www.ibm.com/support/pages/not-all-studios-appear-welcome-page-cognos-version-10-when-using-chrome-browser).

    ------------------------------
    Gerhard Lang
    ------------------------------



  • 11.  RE: [QUERYSTUDIO] Cognos Portal prevents starting QS with Microsoft Edge Chromium v88 & Chrome v88

    Posted Mon September 12, 2022 11:02 AM
    Hello Ralf,

    Thanks a lot for sharing your solution.
    I am facing the same kind of issue regarding Analysis Studio and try to apply your URL Rewrite in iis.

    Could you please confirm that url redirect is at default website level (and not at \bi level).

    Thanks a lot for your help,

    Xavier


    ------------------------------
    Xavier Votion
    ------------------------------



  • 12.  RE: [QUERYSTUDIO] Cognos Portal prevents starting QS with Microsoft Edge Chromium v88 & Chrome v88

    IBM Champion
    Posted Tue September 13, 2022 03:51 AM

    Hello Xavier,

    the rewrite rule for IHS (not IIS!!) is:

    RewriteCond %{HTTP_REFERER} (crn[^\/]).+classicviewer.+id=(?:XSSSTART)?(.[^&]+)(?=XSSEND) [NC]RewriteRule ^/(crn[^\/]+)/bi/v1/disp$ %{HTTP_HOST}/$1/cgi-bin/cognos.cgi/bi/v1/... [NE,R=301,L]???

    We use https://server/crn[0-12]/bi/... so the $1 corresponds to the crnX in the URL. I guess this is what you are asking for?

    All the rest is standard.

    Regards,

    Ralf


    --  Ralf Roeber Managing Partner | He/His w:http://amvara.io | e:ralf.roeber@amvara.io | m:+34 717 102 603 | li:/in/ralf-roeber





  • 13.  RE: [QUERYSTUDIO] Cognos Portal prevents starting QS with Microsoft Edge Chromium v88 & Chrome v88

    Posted Tue September 13, 2022 04:06 AM
    Hi Ralf,

    Thanks for your quick feedback!
    That's indeed what I am looking for!

    Thanks again,
    Xavier

    ------------------------------
    Xavier Votion
    ------------------------------



  • 14.  RE: [QUERYSTUDIO] Cognos Portal prevents starting QS with Microsoft Edge Chromium v88 & Chrome v88

    Posted Mon February 20, 2023 09:47 AM

    Hi Xavier,

    Did you manage to make the redirect in IIS?

    Thanks,

    Dominique



    ------------------------------
    Dominique Courchesne
    ------------------------------