Restarts process file transferTransfers files from one computer to another. A particular Automation Engine object type (FileTransfer object). scripts only partially but the corresponding taskAn executable object that is running. Tasks are also referred to as activities. completely.
Windows and UNIX agents are exempted. They set restartA restart refers to the repetition of an object's execution. This action differs from a new start in some parts. points in regular intervals. A repeated file transfer continues at the last restart point. The interval depends on the settings that the administrator has defined in the parameter "JOB_CHECKINTERVAL" of the variableIt stores or retrieves values dynamically at runtime. An individual Automation Engine object type. UC_HOSTCHAR_DEFAULT.
Restart possibilities depend on the particular agentA program that enables the de-centralized execution of processes (such as deployments) on target systems (computers or business solutions) or a service that provides connectivity to a target system (such as for databases or middleware). An agent is also an object type in the Automation Engine. [Formerly called "Executor."] See also: host's version (file transfer protocol old/new):
Old file transfer protocol: Partially qualified can be repeated as a whole if the parentThere are different ways of activating objects. The originator of an activation is referred to as the superordinate task (parent). See also: Child; Children FileTransfer objectAutomation Engine controlled activities and processes are structured in the form of objects. See also: Task is used for a restart. It is also possible to repeat individual childA subordinate task (such as a task that runs in a workflow). file transfers.
New file transfer protocol: All files are processed via an activityAn activity (or task) is an entity that can be planned, assigned to a user or a team and tracked with respect to their plan and state (started, cancelled, suspended, completed).. If the file transfer fails, it can be continued starting with the last restart position.
Do so by selecting the option From last restart position. Restart points are created in a defined interval while the files are being transferred. Use the key FT_RESTARTINFO_INTERVAL in the UC_HOSTCHAR_DEFAULT to determine the required time interval. If the file transfer aborts, the transfer can continue from the file position where the last restart point has been created. Restart information is stored locally on the agent computer in the form of StatusStore files. A consistency check is made to ensure that incomplete files have not been changed before the restart was initiated. All restart information is deleted after the file transfer has successfully been completed. More information is provided in the document that describes the FileTransfer Procedure.
In restarts, it is still possible to transfer all data from the beginning.
Restart options are only available for file transfers of the new protocol if the restart has been called using the statisticsThis is a list of a task's previous runs. and if the object has not been changed.
When all information is transferred again in a restart, the existing files on the target system will be overwritten even if the option "File exists - abort" is defined in the FileTransfer object. When you select the option "File exists - append", the information is appended to the target file even if the information has already been appended in the original run.
Background information: The option "Transfer all new" in the restart dialog has the effect that the system ignores the StatusStore file of a previous file transfer execution and rebuilds the number of hits. The target file is overwritten because in a restart, the agent cannot recognize whether a file that already exists on the target file has actually been transferred by the previous original run or not.
Automic Documentation - Tutorials - Automic Blog - Resources - Training & Services - Automic YouTube Channel - Download Center - Support |
Copyright © 2016 Automic Software GmbH |