Client browsers
that display dashboards with SAS BI Dashboard 4.31 use Adobe Flash
Player in the Rich Internet Application (RIA) architecture. Content
objects and data referenced by each user are retained in the browser
client under Flash. The parameters for size and refreshing for each
client is controlled by the
config.xml file
that resides in
SAS-configuration-directory/sas.bidashboard4.3.ear/sas.bidashboard.war/DashboardRuntime directory.
If client cache content is not cached in the middle tier, it is not
invalidated.
The default values set
in the
config.xml file should be adequate
for most environments. If the users in your environment have unusually
high numbers of indicators, consider increasing the values for the
size and refresh parameters for client caching.
Client caching is affected
by three types of refreshes or timestamp checks. The
config.xml file
controls how often the cached client content is timestamped. If the
timestamp is determined to be outdated, the client cache is marked
as being invalid. This client cache is refreshed only if it is needed
by another transaction.
If needed, users can
force a browser to refresh by using the browser's refresh or reload
options. As a result, the client cache is refreshed, and the current
dashboard will be displayed. Users can also request an automatic refresh
cycle that displays the current dashboard with the current client
cache, and retrieve any information that is not in the cache. However,
this process does not force the client cache objects to be updated
unless they were marked as invalid by the timestamp checks. Typically,
timestamps occur every five minutes.
Timestamp checks only
compare timestamps between the caches for the client and the middle
tier. If the data or content is not cached in the middle tier, the
client cached objects are marked as invalid.