Triggering a file transfer

We can set certain trigger conditions on a file transfer that must be true before that transfer can take place. If the triggering conditions are not true, the file transfer does not take place and a log message is optionally submitted to record the fact the transfer did not happen. The file transfer request is then discarded. For example, we can set up a file transfer that takes place only if a named file on the system where the source agent is located is over a specified size, or if a particular named file exists on the system where the source agent is located. We can set up a triggered file transfer from either the IBM MQ Explorer or from the command line.


We can monitor a resource continually for a trigger condition to be satisfied. For further information about resource monitoring see: Monitor MFT resources.

There are three different triggering conditions that we can set. The conditions are as follows:

  • If a particular file exists on the same system as the source agent
  • If a particular file does not exist on the same system as the source agent
  • If a particular file is over a certain size on the system where the source agent is located (the size can be expressed in bytes, KB, MB, or GB). These units of measurement use the 210 convention, for example 1 KB equals 1024 bytes and 1 MB equals 1024 KB.

The triggering types in the preceding list can be combined in two ways:

  • For a single condition, we can specify more than one file on the system where the source agent is located. This triggers the transfer if any one of the specified files meets the condition (Boolean operator OR).
  • We can specify multiple conditions. This triggers the transfer only if all of the conditions are met (Boolean operator AND).

We can also combine a triggered transfer with a scheduled transfer. See Create a scheduled file transfer for more information. In this case the trigger conditions are evaluated at the time the schedule is due to start, or for a repeating schedule every time the schedule is due to start.

Triggered transfers are not supported on protocol bridge agents.

To create a triggered file transfer by using the command line, use the -tr parameter on the fteCreateTransfer command.

To create a scheduled file transfer by using the Create New Managed File Transfer wizard in IBM MQ Explorer, use the following steps:


Procedure

  1. In the Navigator view, click Managed File Transfer. Managed File Transfer Central is displayed in the Content view.
  2. All of our coordination queue managers are displayed in the Navigator view. Expand the name of the coordination queue manager that we have used for the scheduled transfer. To change which coordination queue manager we are connected to, right-click the name of the coordination queue manager we want to use in Navigator view and click Connect.
  3. Start the Create New Managed File Transfer wizard by using either of the following methods:
    1. Right-click the name of any of the following nodes in the Navigator view: the relevant coordination queue manager, Transfer Templates, Transfer Log, or Pending Transfers. Then click New Transfer to open the wizard.
    2. Click File > New > Other > Managed File Transfer Wizards > New Transfer Wizard

  4. Follow the instructions on the wizard panels. Ensure that you select the Enable triggered transfer check box on the Triggers tab and complete the fields on that tab to set up triggering. There is context-sensitive help provided for each panel. To access the context-sensitive help on Windows, press F1. On Linux, press Ctrl+F1 or Shift+F1.

Parent topic: Administer Managed File Transfer