File Monitors can be started and stopped via three methods: as a service, manually, or with a Business Process task.
File Monitors are not enabled by default (except when run as a service). They must be started once promoted to a server. This topic describes the different methods available.To Run as a Service
To Start and Stop Manually
These steps takes place in the Admin Console | Resource Monitors view.
- Under the Resource Monitor Types section, select File Monitor. All deployed File Monitors appear in the Resource Monitors section. Any monitor that has already been started has a green indicator, while red indicators show that a monitor is not started.
- From the Resource Monitor section, select the File Monitor you wish to start and click Start ().
It's important to remember that File Monitors are deployed along with dependent objects. Always make sure the related objects exist and are complete before deploying a File Monitor. A good practice is to make your File Monitor one of the last objects you create.
To start with a Business Process
File Monitors can be started and stopped when called with the ControlFileMonitor Business Process task. Another task, GetFileMonitorState can also be helpful to check whether your File Monitors are started or stopped. A typical use case may be to use the "Get" task to check for state, and then the "Control" task to enable the Monitor if found to be disabled.