Archive Integration Guide › Import Policy › Import Policy versus Server Agents

Import Policy versus Server Agents

Import Policy has parallels with the Microsoft Exchange integration provided by the Exchange server agent (see Deploy policy engines). In both cases, events from an external source are passed to a policy engine.

But there is a key difference. Under Import Policy, when a control trigger activates, a control event is generated and saved on the CMS (for example, a warning or blocking). Using the iConsole, or Data Management console, these events can be searched for and reviewed in the normal way. But crucially, because the email has already been sent, the control action can never be invoked so warning dialogs are not actually shown, e‑mails are not actually blocked, and so on.

Also, because Import Policy requires no integration with production email systems, there is no risk of disruption to end-users’ email activity. Import Policy also eliminates the need for CA DataMinder client agents on the desktop and policy engines on the email server.

Note: The Exchange server agent requires Microsoft Exchange Server 2003 or 2007. If your organization uses an earlier version of Microsoft Exchange, you may want to use Import Policy as a substitute mechanism for monitoring email activity.

Import Policy versus email server agents

Email ingestion

Under Import Policy, source data is extracted from Exchange journal mailboxes or email archive files (1a) then converted into CA DataMinder events by Event Import (2a). Conversely, email server agents (2b) simply intercept emails transiting through Exchange or Domino servers (1b).

Email processing

In all cases, imported or intercepted emails are passed to a policy engine for processing. In direct mode, Import Policy passes imported emails straight to a local policy engine (4a). Conversely, Import Policy in hub mode passes e‑mails to a local policy engine connector (3a). This is identical to how email server agents work, passing emails to a local policy engine hub (3b). In both cases, the policy engine connector and hub then allocates emails to a policy engine, typically on a remote server (4b). In all cases, the policy engine then applies capture and control triggers as needed.