These settings cover database management on CA DataMinder machines. They determine whether data compression is used, how often the local databases is purged, and how CA DataMinder handles free disk space.
These settings cover the optional parameters to configure the integration of your Centera device. For example, they determine the number and size of BLOB files stored in a Centera device, and the method used to calculate the Content Address from BLOB files.
These settings cover the optional parameters to configure the integration of your IBM DB2 Content Manager. For example, they determine the number and size of BLOB files stored in the Content Manager, and the credentials for the Content manager Interface Service.
If required, you can compress stored data on CA DataMinder servers and client machines. Specifically, you can compress the 'blobs' (Binary Large Object files), containing policy data and, on the CMS and gateways, captured data.
For each machine, you determine the frequency and time of each purge, plus the minimum retention period that captured events are retained before they are earmarked for purging. Other settings provide further control over purge operations. For example, you can choose to suspend the CA DataMinder infrastructure during purge operations or you can specify a purging timeout.
For each machine, you can specify a warning level and an error level of free disk space. You can also specify how often free disk space is checked. When free disk space falls below the warning level, CA DataMinder adds a series of warnings to the Activity logfile. When free disk space falls below the error level, the CA DataMinder infrastructure is suspended.
These settings cover the optional parameters to configure the integration of the temporary object store. For example, you can configure how long events remain in the object store before being deleted. For details, see the Platform Deployment Guide.
|
Copyright © 2014 CA.
All rights reserved.
|
|