You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 5 Next »

Introduction

Directory monitoring is used to automatically start jobs when a change occurs within a specified folder. 

A directory monitoring event is triggered when a change occurs in a directory. This change can be either:

  • addition, modification or removal of a file or files

In contrast to File Watching, a directory monitoring event is triggered when a change occurs - the number of files in the directory being monitored that cause the event is not significant. Therefore a job that handles directory monitoring events would have to handle the files associated with that event.

Configuring a Standalone Directory Monitoring Job 

The standard method of implementing Directory Monitoring is to start a Standalone Job every time a file is either added to or deleted from a monitored directory. In addition, a filter can be specified to restrict the monitoring to specific file names.

The following screen shot shows how JOE - JobScheduler Object Editor is used to configure the monitoring of a directory ./monitor_dir . Additionally, only files with the extension txt will be acted on.

In the element tree in the left hand pane in JOE you will see the Run Options function for each job. Click on the New Dir button in the Start When Directory Changed area of the right hand pane to configure the directory that is to be monitored. Save this configuration by clicking the Apply Dir button after you have entered the monitor_dir and \.txt$ values in the Watch Directory and File Regex fields. Repeat this procedure to add further directories or patterns as required.

Standalone Jobs that are started by Directory Monitoring can also be started manually as required. Directory Monitoring can also be combined with scheduled Run Time configurations.

Directory Monitoring cannot be implemented for Order Jobs.

Resources

Feature in detail

How To ... Instructions

Frequently Asked Questions

Examples in detail

There is no content with the specified labels

Further References

 

 

  • No labels