Key Capabilities
- SSH-based secure file transfer with public key and password authentication
- Advanced authentication including certificate-based client authentication
- Resume capability for interrupted uploads and downloads
- Advanced SSH encryption algorithms and server thumbprint validation
- Connection pooling and temporary file handling for reliable transfers
- Optional caching to ensure only new or updated files are downloaded
Overview
Each SFTP connector uploads to a specified folder and downloads from a set of folders on the remote SFTP server. Files that reach the SFTP connector in the Arc flow are uploaded to the upload target folder, and files found in the download target folder(s) are downloaded and entered into the Arc flow. The connector supports upload and download filters to only send and receive specified file names and/or file extensions.Connector Configuration
This section contains all of the configurable connector properties.Settings Tab
Host Configuration
Settings related to establishing the connection to the remote SFTP host.Client Authentication
Settings related to authenticating to the SFTP server.Server Authentication
Setting related to verifying the SFTP server’s identity.Upload
Setting related to uploading files to the SFTP server.Download
Settings related to downloading from the SFTP server.Caching
Settings related to caching and comparing files between multiple downloads.Arc automatically cleans up the resource cache. This process runs in the background during every receive cycle and removes stale cache entries for files that are no longer present on the remote server. This keeps the cache size manageable without requiring any manual action.
By default, files are retained for 30 days, but you can use the ResourceCacheRetentionDays setting in the Other Settings field on the Advanced tab to adjust it to fit your environment. For example, ResourceCacheRetentionDays=15 retains files for 15 days before removing them.
TEST.TXT and test.txt.Advanced Tab
Server Commands
Advanced Settings
Settings not included in the previous categories.Proxy Settings
These are a collection of settings that identify and authenticate to the proxy through which the connection should be routed. By default, this section uses the global settings on the Proxy Settings portion of the Security Settings page. Clear the checkbox to supply settings specific to your connector.
| Setting | Description |
|---|---|
| Proxy Type | The protocol used by a proxy-based firewall. |
| Proxy Host | The name or IP address of a proxy-based firewall. |
| Proxy Port | The TCP port for a proxy-based firewall. |
| Proxy User | The user name to use to authenticate with a proxy-based firewall. |
| Proxy Password | A password used to authenticate to a proxy-based firewall. |
| Authentication Scheme | Leave the default None or choose from one of the following authentication schemes: Basic, Digest, Proprietary, or NTLM. |
Message
Message settings determine how the connector searches for messages and manages them after processing.
Note: The settings below are deprecated and hidden by default. They appear only on connectors where they were previously enabled or configured to a non-default value. To retain copies of successfully processed files, right-click the connector in the flow, choose Show Success Path, and connect the success path to a File connector.
| Setting | Description |
|---|---|
| Save to Sent Folder (Deprecated) | Copies files processed by the connector to the Sent folder. Disabled by default. Files saved to the Sent folder are not covered by Encryption at Rest. |
| Sent Folder Scheme (Deprecated) | Groups files in the Sent folder by the selected time interval. Only relevant when Save to Sent Folder is enabled. |
Logging
Settings that govern the creation and storage of logs.
| Setting | Description |
|---|---|
| Log Level | The verbosity of logs generated by the connector. When you request support, set this to Debug. |
| Log Subfolder Scheme | Instructs the connector to group files in the Logs folder according to the selected interval. The Weekly option (which is the default) instructs the connector to create a new subfolder each week and store all logs for the week in that folder. Leaving this setting blank tells the connector to save all logs directly in the Logs folder. For connectors that process many transactions, using subfolders helps keep logs organized and improves performance. |
| Log Messages | Check this to have the log entry for a processed file include a copy of the file itself. If you disable this, you might not be able to download a copy of the file from the Transactions tab. |
Miscellaneous
Miscellaneous settings are for specific use cases.
| Setting | Description |
|---|---|
| Other Settings | Enables you to configure hidden connector settings in a semicolon-separated list (for example, setting1=value1;setting2=value2). Normal connector use cases and functionality should not require the use of these settings. |
Automation Tab
Automation Settings
Settings related to the automatic processing of files by the connector.Automation Status
Performance
Settings related to the allocation of resources to the connector.
| Setting | Description |
|---|---|
| Max Workers | The maximum number of worker threads consumed from the threadpool to process files on this connector. If set, this overrides the default setting on the Performance Settings portion of the Advanced Settings page. |
| Max Files | The maximum number of files sent by each thread assigned to the connector. If set, this overrides the default setting on the Performance Settings portion of the Advanced Settings page. |
Alerts Tab
SLAs Tab
Establishing a Connection
The following settings are required to connect to a remote SFTP server:- Remote Host
- Remote Port
- Authentication Mode
- User
- Password or Client Certificate/Certificate Password
- Server Thumbprint
Uploading Files
The SFTP connector uploads files from the Transactions tab. Files are automatically uploaded to the SFTP server if Upload Automation is enabled in the connector. Remote Path should be set to the folder on the remote SFTP server where files should be uploaded. You can use macros to dynamically create dated folders (such as year or month folders). The application changes directories to the specified folder after logging in to the server. If any files could not be uploaded, the connector attempts to send them again after Retry Interval minutes have elapsed. This process continues until the Max Attempts setting is reached, after which the connector raises an error and the file is no longer sent automatically.Downloading Files
Downloaded files are displayed in the Transactions tab of the connector, or passed along to the next connector in the flow. Files are automatically downloaded from the SFTP server if Download Automation is enabled in the connector, and can be manually downloaded by clicking the Receive button on the Transactions tab. Remote Path should be set to the folder on the remote SFTP server from which files should be downloaded. You can use macros to dynamically create dated folders (such as year or month folders). The application changes directories to the specified folder after logging in to the server. The File Mask property filters files so that only filenames matching the glob pattern are downloaded from the server. You can use the Delete files (after download) setting to delete the files on the remote server after successfully downloading them. On the Transactions tab, click the Receive button to test the settings and retrieve the matching files from the server.Subfolder Headers
If Recurse is checked on the Advanced tab, when receiving a file from the Remote Path in the SFTP connector:- The message for the file that is received contains a Subfolder header in its metadata.
- This header contains the subfolder, relative to the Remote Path in the SFTP connector, that the file was received from.
- This subfolder header is supported by other connectors that support a subfolder header in Send operations.
- The file is placed in the subfolder, relative to the Upload Path in the SFTP connector, that is specified in the subfolder header.
- The subfolder is created if permissions are available.