| Setting | Description |
|---|
Collection Strategy | If there are more than one collection strategy available in the system, a Collection Strategy drop down list will also be visible. For further information about the nature of the collection strategy, see 11. Appendix 4 - Collection Strategies. |
Directory | Absolute pathname of the source directory on the remote host, where the source files reside. If the FTP server is of UNIX type, the path name might also be given relative to the home directory of the User Name account. |
| Include Subfolders | Select this check box if you have subfolders in the source directory from which you want files to be collected. | Note |
|---|
| Subfolders that are in the form of a link are not supported. |
If you select Enable Sort Order in the Sort Order tab, the sort order selected will also apply to subfolders. |
Filename | Name of the source files on the remote host. Regular expressions according to Java syntax applies. For further information, see http://docs.oracle.com/javase/8/docs/api/java/util/regex/Pattern.html.
| Info |
|---|
| To match all file names beginning with TTFILE , type: TTFILE.* |
| Note |
|---|
| When collecting files from VAX file systems, the names of the source files include both path and filename, which has to be considered when entering the regular expression. |
|
Compression | Compression type of the source files. Determines if the agent will decompress the files before passing them on in the workflow. |
Move to Temporary Directory | If enabled, the source files will be moved to the automatically created subdirectory DR_TMP_DIR in the source directory, before collection. This option supports safe collection when source files repeatedly uses the same name. |
Append Suffix to Filename | Enter the suffix that you want added to the file name prior to collecting it. | Warning |
|---|
| Before you execute your workflow, make sure that none of the file names in the collection directory include this suffix. |
|
Inactive Source Warning (h) | If enabled, when the configured number of hours have passed without any file being available for collection, a warning message (event) will appear in the System Log and Event Area: The source has been idle for more than <n> hours, the last
inserted file is <file>. |
Move to | If enabled, the source files will be moved from the source directory (or from the directory DR_TMP_DIR if using Move Before Collecting), to the directory specified in the Destination field, after collection. | Note |
|---|
| The Directory has to be located in the same file system as the collected files at the remote host. Also, absolute pathnames must be defined (relative pathnames cannot be used). If a file with the same filename, but with a different content, already exists in the target directory, the workflow will abort. If a file with the same file name, AND the same content, already exists in the target directory, this file will be overwritten and the workflow will not abort. |
|
Rename | If enabled, the source files will be renamed after the collection, and remain (or moved back from the directory DR_TMP_DIR if using Move Before Collecting) in the source directory from which they were collected. | Note |
|---|
| When the File System Type for VAX/VMS is selected, some issues must be considered. If a file is renamed after collection on a VAX/VMS system, the filename might become too long. In that case the following rules will apply: A VAX/VMS filename consists of <file name>.<extension>;<version>, where the maximum number of characters for each part is: If the new filename turns out to be longer than 39 characters, the agent will move part of the filename to the extension part. If the total sum of the filename and extension part exceeds 78 characters, the last characters are truncated from the extension. An example: A_VERY_LONG_FILENAME_WITH_MORE_THAN_39_ CHARACTERS.DAT;5 will be converted to: A_VERY_LONG_FILENAME_WITH_MORE_THAN_39_. CHARACTERSDAT;5 |
| Note |
|---|
| Creating a new file on the FTP server with the same file name as the original file, but with another content, will cause the workflow to abort. Creating a new file with the same file name AND the same content as the original file, will cause the file to be overwritten. |
|
Remove | If enabled, the source files will be removed from the source directory (or from the directory DR_TMP_DIR, if using Move Before Collecting), after the collection. |
Ignore | If enabled, the source files will remain in the source directory after the collection. This field is not available if Move Before Collecting is enabled. |
Destination | Full pathname of the directory on the remote host into which the source files will be moved after the collection. This field is only available if Move to is enabled. |
Prefix and Suffix | Prefix and/or suffix that will be appended to the beginning and the end of the name of the source files, respectively, after the collection. These fields are only available if Move to or Rename is enabled. | Warning |
|---|
| If Rename is enabled, the source files will be renamed in the current (source or DR_TMP_DIR ) directory. Be sure not to assign a Prefix or Suffix , giving files new names still matching the Filename regular expression. That will cause the files to be collected over and over again. |
|
Search and Replace | Select either Move to or Rename option to enable Search and Replace. Search and Replace operate on your entries in a way that is similar to the Unix sed utility. The identified filenames are modified and forwarded to the following agent in the workflow. This functionality enables you to perform advanced filename modifications, as well: Use regular expression in the Search entry to specify the part of the filename that you want to extract. | Note |
|---|
| A regular expression that fails to match the original file name will abort the workflow. |
Enter Replace with characters and meta characters that define the pattern and content of the replacement text.
| Info |
|---|
| title | Search and Replace Examples |
|---|
| To rename the file file1.new to file1.old, use: - Search:
.new - Replace:
.old
To rename the file JAN2011_file to file_DONE, use: - Search:
([A-Z]*[0-9]*)_([a-z]*) - Replace:
$2_DONE
Note that the search value divides the file name into two parts by using parentheses. The replace value applies to the second part by using the place holder $2. |
|
Keep (days) | Number of days to keep moved or renamed source files on the remote host after the collection. In order to delete the source files, the workflow has to be executed (scheduled or manually) again, after the configured number of days. | Note |
|---|
| A date tag is added to the filename, determining when the file may be removed. This field is only available if Move to or Rename is enabled. |
|
| Route FileReferenceUDR | Select this check box if you want to forward the data to an SQL Loader agent. See the description of the SQL Loader agent in 9.75 SQL Loader Agent for further information. |