...
The configuration described in this tutorial can be downloaded and then directly opened in the XML Editor using the following link:
- coming ....local_2_local_file_complete.xml
Checking files for completeness
A number of methods for checking whether file transfer has been completed are presented in this document:
- MD5 Integrity hash checksums such as MD5, which are generated before file transfer starts and can be used to check files after transfer.
- Atomic file transfer, which is used to hide files being transferred from target directory monitors until the file transfer has been completed.
- A prefix and/or suffix is added to the name of the file for the duration of the transfer.
This prefix/suffix is chosen so that the file being transferred will not be matched by any target host file monitor. - Once transfer has been completed, JADE removes the prefix/suffix and the file becomes visible to a file monitor.
- A prefix and/or suffix is added to the name of the file for the duration of the transfer.
- Regularly checking the file size until it reaches a steady state. Here it is assumed that the transfer has been completed when two checks in series return the same size.
...
- Repeating the file transfer and comparing the sizes of the file transfers. When both transfers have the same size then it is assumed that the transfer is complete.
See the CheckSteadyState parameter CheckSize element documentation for more information. - Checking file size after transfer with the CheckSize parameter element.
If Use of the transactional parameter is generally recommended if more than one file is to be transferred then the use of the transaction parameter is generally recommended (TBD - LINK).
File Completeness -
...
Integrity Hash Checksums
Example a) - Creating an MD5 checksum file
...