Content Manager Enterprise Studio 25.1 Enterprise Studio

# 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

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.

Structure

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.

Revisions

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.

Tables

Metadata tables cached on the Workgroup Server are relatively static tables and are designed to give quick access to the system when logging on.

Security, Record Types and the Thesaurus tables are cached and updated at the Workgroup Server.

Related information

Copyright 2008-2025 Open Text
Version 25.1 | Last updated October 2024
Contact

Send documentation feedback

Close

Send documentation feedback

To send feedback using your default email client, open an email window.

Otherwise, send your feedback and the information below to hprmdocumentation@microfocus.com.

We appreciate your feedback!

Product: Content Manager Enterprise Studio 25.1

Topic Title: Document caching