Directory Monitor
MFT Server can monitor local directories, Windows and Linux/Unix shares, and some Trading Partner directories for files added, deleted, changed, or aged. Watching a directory for changes lets you configure an automatic response when a change occurs. The automatic response is handled using a Trigger that listens for Directory Monitor events. A Trigger consists of one or more Actions, where an Action describes what to do as a result of the Directory Monitor event. See Triggers.
Is not necessary to create Directory Monitors for directories that are managed using an MFT Server service such as SFTP, FTPS, HTTP/S, etc. Directory changes made using services are captured more effectively by using Trigger events such as
File Upload, File Rename, File Delete, etc. This means you do not need to create a Directory Monitor. You only need to create a Trigger that listens for the appropriate file-related event
The following example offers a high-level description of how using a Directory Monitor and Trigger can address a specific use case.
On a nightly basis, the IT Department moves a file to a directory on the MFT Server. When this happens, you would like MFT Server to upload the file to a Trading Partner
.To implement this use case, do the following:
Create a Directory Monitor with the
Monitor file add option selected. The directory to watch is the directory where the IT Department places the file. When a file is added to the monitored directory, the Directory Monitor raises the
Directory Monitor File Added event.To automatically respond to this event, create a Trigger to listen for the
Directory Monitor File Added event type.When the Trigger event occurs, the Trigger executes one or more Trigger Actions. Trigger Actions specify the type of work to be done (e.g. upload a file or copy a file). In this example, you can use the
Trading Partner File Upload Action. Note: You need to create the Trading Partner with the connection information first.