Problem:
File order source starts the order when the file is created, not when the file is ready.
In some file transfer scenarios has the receiver of a file no knowledge about the time when the sender creates the file. In case of a (very) large file it can be the situation that the receiver tries to read the file but the sender has not finished to write it. If the receiver get the file at the moment the sender is still writing, as a result he will get a corrupted, incomplete file.
Solution:
#The sender creates a file name abc.txt~. When transmission is complete, the sender renames the file to abc.txt. You regular expression is something like ^.*\.txt$
#The sender creates a file named abc.txt. When it is ready, a second file with 0 byte will be created. The name of the second file is abc.txt.trigger You regular expression is something like ^.*\.txt.trigger$ With this approach you have the disadvantage, that on scheduler_file_path the name of the trigger file is found, not the name of the file that should be executed
- The first node in the job chain checks the file size. When it is changing a setback will be performed.
- Don't use file order source but the file exist job. You can find an example here www.sos-berlin.com/download