Configuring MFT monitor tasks to start commands and scripts

Resource monitors are not limited to performing file transfers as their associated task. You can also configure the monitor to call other commands from the monitoring agent, including executable programs, Ant scripts or JCL jobs. To call commands, edit the monitor task definition XML to include one or more command elements with corresponding command call parameters, such as arguments and properties.

About this task

The file path to the executable program, Ant script, or JCL job that you want the monitoring agent to call must be included in the commandPath of the monitoring agent. For information about the command path property, see commandPath MFT property.

You can create the task definition XML document in one of the following ways:

Create the task definition XML document manually according to the FileTransfer.xsd schema.
Use a generated XML document as the basis for your task definition.

Whether you want a transfer task or a command task, the task definition must start with a <request> root element. The child element of <request> must be either <managedTransfer> or <managedCall>. You would typically choose <managedCall> when there is a single command or script to run, and <managedTransfer> if you want the task to include a file transfer and optionally up to four command calls.

Procedure

To create the task definition XML document manually according to the FileTransfer.xsd schema, see Creating a task definition XML manually according to the schema.
To create a task definition by modifying a generated document, edit the XML document generated by the fteCreateTransfer -gt parameter. For more information, see Creating a task definition document by modifying a generated document.