On Unix, FolderMonitor is installed automatically. On Windows, DocOrigin FolderMonitor is installed as a separate step from the main DocOrigin installation. It is installed using the Microsoft installer by clicking on the .../DO/Bin/FolderMonitorSetup.exe file provided as part of the install set.

Testing a new install

When FolderMonitor is installed it adds a default set of test forms (.xatw) and scripts in order to assist in understanding how the system works. This setup also allows you to confirm that all components are correctly installed.

The installation of FolderMonitor adds a Windows service called: DocOriginFolderMonitor.

IF YOU HAVE MADE NO (REPEAT NO) CHANGES IN THE FOLDERMONITOR CONFIGURATION FolderMonitor and the Windows service can be tested by doing the following:

• Start FolderMonitor Console from the desktop icon or the Start menu.
• Once the FolderMonitor Console window is displayed, simply click on the Start FolderMonitor button. The Windows service will be started and FolderMonitor will begin its scan of its queue folder(s). Several lines of text will appear in the Log Messages window as the service starts the FolderMonitor instance(s) and they do their initial processing.
• Click on the Copy Test Files to Scan Folders button. This will copy two XML data files into the first queue folder.
  This button has been dropped as of 3.0.004.05 since it was nearly certain to fail once you made adjustments to your configuration. If you really have made no changes to the initial FolderMonitor installation and wish to do a "proof of life" test, you can run the FolderMonitor-CopyDataFiles.bat command file that is supplied under .../DO/Samples. It simply copies two shipped sample XML files to the standard jobs folder. Of course, you could copy in any test files you like, but they should correlate to the Job Name Discovery and Job Processing scripts that you have defined.
• You should now see several additional lines appear in the Log file messages box showing that Merge has been run and has processed those two data files.
• Check the .../User/Output/PDF folder and you should see two new PDF files that were created by Merge using the two data files copied to the queue folder.
• If you now check the .../User/FolderMonitor/ProcessedFiles folder you should see the two data files there, indicating that they have been processed by FolderMonitor.

The site-specific job name discovery script is to be placed, by you, in .../User/Overrides/JobNameDiscovery.wjs. That file is referenced in the main discovery script file .../DO/Bin/Default-JobNameDiscovery.wjs. You never edit files under the .../DO folder. Note that you can specify a different script to be used as your Job Name Discovery script. See Job Name Discovery.

Similarly, you should copy the .../DO/Bin/Default-JobProcessing.wjs script to your .../User/Overrides/Default-JobProcessing.wjs file, and edit it there according to any changes you wish to have in the default processing of a job. Again, options are available to use alternate Job Processing scripts. See Processing the Job.