Resource Caching

By default, all resources used by custom client applications are cached by the browser.

Consequently, when you make and publish changes to an application, those changes may not be immediately reflected because the browser is using a cached copy of some or all changed resources. (It is of course possible to fix this by clearing the browser cache and reloading the page, but this may not be desirable in all cases.)

If this default behavior is unsuitable, you can switch off caching for specific file extensions. You do this in TIBCO Administrator, by editing the wr.nonCacheableExtensions substitution variable on the amx.bpm.app application. (The default setting for this variable is .nocache.js.)

Note: If SSL is enabled, the extensions listed in wr.nonCacheableExtensions are only not cached when SSL caching is also enabled (wr.isSSLCacheable is true).

If SSL is not enabled, the extensions listed in wr.nonCacheableExtensions are always not cached.

Note: Changing the value of wr.nonCacheableExtensions causes the amx.bpm.app application to go Out-of-Sync. You must re-deploy amx.bpm.app and wait until it has completely restarted. When you subsequently publish an application, any changes made to files with the specified extensions will not be cached and so will be immediately visible.

For example, suppose you are updating the MobileCaseManagement1 application and you want to make changes to the MobileCaseManagement1.config.json configuration file. Changing wr.nonCacheableExtensions to .nocache.js,.config.json (and then redeploying amx.bpm.app) will prevent MobileCaseManagement1.config.json from being cached. When you publish the updated application, the changes will be immediately visible.

For more information about wr.nonCacheableExtensions and wr.isSSLCacheable, see "Enhancing Security in ActiveMatrix BPM" in TIBCO ActiveMatrix BPM Administration.