Deployment Guide › Third-Party Integration › Autonomy Message Manager Integration

Autonomy Message Manager Integration

CA DLP can integrate with Autonomy Message Manager. This is an enterprise message archival and management suite of products that enables organizations to manage and archive huge volumes of messages (emails and IM conversations). This section summarizes how to set up CA DLP to integrate with Message Manager.

Note: For full details about Message Manager, please refer to your Message Manager documentation.

Note: For supported versions of Message Manager, see Supported archive versions.

The diagram below shows an example deployment with, for simplicity, a single Mail Processor server for Message Manager. Using the CA DLP External Agent API, Message Manager passes messages to a local CA DLP hub and policy engine. Included with each message is a unique identifier.

The policy engine then processes these messages. If a message causes a policy trigger to activate, a CA DLP event is generated. The unique message identifier, plus any smart tags generated by policy triggers, are saved with the event’s metadata.

The event, including its metadata, is then replicated to the CMS. Note that the actual email or IM content is not saved on the CMS; instead, the event record in the CMS database includes the unique identifier that references the associated message in the archive.

Finally, the Remote Data Manager uses the message identifiers to retrieve the associated emails or IM conversations from the Message Manager archive during subsequent iConsole event searches.

CA DLP integration with Message Manager

1. Message Manager servers: These servers include a Mail Processor server (1a) and an Archive server (1b).
2. External Agent API and PE hub: The External Agent (2a) provides the interface that the Mail Processor (1a) uses to pass messages, via the hub (2b), to the local policy engine (3). Each message passed to the policy engine includes a unique identifier.
3. Policy engine: This analyzes the messages received from Message Manager and applies policy triggers as necessary.
4. CMS: Events generated as a result of policy processing, including metadata that incorporates the unique message identifiers, are replicated to the CMS and stored in the database (4a). In this example, the CMS also hosts the Remote Data Manager (4b).
5. iConsole: When ther iConsole displays captured emails, the Remote Data Manager retrieves data for archived e‑mails and IM conversations from the archive (1b).