The CMS acts as the central collector of ‘event data’ (captured or imported messages). Each CA DataMinder event comprises metadata, written to the local CA DataMinder database, and a blob (Binary Large Object) file, saved on physical media. The CMS is responsible for building the event database, event object store and temporary object store. These components are summarized below:
The object store contains the blob files. A blob file contains the email content and any attachments, stored in CA DataMinder format. The blob file is written to disk and saved in the \Data folder or migrated to a third party object store.
Note: If required, the object store can be a remote data folder, for example UNC-specified network file share or a network-attached storage (NAS) device.
The temporary object store is a subfolder of the object store and it contains cached blob files which are also stored on a third party storage device.
Full details about tables and indexes are in the CA DataMinder Database Schema, available from CA Support at http://ca.com/support.
|
Copyright © 2014 CA.
All rights reserved.
|
|