Previous Topic: How CA DataMinder Events Are StoredNext Topic: Managing the Temporary Object Store


Configure the Temporary Object Store

Using settings in the CMS policy, you can configure how long events remain in the temporary object store and how long the RDM waits for a response from the CMS when attempting to retrieve events. After the configurable timeout (see below), blobs in the temporary objects store are deleted. Any subsequent searches for these events must use the Remote Data Manager.

To configure the temporary object store, use the following settings in the Infrastructure\Data Management folder in the CMS machine policy:

Remote Data Cache Timeout (Minutes)

Specify how long (in minutes) data retrieved from the Remote Data Manager (RDM) server is retained in a temporary local cache. After this period, the cache is deleted. The minimum timeout is 1 minute; the maximum timeout is 525600 minutes (365 days).

The default timeout is 4320 minutes. This means the cache is deleted every 3 days. You may need to increase the default timeout for newly deployed CA DataMinder installations if you are using the Content Indexer to index large volumes of captured data.

Note: Be aware of the following:

Remote Data Request Timeout (Seconds)

Specify how long (in seconds) the CMS will wait for a response from the Remote Data Manager (RDM) server. If this timeout expires before the RDM can retrieve an event, CA DataMinder displays a error message. For example, an error message is shown if the Data Management console is unable to display an archived email because this timeout has expired.