The implementation with individual file transfer shell scripts is quite often platform-dependent and
error-prone, this means most of the time there is no sufficient proof that a file transfer has definitely
been successful.
In most cases there is no error handling, e.g. no repeating of the file transfer in case of failure.
Implementing with individual shell scripts means that it is required for the configuration to be
organised individually. The change of a protocol, e.g. from FTP to SFTP requires a new
implementation each time.
Benefits
Using a platform independent implementation (Java) for all platforms with no additional requirement
for the installation.
Error recognition and error handling.
Support of protocols FTP, FTP/S, SFTP (public / private key).
Batch processing via command line and configuration file.
No information about received or sent files is centrally available.
No analysis is possible concerning the error occurrence of transfers that have been undertaken with shell scripts.
No compliant reporting is available, e.g. a daily or weekly report that shows frequency and time of the transferred files.
Benefits
A centrally available GUI is used in order to monitor and to analyse the file transfers.
The Web GUI allows searching the complete file transfer history.
Automatic generation and mailing of file transfer history reports, configurable KPI-Reports.
Individual reports can be created with a standard report generator by querying the
transfer history database.