We are working on multiple fronts to address many of the Job Processor issues that people are running into. For this post, I want to point out some command line features we added to Vault 2013. This feature won’t fix all problems, but it has many uses.
You can read about the command line options from the SDK documentation or the wiki. The idea behind these commands is to make JobProcessor behave more like a service. You can now programmatically start, pause, resume, and gracefully shutdown. Previously, start and kill were the only things you could do from a command line.
Here are a couple of uses I came up with for these new command line operations. Feel free to post your ideas too in the comments section.
Make use of idle computers
When the CAD engineers go home for the night, use the idle computers to run Job Processor. Create a Windows task that starts up Job Processor at 8 PM and shuts it down at 5 AM, for example. If every CAD station does that every night, it should clear out any backups on the job queue.
Run certain jobs at certain times
Maybe you would rather not process DWF files during the daytime. You can set things up so that DWF files only get processed at night. The first step is to copy JobProcessor.exe.config. Next edit the copy in an XML editor and comment out all the <jobHandler> elemets where the class attribute starts with “Autodesk.Vault.DWF.Create”. This config will will be the one you use when you don’t want to handle DWF files.
Set up a Windows task that runs at 5 AM. The task will shut down Job Processor, swap in the non-DWF config file, then re-start Job Processor. Because the DWF <JobHandler> tags are commented out, it will not process DWF files. Set up another task at 8 PM to shut down Job Processor, swap in the original config file, then re-start.
Here is an example BAT file for the 8 AM task.
cd C:\Program Files\Autodesk\Vault Professional 2013\Explorer
REM Send the stop command to Job Processor
REM Wait for Job Processor to exit
tasklist /FI "IMAGENAME eq JobProcessor.exe" 2>NUL | find /I /N "JobProcessor.exe">NUL
if "%ERRORLEVEL%"=="0" goto RunCheck
REM swap in the non-DWF config file
REM restart job processor
REM Job Processor should be running now and should be ignoring DWF jobs