Deployment Guide › Event Import › Event Import Parameters › File Handling Parameters

File Handling Parameters

These parameters can be used to configure file handling in any type of import operation. They cover such areas as the location of the source files to be imported, and whether to search subfolders for target files and delete source files after a successful import. There is also a ‘continuous import’ parameter that causes Event Import to repeatedly scan the target folders for files to be imported.

File.Pathspec

This parameter has no default value. It specifies a fully‑qualified path to the folder on the source machine containing the source files. The syntax is:

File.Pathspec=<file path>

For example:

File.Pathspec=C:\msgs\all_messages.msg or \imports\*.pst.

If you only specify a path, Event Import infers a file specification based on Import.Type. When specifying the path, be aware of the following:

Paths containing spaces

If you specify File.Pathspec directly in a command line and the name of a file or folder in the path contains spaces, you must enclose the entire parameter in "double quotes". For example:

wgnimp -f params.ini "File.Pathspec=C:\My messages\File1.msg"

Conversely, if you specify File.Pathspec in a configuration file, you must not enclose the path in double quotes, even if it contains spaces:

File.Pathspec=C:\My messages\File1.msg

Paths containing # hash characters

If you specify File.Pathspec in a configuration file, you must edit any path containing a hash character '#' to ensure that wgnimp.exe interprets the path correctly. Specifically, you must prefix each hash with a backslash '\'. For example, change this:

File.Pathspec=C:\Messages\File#1.msg

To this:

File.Pathspec=C:\Messages\File\#1.msg

File.IncludeSubdirs

Defaults to No. This parameter specifies whether to search for matching files in subfolders below the source folder specified by File.Pathspec (see above). The syntax is:

File.IncludeSubdirs=Yes or No

The file specification is determined by the Import.Type parameter.

File.DeleteAfterImport

Defaults to No. This parameter specifies whether to delete the source files after an import operation. The syntax is:

File.DeleteAfterImport=Yes, No or Always

If set to:

No

The source files are never deleted. (If used with File.ContinuousInput=Yes, then the import operation will fail to start, as you cannot use these parameters together in such a way.)

Yes

The source file is only deleted after a successful import operation.

Always

The source file is always deleted, whether the import succeeds or not, and even if File.ContinuousInput=Yes (see below).

File.ContinuousInput

Defaults to No. This parameter specifies whether Event Import repeatedly scans for and imports files specified by File.Pathspec, or whether it shuts down after the input directories and files have been processed. The syntax is:

File.ContinuousInput=Yes or No

Continuous import is necessary when Event Import is running as a service and perpetually scanning an input directory.

Multiple event import processes can process a single input path when this parameter is set to Yes. To support this concurrency, a file is moved to a subdirectory of the input path while being processed. This prevents other instances of Event Import from trying to import it.

Important! If this parameter is set to 'No', you must add the parameter File.IncludeSubdirs=Yes to your import.ini file.

If this parameter is set to Yes:

• It creates a \Failed subfolder on the source machine below the 'importing machine' folder (see the note below). Any files that fail to be imported are moved into this subfolder. But if File.DeleteAfterImport=Always (see above), then any 'failed' files are deleted and the \Failed subfolder is not created.

  Note: Each machine running Event Import creates its own subfolder below the folder specified by File.Pathspec on the source machine. This subfolder has the same name as the machine running Event Import. For example, if Event Import on machine UNI-KEEGAN fails to import a file, it creates the folder <File.Pathspec>\UNI-KEEGAN\Failed on the source machine.

• File.IncludeSubdirs is invalid and will fail if set to Yes. This is because Event Import creates its own subdirectory.
• File.DeleteAfterImport must be set to either Yes or Always. The import operation will fail if this parameter is set to No.

File.ParticipantsFromNBAFilename

This parameter applies to files captured by the NBA during file upload and download operations and FTP transfers. It determines whether Event Import extracts the source and destination machine IP addresses from the NBA-generated file name and saves this address in the event participants table in the CMS database. The syntax is:

File.ParticipantsFromNBAFilename=Yes or No

By storing the machine IP addresses as an event participants, this provides a mechanism for associating file uploads, downloads and FTP transfers with individual CA DLP users. In CA DLP terms, these machine addresses are referred to as ‘pseudo user addresses’. But note the following:

For details about NBA-generated file names, see the Network Implementation Guide; search the index for ‘filename formats’.

Important! Only use this parameter if your organization assigns static IP addresses to users’ computers. This parameter is not appropriate you use DHCP!

• To ensure that the resulting file events are searchable by user in the iConsole or Data Management console, CA DLP administrators must first add the relevant machine IP addresses to users' address lists in the Administration console.
• This parameter does not apply to files sent as email attachments. These are mapped to CA DLP users by conventional email addresses.