Network Integration Guide › Importing NBA Events › Importing Events Overview

Importing Events Overview

Note: Importing events is not the preferred ingestion method. More commonly, the NBA runs in ‘output to socket’ mode, passing items to CA DataMinder policy engines for analysis and capture.

The CA DataMinder Import Policy utility connects Event Import to policy engines in order to apply triggers to emails or files as they are imported. If you run the NBA in ‘output to disk’ mode, you can use Import Policy to apply policy ‘after the event’ to any emails or files imported from the NBA. For example, you can categorize, or apply smart tags to, IM conversations or emails sent using Hotmail or Yahoo! For details about Import Policy, see the Archive Integration Guide.

The following sections describe the steps needed to set up Import Policy jobs for the NBA:

1. Specify user accounts for NBA import operations.
2. Set up Event Import. Specifically, you must configure the file and email import operations.
3. Verify that the necessary CA DataMinder user policies are correctly set up.

   User policies are described in Apply User Policy to NBA Events.

4. Verify that machine policy settings for your policy engines are correctly set up.

   These settings are described in the Policy Engines chapter of the Platform Deployment Guide.

   

Example NBA import policy operations

Two Import Policy servers are deployed (2). One ingests files; the other ingests emails. In each case, Event Import (2a) imports items from the NBA (1) and passes these events via a hub (2b) to a shared pool of policy engines (3) for processing. The resulting events are replicated to the CMS (4).