...
Part of the configuration can be made in the Filename Template service tab described in Filename Template Tab in 3.1.6 Workflow Template.
Connection Tab
The SFTP forwarding agent configuration - Connection tab
...
| Setting | Description |
|---|---|
Enable Backlog | Enables backlog functionality. |
Directory | Base directory in which the agent will create sub directories to handle backlogged files. Absolute or relative path names can be used. |
Type | If you select the Files option, the Size field below will determine the maximum number of files allowed in the backlog folder. If you select the Bytes option, the Sizefield below will determine the total sum (size) of the files that resides in the backlog folder. If a limit is exceeded the workflow will abort. |
Size | Enter the maximum number of files or bytes that the backlog folder can contain. |
Processing Order | Determines the order by which the backlogged data will be processed once connection is reestablished. Select between First In First Out (FIFO) or Last In First Out (LIFO). |
Duplicate File Handling | Specifies the behavior if a file with the same file name as the one being transferred is detected. The options are Abort or Overwrite and the action is taken both when a file is transferred to the target directory or to the backlog. |
Security Tab
The SFTP forwarding agent configuration - Security tab
See the description of the Security tab in 9.73.2.1 SFTP Collection Agent Configuration
| Note | ||
|---|---|---|
| ||
Due to an upgrade of the Maverick library for 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 for 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/ |
| Scroll ignore | ||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||