Waarp is pleased to release a first version of Waarp Transfer, its new file transfer monitor.
Available now, Waarp Transfer uses the R66 protocol and largely uses the code of Waarp Gateway, with which it shares 90% of the code. This means a similar mode of administration for both applications, corrective support and faster functional evolution. This version is based on Waarp Gateway 0.4.4 (Version 0.2 is planned to be based on Gateway 0.7.0, and subsequent versions will follow Gateway developments with joint releases).
This first version of Waarp Transfer includes most of the features of Waarp R66. However, it is an application entirely written in Go which is based on a different command syntax from its big sister in Java.
In addition to the thin administration client inherited from Waarp Gateway, Waarp Transfer includes a thick client allowing you to carry out operations relating to file transfer as well as a filewatcher.
Linux and Windows platforms are supported now, and support will be expanded in the coming months, including the release of official Docker images.
Listing files
The waarp-transfer ls and waarp-transfer lls commands allow you to list respectively, for a given rule, the files available for retrieval on a remote R66 server or the files available for sending locally. It is possible to request additional information about these files via the -d or --detailed option (size, last modification date, permission, etc.) .
Example: with the command `waarp-transfer ls --partner server --login user --rule recv --file “*.xml”`, the client connects to the partner server with the user user and requests the file listing whose name ends with “.xml”, available via the recv rule.
For more information:
File listing command
Synchronous transfers
The waarp-transfer transfer run command allows file transfers to be carried out synchronously (the client carries out the transfer itself and does not delegate it to the waarp-transferd daemon). The direction of the transfer is specified by the -w or --way option (see: the waarp-transfer add command).
It is possible to execute multiple transfers with the same command by:
Specifying multiple files by repeating the -f or --file option.
Specifying multiple partners by repeating the -t or --to option.
Specifying multiple rules by repeating the -r or --rule option.
These options can be combined, so the command waarp-transfer transfer run -r send -t login1@server1 -t login2@server2 -f foo.txt -f titi.csv sends the foo.txt and titi.csv files to the servers server1 (by logging in with login1) and server2 (by logging in with server2).
To know more:
Transfer execution command
File Watcher
The waarp-transfer watcher command monitors a set of folders specified in a configuration file and sends all files arriving in said folders.
The configuration file specifies for each folder, the file selection pattern, the destination server, the identification login, the transfer rule, the information, etc.).
Detection of files to be transferred is based on OS write events; a file being written will only be transferred once its writing is complete. The file watcher is generally more efficient, faster and responsive, especially on large files, compared to the previous version, written in Java.
To know more:
File watcher command
Changes
Features
#6 Added file listing commands.
#5 Added synchronous transfer command
#4 Adding the file watcher command
#21 Added r66 and r66-tls local servers by default.
#9 Added the ability to enable and disable local servers. By default, r66-tls server is enabled and r66 server is disabled. It is now possible to deactivate a server, via the REST interface or via the command line client. Unlike activated servers, a deactivated server will not be automatically activated when launching Waarp Transfer. Please note that deactivating a server does not immediately stop it. The server will remain active until Waarp Transfer is stopped.