Your browser does not support HTML5 local storage or you have disabled it. Some functionality on this site, including saving your privacy settings and offering you special discounts, uses local storage and may not work with local storage disabled. We recommend allowing the use of local storage in your browser. In some browsers, it is the same setting used for disabling cookies.

SSH

Automated File Operations and Commands

Once the events have been created, Tectia MFT Events can be left running in the background without user presence. All newly created events are enabled by default, and they get executed according to their triggers and Tectia MFT Events logs detailed information on their progress.

Automating scheduled file transfers

Triggers that start event execution can be time-based, command-based or file-modification-based. The execution time can be defined as intervals, as a specific time, or Tectia MFT Events can poll a directory for changed files. The trigger can be defined to be used during a certain period, after which the execution will cease automatically. It is also possible to define events to be executed only once.

Automated Commands

Commands can be used as triggers, and commands can be defined as actions. They 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. The command can be set to be executed on the local node or at the remote end.

Synchronizing directories

Tectia MFT Events can be used to synchronize directories. It can poll a source directory for modifications, and transfer any new or updated files to one or several destination directories. The operator just needs to define the directories and the polling interval, and Tectia MFT Events will handle the secure file transfers automatically.

Chaining actions and events

Actions and events can be grouped and chained to build more complex transaction scenarios. Conditional actions can be defined to provide backup to each other and action blocks can be used to build dependencies between the actions (for example: if A, then B or else C).

An event can have success and failure conditions which can trigger new events in a chain based on the result of the first event. This way the existing events definitions can be reused.

Connection profiles for automatic connections

As the events run automatically without user presence, the connections require non-interactive authentication. The operator should connect to each target host once, and store the relevant user credentials per host as connection profiles, and after that Tectia MFT Events uses the predefined connection profiles for easy session setup.

Each connection profile contains all details needed to establish a connection to a host automatically. When creating the events, the connection profiles can be easily selected from a drop-down list.

===AUTO_SCHEMA_MARKUP===