Archive Integration Guide › EMC SourceOne Integration › Overview

Overview

CA DataMinder can integrate with the EMC SourceOne archiving solutions for Microsoft Exchange and Lotus Notes Domino. It can also integrate with EMC SourceOne when it is being used to archive internet emails.

Integration is provided through a business component extension (BCE) for SourceOne, wgnemcs1.dll. In This section, the term ‘SourceOne archive agent’ refers to this BCE.

How does the integration work? SourceOne extracts emails from Exchange or Domino or from an internet email drop folder. They are then passed to CA DataMinder policy engines for analysis and processing. When processing is complete, the emails, plus any resulting smart tags, are returned to SourceOne for storage in the archive. SourceOne can then use these smart tags to distribute emails across different archives based on criteria indicated by the smart tags. For example, you can use smart tags to indicate archive retention periods.

Note: Internet emails are stored as EML files and conform to RFC 2822. They are commonly referred to as internet emails because of the RFC document, ‘Internet Message Format’, that describes them.

The key components are illustrated in the diagram below. For simplicity, this diagram shows SourceOne installed on a single server, and the SourceOne archive agent passing emails to a single CA DataMinder policy engine. In practice, large organizations may have a distributed SourceOne deployment and use multiple policy engines.

CA DataMinder integration with SourceOne archive

1. Email source. SourceOne extracts emails from an Exchange journal mailbox (1a) or, for Domino, from the EMC Mail Journal Database (1b). Or it extracts internet emails from a drop folder (1c).
2. EMC SourceOne management server. SourceOne (2a) extracts emails from the journal mailbox or journal database and passes them to the SourceOne archive agent (2b). In turn, the archive agent passes emails to a policy engine hub (2c). The hub then distributes emails to policy engines (3).
3. Policy engine. The policy engines analyzes emails, applies policy triggers, and attaches smart tags as necessary.
4. EMC SourceOne archive. Processed emails plus any resulting smart tags are returned to SourceOne for archiving. This example shows two archives, one for storing emails with short retention periods (4a) and the other used for storing emails with longer retention periods (4b).
5. 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. In this example, the CMS machine also hosts the Remote Data Manager (7).
6. iConsole. Reviewers can search for archived emails.
7. Remote Data Manager. When a user searches for archived emails in the iConsole (6), the Remote Data Manager retrieves data for these emails from the archive (4).