Document caching
Content Manager provides caching options for clients and Workgroup Servers for metadata and objects, i.e. documents. In both arrangements, Content Manager caches metadata in volatile memory and writes the object cache to disk. Object cache for clients can be individually turned on and off and allow for a size capacity.
Retentive caching means all documents created or viewed by this Workgroup Server's clients are retained up to the limits set. Limits do not have to be set.
The Workgroup Server cache repository has the same structure as the object store.
This enables manually establishing a cache on initial installation by copying the object store structure to the Workgroup Server cache and pre-fetching certain documents easily, as the structures are identical.
It is not possible to view an outdated document when using Content Manager's cache.
Content Manager gives updated documents a new object ID in the Content Manager store and therefore in the cache, as well.
The details of the object ID are updated and maintained within the RDBMS metadata.
Content Manager uses the metadata as the authority to identify its object; previous objects are maintained as revisions.