Technical preview: Transfer files using SFTP

Available on Windows (win-x86-32, win-x86-64) and Unix (Linux-x86-64, Linux-ia64-64, Sun-x86-64, Sun-SPARC-64)

SSH File Transfer Protocol (SFTP) is a protocol for transferring files over an encrypted SSH channel, which you can use with Transfer CFT. Support includes the SFTP versions 3, 4, 5 and 6 for both client and server functionality.

The following sections describe how you can use the Transfer CFT SFTP feature:

Supported operations

The Transfer CFT server supports the following SFTP commands:

  • Upload (put) and download (get)
  • Get directory listings
  • Create, remove, change directory
  • Rename, remove file
  • Change file mode

Supported Transfer CFT features    

The Transfer CFT SFTP implementation supports these Transfer CFT features:

  • Text/binary file transfer
  • Group of files in heterogeneous mode (mput, mget)
  • Folder monitoring
  • Multi-node
  • Multiple CFTPROT objects of the SFTP type
  • SSH compression
  • Bandwidth control in client mode
  • Authentication with the user password
  • Authentication with an SSH key
  • FDISP, FACTION, WFNAME
  • MAXCNX

Use cases

You can use SFTP with Transfer CFT, other Axway products, and third-party products, to connect file transfer networks.

Use case 1: Connecting networks

Transfer CFT can integrate with non-PeSIT based file transfer networks, as a server as well as a client.

Use case 2: Application to application file transfers

Alternatively, you can implement Transfer CFT with SFTP in application to application flow scenarios. Transfer CFT can transfer files between applications using PeSIT or SFTP, as either a client or a server.

Configuration template

Transfer CFT provides a basic SFTP configuration template. Click here to view the template.

Restart a transfer

Transfers are activated by the client, so a restart only works from the client side.

  • Between two Transfer CFTs, interrupted transfers are restarted as on other protocols. There is only one entry in the catalog for the transfer. Use the file name to identify the transfer identifier during the restart.
  • When a send is restarted by the client, it checks that the file is still available on the server. This is possible only when the transfer is configured in Open Mode, because otherwise the server file name is provided by the server and the client does not know what it is.

Receive of a group of files in heterogeneous mode

You can receive a group of files in a single command. For that, start the NFNAME parameter of the RECV command with the prefix # (Windows ) or @ (Unix). This can be:

  • Some files in a directory matching a filter containing wildcard characters (* and ?) such as #path/file*.
  • All the files in a directory such as #path, not including the files in sub-directories.

Command examples on a Windows system

RECV PART='PARIS', IDF='BIN', nfname=#rest/F1/test*, FILE=ALL

RECV PART='PARIS', IDF='BIN', nfname=#rest/F1, FILE=ALL

With FILE=ALL, all files are transferred. With FILE=FIRST, the first file is transferred. If no file matches, the resulting DIAGI is 610.

Limitations

  • SFTP supports messages and replies (ACK or NACK), but only between Transfer CFTs.
  • SFTP implementation does not support the store-and-forward functionality.
  • Presently, you cannot use Central Governance to manage the SFTP feature for Transfer CFT.
  • You cannot use Copilot to create CFTSSH objects.
  • Windows - You cannot modify the files rights (chmod) from the SFTP client when using Transfer CFT Windows as the SFTP server.

Related Links