Note: We expect the current version of CA Data Protection to integrate successfully with Autonomy ZANTAZ EAS, but this integration has not been tested."
CA Data Protection can integrate with the Autonomy ZANTAZ EAS solution. This section summarizes how emails are extracted from the EAS archive and imported into CA Data Protection. The diagram below summarizes the key components and processes involved.
For simplicity, the diagram shows a single email archive server, feeding data into a single EVF file cache. In practice, a large organization may have many such servers feeding data into multiple caches.
CA Data Protection integration with Autonomy ZANTAZ EAS
1 This server hosts the email archive solution, EAS (1a). This connects to an email server such as Microsoft Exchange (2) and archives messages in the email store (9).
The EAS archive solution uses an indexer process, EAS IndexerService.exe (1b), which in turn passes data to the External Agent API (1c).
The External Agent API extracts archived emails and saves them as EVF files in a cache (3). This cache provides the source data for the CA Data Protection Event Import utility (4). This utility requires the CA Data Protection infrastructure. For very large email archives, you may need to run multiple Event Import utilities simultaneously to avoid import bottlenecks.
Each Event Import utility imports archived emails into the CMS (5). The actual message data is not saved on the CMS; instead, a record in the CMS database for each imported email references the associated entry in the email store (9).
When displaying captured emails in the iConsole (6), the Remote Data Manager utility (7) retrieves data for emails archived in the email store (9). In the case of EAS, these data requests are sent via Microsoft IIS (Internet Information Services) (8).
|
Copyright © 2015 CA Technologies.
All rights reserved.
|
|