SwiftView Directory Monitor (hot folders)
Installation and Default SwiftView Directory Monitor Configuration:
To begin an evaluation of SwiftView Directory Monitor, please contact our Sales team at (971) 223-2661 or email SwiftView Sales to start your evaluation today.
The SwiftView Directory Monitor evaluation installer adds seven monitored directories under C:\SV_DirMon:
The directories that begin with "convert" and "testlicense" use SwiftConvert instead of SwiftPublish, and will not be discussed here.
For more information see the SwiftConvert Quick-Start Guide.
A simple user interface to change these directories or add your own can be accessed from Start...All Programs...SwiftView...SwiftView Directory Monitor.
It looks like this:
The following notes are helpful as you create your own monitored directories.
A SwiftView Directrory monitored directory consists of:
Command Contains the complete command line of the selected Action.
Input Folder The full path of the input directory to monitor.
Output Folder The full path of the output directory for the finished file.
Input Filer Enter one or more filter patterns. Separate patterns with semi-colons. Example: *.prn; *.tif...
Output Suffix To change the output file suffix, enter it here. Example: .tif to only process TIF files.
Watch Subfolders To monitor sub-folders of the defined Input Folder.
Regular Expression To use regular expressions in the Input Filter field, check box.
Working Folder The full path of the directory where the file is temporarily stored while being processed.
Save Folder The full path of an optional directory, where the input file is moved after process completion. If this is not set, the input file is deleted.
Overview of SwiftView Directory Monitor Operation:
Once SwiftView Directory Monitor is installed, you can copy or move any file to c:\SV_DirMon\importtopcl and collect the converted PCL file in c:\SV_DirMon\convertout.
When a file is placed into the importtopcl directory, SwiftView Directory Monitor waits until the file is fully written, then moves it to the importtopclwork directory and begins to perform the conversion.
Once a file is converted, SwiftView Direcoty Monitor creates an output file in the convertout directory with the same name as the original input file, but with a .pcl or .tif suffix. SwiftView Directory Monitor then deletes the input file.
The importtotiff directory is the same as importtopcl, except the output file is a TIFF. Using the importtotiff directory is fully licensed by purchasing SwiftPublish Server, but requires installing the SwiftConvert software.
SwiftView Directory Monitor can be configured to monitor additional directories if desired.
Simply select a directory similar to the one you want to add, modify the
settings, and click "New."
You can drop multiple files into monitored directories, and SwiftView Directory Monitor will properly queue them.
By default, Directory Monitor runs as many simultaneous conversion processes as the
number of processors on your server. You can change the number of simltaneous processes from the Directory Monitor configuration gui.
Note: when you rename a directory, the original directory is not deleted;
you can remove it manually.
In some cases you may need a multi-step process. This is easily done
by setting the output directory of the first monitored directory to be the
second monitored directory. In the example below SwiftConvert is used to convert a file to HPGL and then to PDF.
Advanced Use - Monitoring multiple directories:
command="c:\program files\swiftview\sview.exe" -c"set printautorotate disable|ldoc ""%in""|rotate 1|set printres original|draw|save RHPGL_US all ""%outdir\%inbase.hpg"" onefile"
command="c:\Program Files\Swiftview\sview.exe" -v1 -c"set quotechar ^|set service on|ldoc ^%in^|set allpensblack|save PDF all ^%outdir\%inbase.pdf^ onefile""
Since the output directory in step one and the input directory of step two
are the same, the process will look seamless to the end user. They
drop a file into 'importtohpgl' and then pick up the converted PDF from
the 'pdfout' directory.
When you install SwiftView Directory Monitor, you are asked to enter the username and password
for an account under which SwiftView Directory Monitor runs. This is important to insure
that you will see any dialogs that a printing application might display, or
to see error messages from SwiftView Directory Monitor.
Note that the SwiftView Directory Monitor service
is titled “SwiftView Directory Monitor” and runs as a service called svdirmon.exe. After installation, you can change
the user account under which SwiftView Directory Monitor and it's applications run from the Control Panel...Administrative Tools...Services menu.
When integrating DirMon into your process, there are a few details you should keep in mind.
All errors during directory monitor operation are logged in the Windows Event Viewer. Open Control Panel...Adminstrative Tools...Event Viewer...Application. Errors are displayed in console error dialogs in an
evaluation install, but this should be disabled for production by unchecking the "Display Errors" option in the DirMon configuration screen.
Error display by printing applications depends on DirMon running under the Local System user, see below.
Users and Permissions
DirMon is an NT service named "SwiftView Tools".
It runs under a Log On user account you select at installation, which you can subsequently change from the Control Panel...Adminstrative Tools...Services...SwiftView Tools...right-click...Properties screen.
The Log On user should always be a member of the Adminstrators group.
When initially testing DirMon operation, login as Local System is recommended.
If you find problems accessing resources such as network filesystems, try changing to a real user with network access.
You should check that any conversion application run under SwiftPublish can be started by that user without displaying any dialogs.
Drag a file onto a printer icon to check.
If customizing your own monitored directories you must make sure the SwiftView Tools service user has write access to the monitored directories.
This issue can come up if you are monitoring a directory on a network file server, whether that directory is
in a drive location mapped for that user (e.g. "f:\"),
or accessed using the full UNC path ("\\hostname\\directory").
Each monitored directory set has an input, working, and output directory, but it is possible to share some of these locations among the sets.
In the default configuration, DirMon has separate input and working directories for each type of conversion, however always outputs to the same directory.
You can use the same working and output directory for multiple sets.
Depending on your setup, you may want to separate some of the directories and share others.
If you were developing an archiving system, for example, this may be useful. If the users that are creating the initial file have restricted access to directories, it could be necessary to have multiple input directories, each accessible by a user.
Once the files are in the users input directory, the directory monitor could use the same working and output directories since it would have different access restrictions then the user.
The result would be users placing files in individual directories, but all files converted and outputted to the same location.
For more technical details on installing and configuring SwiftPublish or Directory Monitor please contact our Technical Support Team. They can be reached between 6am-6pm PST Monday through Friday at 800-720-0196 x2 or email at Technical Support