Oracle Analytics Cloud and Server

Home› Oracle Analytics› Oracle Analytics Forums› Oracle Analytics Cloud and Server› Oracle Analytics Cloud and Server

Categories

Welcome to the Oracle Analytics Community: Please complete your User Profile and upload your Profile Picture

Behaviour of OAS saw.dll?ReloadDashboard different on two OAS instances why?

Accepted answer
83
Views
10
Comments
Timothy Dickinson
Timothy Dickinson Rank 3 - Community Apprentice
in Oracle Analytics Cloud and Server

We have different behaviour in PROD and DEV OAS instances on opening a classic BI dashboard.
PROD always fires an ajax call = saw.dll?ReloadDashboard on opening any dashboard with content even the smallest static prompt or text box ,but, DEV does not, even with complicated dashboard with multiple objects. We see this behaviour in chrome developer tools. We have identical prompts / RPD / instanceconfig.xml and nqsconfig.ini between instances. everything is identical. We have tried avoiding load balancer etc direct URLS but same result. Opening a blank dashboard in PROD does not cause the reloadDashboard to fire, but, even a basic text box on the dashboard will cause the reload on opening the dashboard?

The initiator of reloaddashboard is ajax.js:1 and saw.dashboard._reloadAlt is called by portalscript.js:1 but we can't see any differences here between DEV and PROD here either.

Why does this matter? we don't like unexplained differences between PROD and DEV, also, it has caused some issues prompting new dashboard between dev and prod.

We have an SR open with Oracle but so far nothing has been suggested to explain behaviour, We are thinking perhaps internal to OAS if there is a certain load on server as there will be with PROD then OAS internally calculates it need to initiate reloaddashboard.
Any help from this community is more than welcome.
Tim

Best Answers

  • SteveF-Oracle
    SteveF-Oracle Mod
    edited Mar 11, 2025 8:14PM Answer ✓

    Hi Tim,
    This internal call is not documented, but basically it is getting called at intervals until the complete request is returned to the client. If the client receives the complete request on the initial call, then ReloadDashboard does not happen.

    I think you are on the right track with differences between a low/volume, low data environment vs. a loaded production environment. There is no harm in the call. Some things you could do to minimize it:

    + Make sure the dashboard is designed well.
    + Make sure the queries perform well.
    + Make sure network latency is not an issue.
    + Configure an HTTP Server to compress and cache static content.
    + Make sure the servers are sized for the peak load capacity (horizontal scale)

    I am probably forgetting some things, but just some general off the cuff tips.

    Hope that helps somewhat, other comments certainly welcomed.



  • Timothy Dickinson
    Timothy Dickinson Rank 3 - Community Apprentice
    Answer ✓

    @SteveF-Oracle thanks for the reply :) I really appreciate your efforts!

  • Tim Dickinson UK
    Tim Dickinson UK Rank 2 - Community Beginner
    Answer ✓
    https://community.oracle.com/products/oracleanalytics/discussion/comment/64885#Comment_64885

    we have tracked this down as the actual reason for this behaviour, it might be useful for other OAS users https://blogs.oracle.com/analytics/post/oracle-analytics-dashboard-rendering-mode-options

Answers