...
Setting | Description | |||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
From the drop-down list select Multi Directory. | ||||||||||||||||||||||||||||||
Enter the path and the name of the control TXT file.
| ||||||||||||||||||||||||||||||
Filename | The regular expression of the names of the source files on the local file system. Regular expressions according to Java syntax apply. For further information, see http://docs.oracle.com/javase/8/docs/api/java/util/regex/Pattern.html.
| |||||||||||||||||||||||||||||
Select this check box to abort the workflow if a directory, that is specified on the control file list, is missing on the server. Otherwise, the workflow continues to execute (default). | ||||||||||||||||||||||||||||||
Select this check box to prevent the collection of the same file more than once. Files are considered to be duplicates if the absolute filename is the same.
The workflow holds an internal data structure with information about which files the collector has collected in previous executions. The data structure is purged by the collection strategy based on the contents of the collection directories. If files collected in the past are no longer found in the collection directory they are removed from the data structure.
It is possible to manually purge the internal duplicate data structure if needed. To do this, disable the duplicate filter and run the workflow. The next time a duplicate filter is enabled the internal data structure will be empty. | ||||||||||||||||||||||||||||||
Select this check box to enable the generation of error or debug messages.
|
Scroll pagebreak |
---|