

Archive Integration Guide › Third-Party Integration
Third-Party Integration
The following section focuses on CA Data Protection integration with third-party solutions such as email archiving applications. You can also integrate custom archives.
In particular, this section describes how emails stored in a third-party archive are still searchable using the iConsole or Data Management console; and how, for some integrations, emails can be categorized (using smart tags) before they are archived.
How archive integration works
- The archive passes an email (or file) to CA Data Protection for policy analysis.
- CA Data Protection returns optional SmartTags for the archive to store.
- The Archive passes a unique ID which CA Data Protection stores in the database with the event.
- An event BLOB is stored in the 30-day cache of the CMS.
- If the data is needed after expiry from the cache (for example, because a user accesses an event in the iConsole), the CMS makes a request to the Remote Data Manager. The Remote Data Manager retrieves the email form the archive and stores it back in the 30-day cache.
Copyright © 2015 CA Technologies.
All rights reserved.
 
|
|