To open the Disk-Deprecated collection agent configuration dialog from a workflow configuration, you can do either one of the following:
- right-click the agent icon and select Configuration...
- double-click the agent icon
Disk_Deprecated Tab
The Disk_Deprecated tab contains settings related to the placement and handling of the source files to be collected by the agent.
Disk_Deprecated collection agent - Disk_Deprecated tab
File Information
| Setting | Description | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Directory | Enter the path of the source directory on the local file system of the EC, where the source files reside. The path can be absolute or relative to the During processing of a file, it will be temporarily stored in a subdirectory under | ||||||||||
| Filename | Enter an expression that matches the source files on the local file system. Regular expressions according to Java syntax applies. For further information, see: http://docs.oracle.com/javase/8/docs/api/java/util/regex/Pattern.html
| ||||||||||
| Compression | Select Gzip to decompress files before collection and insertion into the workflow. If the collected files are not compressed, select No Compression. | ||||||||||
| Polling Interval (ms) | Enter the interval, in milliseconds, at which the source directory is to be scanned for new files. | ||||||||||
| File Reader Size | The agent moves files to the temporary directory for processing in bulk. Enter the maximum number files that can be included in each bulk move operation. | ||||||||||
| Read Size (b) | Enter the size buffer size to be used for for reading files. When a decoder is selected the agent produces
| ||||||||||
No of Thread(s) | Enter the number of worker threads that should be used for file collection. This field determines the number of files that agent can process concurrently. You should typically set the number of threads to match the number of workflow threads. If you want to ensure that the files are processed in timestamp order you should set No of Thread(s) to 1 and also select the check box Sort Files. | ||||||||||
| Sort Files | Select this check box to sort the files that are moved to the temporary directory for processing. The files are sorted according to timestamp in ascending order. Due to multithreading, the files may not be processed in this order. | ||||||||||
| Timeout Handling | |||||||||||
| Timeout (ms) | When the agent routes the first partial data set to the workflow, a timeout counter starts. The timeout counter is reset when the workflows acknowledge reception of the complete file. If the timeout counter is exceeded the collected file is either moved to a user-specified directory or After Collection strategy is applied. Enter the timeout value in milliseconds. | ||||||||||
| Move Files on Timeout | Select this check box to move timed out files to an automatically created subdirectory that you specify in the Directory setting.
| ||||||||||
| Path | When Move Files on Timeout is selected, enter the target directory for files that are subject to timeout handling. | ||||||||||
| After Collection | |||||||||||
| Move/Rename | If you select this radio button, the source files will be moved to the directory that you specify in the Destination field, after the collection. If you use the Prefix or Suffix fields, the file will be renamed as well. Enter the path of the directory on the local file system of the EC into which the source files will be moved after collection. The path can be absolute or relative to the
| ||||||||||
| Prefix/Suffix | Enter the prefix and/or suffix that will be appended to the beginning respectively the end of the name of the source files, after the collection. These fields are only enabled if you have selected Move or Rename.
| ||||||||||
| Search/Replace |
Replace: Enter the replacement text. Search and Replace operate on your entries in a way that is similar to the Unix The identified filenames are modified and forwarded to subsequent agents in the workflow. This functionality enables you to perform advanced filename modifications, as well:
| ||||||||||
| Remove | If this radio button is selected, the source files will be removed from the source directory after collection. | ||||||||||
Decoder Tab
The Decoder tab contains settings related to decoding of the collected data.
Disk_Deprecated collection agent - Decoder tab
| Setting | Description |
|---|---|
Decoder |
...
Select from a list of available decoders |
...
created in the Ultra Format Editor |
...
The decoders are named according to the following syntax:<decoder> (<module>)
The option MZ Format Tagged UDRs indicate that the expected UDRs are stored in one of the built-in formats.
Select this option to make the Tagged UDR Type list accessible for configuration. If this option is selected, the Tagged UDR Type list will be enabled.
...
, as well as the default built-in decoders:
Different settings are available depending on the Decoder you select. | |
| Full Decode | This option is only available when you have selected a decoder created in the Ultra Format Editor. If you have selected this option, the UDR will be fully decoded before |
...
being sent out from the decoder agent. This option may have a negative impact on performance, since not all fields may |
...
be accessed in the workflow, making decoding of all fields in the UDR unnecessary. |
...
If it is important that all decoding errors are detected, you must select this option. If you have not selected this option, the amount of work needed for decoding is minimized |
...
using |
...
"lazy" |
...
decoding |
...
of field content. This means that the actual decoding work |
...
might not be done until later in the workflow, when the field values are accessed for the first time. |
...
In this case, corrupt data (that is, data for which decoding fails) |
...
might not be detected during the decoding stage |
...
, but can cause a workflow to abort at a later processing stage. | |
| MZ Tagged Specific Settings | |
Tagged UDR Type | Click the Add button to select from a list of available internal UDR formats stored in the Ultra and Code servers to reprocess UDRs of an internal format and send them out. If the compressed format is used, the decoder automatically detects this. |
| JSON Specific Settings | |
UDR Type | Click Browse to select the UDR type you want the Decoder to send out. You can either select one of the predefined UDRs or the |
| Unmapped Fields | If you have selected the DynamicJsonUDR as UDR Type, you can select the option data in this field in order to include payload. If you have selected another UDR type that contains an any, or a map field, you can select to put any unmapped fields into the field you select in this list. All fields of any or map type in the selected UDR type will be available. If set to (None), any unmapped fields will be lost. |
| Schema Path | Enter the path to the JSON schema you want to use in this field. |
| CSV Specific Settings | |
| UDR Type | Select the UDR type you want the Decoder to send out. You can either select one of the predefined UDRs or the DynamicCsvUDR if the CSV format is not known. |
| Format | Select the CSV format you want to use; Unix, Mac, Windows, or Excel, or select to define your own customized format. If you select Custom, the following four settings will be enabled. |
| Delimiter | Enter the delimiter character(s) for the fields in the CSV. |
| Use Quote | Select this option if quotes are used in the CSV. |
| Quote | If Use Quote is selected, enter the type of quotes used in the CSV. |
| Line Break | Enter how line breaks are expressed in the CSV. |