Use custom caching
We can overrule the default caching parameters of a site using "cache" and "expire" parameters in URLs and IBM Web Content Manager tags.
Custom caching can only be used when a server's default Web Content cache is set to none or advanced caching. If basic caching is used as the default web Content cache, Custom caching cannot be used.
There are two basic methods in which custom caching can be used with the default server caching settings:
- Default Server Caching Enabled
- In this scenario, some form of default server caching has been enabled. Caching parameters within connect tags and URLs can be used to either:
- Disable caching for the data being requested.
- Apply different caching parameters to the data being requested.
This method is used with sites that are mostly static, but which contain a few dynamic elements that require a different caching strategy from the server's default caching strategy.
- Default Server Caching Disabled
- In this scenario, default server caching has been disabled. Caching parameters within connect tags and URLs can be used to enable caching for the data being requested.
This scenario is used with sites containing a large number of elements requiring different caching strategies.
- Cache parameters
We use "cache" parameters in IBM Web Content Manager tags and URLs to specify whether the retrieved data should be cached or not, and if so, how it should be cached. The "cache" parameter is not mandatory.
- Cache expire parameters
Use "expires" parameter in IBM Web Content Manager tags and URLs to specify how long to maintain data in the cache before it is expired. Once data expires from a cache, the next request for the data will be retrieved from the original server. The expires parameter is not mandatory.
- Caching IBM Web Content Manager elements
We can apply caching to elements using "connect" tags to reference elements within presentation templates instead of the component or element tag.
Parent: Tags