The automated file transfers and other data operations are configured as events in Tectia MFT Events.
An event consists of one or several actions that are triggered at a given time or under defined conditions.
The main concepts used in managing the events are explained below:
Actions define what the event does. An action can be one of the following options or combinations of them:
File transfer: one or several specified files transferred to one or several destinations; the number of retries can be configured
Transfer of modified files or directories
Removal of specified or modified files
Synchronizing a destination directory with a source directory. Tectia MFT Events can be used to poll for modifications in a file or a directory, and to transfer any new or updated files to one or to several locations. The polling intervals are configurable.
Commands, that can perform a wide variety of actions for files, and can be used as handles to external tools. For example, pre- and post-processing of files can be defined using local or remote commands. Commands can be defined to be executed on the local node or at the remote end.
Sending email noticications to defined users. Tectia MFT Events can be configured to send email notifications to one or several recipients when defined conditions are met, for example when a file transfer task fails. Tectia MFT Events includes a built-in SMTP client for this purpose.
The actions can be conditional (if A, then B or else C) or they can be grouped into action blocks with dependencies between the actions. An event can also have success and failure conditions which can trigger new events in a chain based on the result of the previous event.
These grouping and chaining options make it possible to build complex operations, but since all parts of the events are clearly visible in the Management Console their management is clear and easy.
Triggers define when the action will be started. The following types of triggers can be defined:
Time-based trigger defines a specific time or an interval for running the event.
Command-based trigger defines a command script to be run at specified intervals.
File modification-based trigger defines a polling interval for checking if modifications have occurred in the specified files or directories. When any files are created, modified or removed in the monitored location, it will trigger the event action.
Directory synchronization trigger defines a polling interval for monitoring two directories and keeping their contents in sync.
Events can be chained, so that secondary actions are performed when an event ends with a certain result. The conditions are On Success and On Failure. There can be several actions defined under each success and failure condition, and all the actions specified will be run when the event ends with the set result.
The On Success and On Failure conditions can have one or several actions to trigger new events or definitions of audit messages (configurable texts to be logged), command scripts, or email notification about the event results