We recommend that you configure your policy engine to save events to the CMS at the same time that it applies policy and adds smart tags to them. (For details, see the CA DataMinder Administration console online help; search the index for: ‘captured data, emails’). This removes the need for Import Policy and therefore any additional policy engines. This is the most efficient process, unless your policy is particularly intense.
If this is the case (for example, your policy involves a deeper analysis of events), it may be more efficient to de‑couple policy analysis from the processing of the Universal Adapter. In other words, we recommend that you do not configure the policy engine to save blob files to the database after applying policy and adding smart tags, but instead, send the blob files back to the Universal Adapter which can then output them to EVF files. These EVF files can then be processed via Import Policy and replicated up to the CMS. This ensures that the Universal Adapter rate is kept as high as possible and does not impact the archiving process.
|
Copyright © 2014 CA.
All rights reserved.
|
|