Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

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 containing the available strategies. For further information about the nature of the collection strategy, see Appendix 4 - Collection Strategies.

File Information Settings

Directory

Absolute pathname of the source directory on the remote host, where the source files reside. The pathname might also be given relative to the home directory of the Username 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

Example

To match all filenames beginning with  TTFILES , type:  TTFILES.* .

Compression

Compression type of the source files. Determines whether the agent will decompress the files before passing them on in the workflow or not.

  • No Compression - the agent will not decompress the files.

  • Gzip - the agent decompresses the files using gzip.

Before Collection Settings

Move to Temporary Directory

If enabled, the source files will be moved to the automatically created subdirectory DR_TMP_DIR in the source directory, prior to collection. This option supports safe collection of a source file reusing the same name.

Append Suffix to Filename

Enter the suffix that you want added to the file name prior to collecting it.

Warning

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>.

After Collection Settings

Move to

If enabled, the source files will be moved from the source directory (or from the directory DR_TMP_DIR, if using Move to Temporary Directory) after collection, to the directory specified in the Destination field. If Prefix or Suffix are set, the file will be renamed as well.

Note!

If a file with the same filename already exist in the target directory, this file will be overwritten and the workflow will not abort.

Destination

Absolute 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.

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.

Prefix and Suffix

Prefix and/or suffix that will be appended to the beginning and/or the end, respectively, of the source files after the collection. These fields are only available if Move to or Rename is enabled.

Search  and  Replace

To apply Search and Replace, select either Move to or Rename.

  • Search: Enter the part of the filename that you want to replace.

  • Replace: Enter the replacement text.

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
    titleNote!

    A regular expression that fails to match the original file name will abort the workflow.

    Enter Replace with characters and metacharacters 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 brackets. 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 selected.

Rename

If enabled, the source files will be renamed after the collection, remaining (or moved back from the directory DR_TMP_DIR, if using Move to Temporary Directory) in the source directory from which they were collected.

Note!

You must avoid creating new file names still matching the criteria for what files to be collected by the agent, or else the files will be collected over and over again.

Remove

If enabled, the source files will be removed from the source directory (or from the directory DR_TMP_DIR, if using Move to Temporary Directory), after the collection.

Ignore

If enabled, the source files will remain in the source directory after the collection. This option is not available if Move to Temporary Directory is enabled.

UDR Type Settings

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 SQL Loader Agent for further information

...

Note

Note!

Due to an upgrade of the Maverick library for Image Removed MediationZone version 8.1.5.0, the default handling of the advanced security has changed. Users should take note of the behaviour change for the Advanced Security Option for the SFTP agents. The Advanced Security Option will be disabled by default. Users will have to enable it on their own accord from the Security Tab in the SFTP agents configuration.

With Advanced Security Option disabled, Maverick will manage the connection between the SFTP agent and the server. Maverick will attempt to connect with the STRONG security level. Failing to do so, it will auto downgrade the security level to WEAK and attempt to connect, this behaviour will allow our agents to work well with backwards compatibility for servers with older instances of the Maverick library.  Furthermore, having STRONG security level will result in a performance degradation.

However, when a user manually enables the Advanced Security Option from the security tab, Maverick will instead assign the WEAK security level, which will not be as strict or resource intensive as the STRONG security level.

For more information about security levels, you can refer to this page: https://www.jadaptive.com/managed-security-in-our-java-ssh-apis/

...