Client-side Features

Client-side protocols

The client-side component is used to push or pull files to or from a file transfer server. It is designed for automated transfers (not interactive transfers) that are transferred according to pre-configured events or scheduling, etc.

It can connect to a 3rd party file transfer server as well as our own file transfer server solution, SFTPPlus.

It supports all main open standard file transfer protocols including:

  • FTP
  • Explicit FTPS / FTPES (over TLS)
  • Implicit FTPS / FTPIS (over SSL)
  • SFTP (over SSH version 2)
  • WebDAV (over HTTPS)

The client-side protocols are continuously tested to assure compliance with RFCs and de facto implementations.

An overview of the supported client-side protocols are in the Users Guide Protocols section.

Below is a non-exhaustive list of servers used for testing and validation:

  • SFTPPlus
  • Filezilla
  • OpenSSH SFTP / SCP Server
  • ProFTPD
  • PureFTPD

Managed file transfer

The client-side component of SFTPPlus monitors either local or remote folders and triggers actions or transfers as soon as files are found in the monitored folders.

Actions are fully automated. While actions are being executed, no manual intervention is required as the client functions are executed within a process taking place in the background.

It can be configured in great detail to control:

  • Actions based on either local or remote events (e.g. scans for either local or remote file availability at a configured interval)
  • Scheduled transfers at certain times or time window
  • Options for retries on failures
  • Actions before starting a transfer
  • Actions after a failed or successful transfer
  • Alerts can be raised for events and/or failures

It is designed to replace or augment custom batches / shell scripts which are called from a scheduler or as cron jobs. It can be configured to do automatic pre and post-processing to implement the following tasks before or after transferring a file:

  • Virus checked
  • MD5 checksum checking
  • Renamed and/or moved
  • Call another arbitrary program
  • PGP/GPG encryption / decryption

All actions are audited and the audit trail is persisted in the following formats:

  • Plain text file
  • Windows Event logs
  • Streamed to standard output