Directory Monitor

Directory Monitor is a windows service which tracks folder changes, such as file creation, removal, modification or renaming.

• Multiple locations can be monitored
• Network shares can be monitored using the UNC path
• Automatically performs user-defined tasks and actions.

User Interface

Event Log Example

Installing Directory Monitor

Directory Monitor service is automatically installed during setup but not configured.

It can be also installed using the command line

To install the Directory Monitor as a service run the following command:

aetldirectorymonitor.exe /INSTALL

for Advanced ETL Processor

vimpdirectorymonitor.exe /INSTALL

for Visual Importer ETL

If the Monitor is already installed it must be uninstalled first

To uninstall the Monitor as a Windows service you must run the Monitor with the /UNINSTALL switch as follows

aetldirectorymonitor.exe /UNINSTALL

for Advanced ETL Processor

vimpdirectorymonitor.exe /UNINSTALL

for Visual Importer ETL

The commands above must be executed as administrator (elevated).

Configuring Directory Monitor service

It is recommended to run Directory Monitor using the same user used to design packages/transformations/sql scripts.

• Open windows services
• Find Directory Monitor in the list
• Double click on it
• Dialog box will appear
• Set startup time to automatic
• Change username
• Start the service

Checking Monitor Status

• Make sure that the monitor service is up and running
• Make sure that the monitor service is using the appropriate username and user
• Make sure that the user has access to directories monitored
• Make sure that the monitor is enabled on the maintenance tab
• Make sure that the directory is enabled on the Event monitors tab
• Make sure that the execution agent is configured properly

Monitor is enabled on Maintenance tab

Monitor is enabled on Event Monitors tab

Action was submitted by Directory Monitor

Directory Monitor Variables

<Monitor ID>
<Directory Monitor File Name>

Things to Consider

• Directory Monitor is only available with Enterprise Version.
• Do not use mapped drives, use UNC path instead.
• “Wait until the file is ready” only works for file creation.
• What if you have 1000+ files copied into the directory? The directory monitor will fire a trigger for every single file
• Use “Log Events” option to investigate issues

The solution to this problem is to use a trigger file. Eg you copy 1000+ files into the directory and copy the last file called trigger.txt. Set monitor mask to trigger.txt. Monitor fires only once. The package moves files into the different directories (with a timestamp) and processes the files one by one.

Video Tutorial