Example Import Configuration File

Archive Integration Guide › Event Import › Example Import Configuration File

Example Import Configuration File

Each parameter begins on a new line. If a parameter value contains spaces, you do not need to enclose the parameter in double quotes. Below is a typical configuration file for a simple import operation from an EAS email archive.

Note that the parameters to define the CMS logon account are not included in this file (for security reasons). To add comments to a configuration file, use any of the following formats: #, // and REM. The full range of available parameters are shown in Event Import parameters.

This example specifies a continuous EVF import operation.

Parameters	Description
import.type=evf	Specifies an EVF file import operation.
Engine.StopOnError=No Engine.LogLevel=3	Non-critical importing errors are ignored. Full log details are written to the CA DataMinder system logfile.
# Specify continuous import	Adds a comment.
File.ContinuousInput=yes File.pathspec=\\W2K-UPX01\EASCache File.includesubdirs=No	Continuous importing is specified. This is essential when using the wgnimpsv.exe service. The source folder is defined as \EASCache on machine W2K-UPX01. The NBA does not write captured files to subfolders, so Event Import does not need to search subfolders.
// Specify email configuration	Adds a comment.
EMail.EventDateFromEMail=yes Email.InternalAddrPattern=unipraxis	Capture dates are based on the dates in the e‑mails. When detected in an email address, the term ‘unipraxis’ signifies an internal email.
REM Specify import filter	Adds a comment.
Email.SenderAddrIncludeFilter=unipraxis	Only emails sent by users whose email address contains ‘unipraxis’ are imported.

More information:

Event Import Parameters