Cache Refresh Settings

The performance of Enterprise Console can be improved by reusing previously fetched resources. The caches reduce latency and network traffic and thus lessen the time needed to display a representation of a resource. By making use of HTTP caching, Enterprise Console become more responsive.

Enterprise Console Web Application makes use of clientCache element of the staticContent element, which update the HTTP Header Cache-Control with must-revalidate and max-age request directives. The value set for the max-age request directive is 1 hour, which can be set using the cacheControlMaxAge attribute of the clientCache element.

After the product is installed, you can change the cacheControlMaxAge attribute value as per your requirement. The Enterprise Console Web Application's web.config file related to the caching is usually located at <product installation path>\Web\BPMUITemplates\Default\web.config and would contain the clientCache settings as below:

<system.webServer>

<staticContent>

<clientCache cacheControlCustom="private, must-revalidate" cacheControlMode="UseMaxAge" cacheControlMaxAge="0.01:00:00" />

</staticContent>

</system.webServer>

It is recommended to set the cacheControlMaxAge attribute value to 0 for a staging or non-production environment, as there would be frequent changes to the files/resources used by the site, which is used for development.

Note: If you change the .js, .css, or image files, the changes for the same would be reflected in the browser as per the cacheControlMaxAge attribute in the web.config file.