Monitoring MFT resources

You can monitor Managed File Transfer resources; for example, a queue or a directory. When a condition on this resource is satisfied, the resource monitor starts a task, such as a file transfer. You can create a resource monitor by using the fteCreateMonitor command or the Monitors view in the Managed File Transfer plug-in for IBM® MQ Explorer.

About this task

Managed File Transfer resource monitoring uses the following terminology:
Resource monitor
A resource monitor is process that polls a resource (such as a directory or queue) at a predefined regular interval to see if the resource contents have changed. If they have, the contents are compared with the set of conditions for this monitor. If there is a match, the task for this monitor is started.
Resource
The system resource that the resource monitor examines at every poll interval to be compared with the trigger conditions. Queues, directories, or nested directory structures can be the monitored resource.
Condition and Trigger condition
A condition is an expression that is evaluated (typically against the content of the monitored resource). If the expression evaluates to true, the condition contributes to the overall trigger condition.
The trigger condition is the overall condition, which is satisfied when all conditions are satisfied. When the trigger condition is satisfied the task can proceed.
Task
A task is the operation that is started when the trigger condition or set of conditions is satisfied. Supported tasks are file transfer and command call.
Trigger file
A trigger file is a file that is placed in a monitored directory to indicate that a task (typically a transfer) can begin. For example, it might indicate that all the files to be processed have arrived in a known location and can be transferred or otherwise acted upon. The name of the trigger file can be used to specify the files to be transferred by using variable substitution. For more information, see Customizing MFT resource monitor tasks with variable substitution.
The trigger file is also known as ready file or go file. However, in this documentation it is usually referred to as the trigger file.

Resource monitoring is not supported on protocol bridge agents or Connect:Direct® bridge agents.