Archive Integration Guide › Third-Party Integration › Integration Models › Model 1: Push from Archive
Model 1: Push from Archive
The following illustration describes this model:
Integration model 1: Push from archive
In this model, a third party application (step 2 in the diagram below) passes archived emails from a journal mailbox (1) to CA DataMinder. At this point in the integration model, there are four methods (4a through 4d) for ingesting the emails into the CMS:
- 4a: Agent outputs to local policy engine: The archive solution notifies a CA DataMinder integration agent (3) that emails are available for processing. The agent then passes the emails to a local policy engine (4a). The resulting events are replicated to the CMS (5).
- 4b: Agent outputs to policy engines via hub: As for 4a, except that the CA DataMinder agent passes the emails to remote policy engines via a PE hub (4b).
- 4c: Agent outputs to EVFs for direct import into the CMS: The archive solution uses the CA DataMinder External Agent API (3) to convert the archived emails to event (EVF) files. These EVFs are saved in a cache (4d), from where they are subsequently imported directly onto the CMS (5).
- 4d: Agent outputs to EVFs to be ingested by Import Policy job: The archive solution uses the External Agent API (3) to convert the archived e‑mails to event (EVF) files. These EVFs are saved in a cache (4c), from where they are retrieved by Event Import and passed to a local policy engine for processing. The resulting e‑mail events are then replicated up to the CMS (5).
For details about the operational benefits associated with each ingestion method. In all cases, only the event metadata is saved on the CMS. The actual message data is not stored on the CMS; instead, a database record for each email references the associated entry in the archive.
Archive integrations currently using this model are listed beliow.
More information:
Autonomy ZANTAZ EAS Integration
Symantec Enterprise Vault Integration
EMC SourceOne Integration
IBM Content Collector
Copyright © 2014 CA.
All rights reserved.
|
|