In the event of file transfer being interrupted for any reason, openFT provides for secure restart. This means that network problems, for example, present no difficulty to openFT, since openFT automatically continues transfer as soon as it becomes possible again.
The storage of the request in the request queue and the so-called restart points for the basis for automatic restart. These are the security points with which the two partner systems are synchronized at regular intervals during file transfer. If transfer is interrupted, it is continued as soon as possible starting at the last security point. You can therefore rest assured that not one single bit is lost and nothing is added during file transfer.
The fixed timing between security points ensures that no unnecessary security points are set for fast lines, and that the intervals are not too long for slow lines.
Deactivation of automatic restart
It is sensible in some situations to deactivate the restart function for the openFT and FTAM protocol for asynchronous file transfer jobs. If, for example, an openFT Initiator instance is coupled to a load balancer which selects one of the many responders depending on the load, there is no guarantee that this load balancer at restart selects the same responder instance which processed the job at the beginning. The restart would fail and a job "corpse" remains in the original responder.
The partner-specific deactivation of the restart function has an impact on outbound requests. The restart function can also be deactivated via operation parameter settings, separately for outbound and inbound requests.