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.
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:
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
Event Import only recognizes paths to mapped drives (for example, "Z:\Pickup Folder") when you run individual import operations using the Event Import utility, wgnimp.exe, from a command line.
Event Import cannot recognize paths to mapped drives when you run continuous import operations using the Event Import service (wgnimpsv.exe).
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
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.
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:
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.)
The source file is only deleted after a successful import operation.
The source file is always deleted, whether the import succeeds or not, and even if File.ContinuousInput=Yes (see below).
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:
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.
|
Copyright © 2014 CA.
All rights reserved.
|
|