Skip to main content
Skip table of contents

Installing a Job Processor


  • Microsoft .Net 4.5.2 or higher
  • Running DPE Server (can be installed on another server)
  • Check DPE Firewall Settings
  • The according DPE licenses (obtainable at DAVID Systems) to run the Workflow System and its modules
  • A time synchronizing mechanism (like NTP) for all machines used with DigaSystem for aligning the computer clocks with a central reference time for proper fetching of table updates.

  • Check Windows Server power options and set it to “High performance” to get best processing performance

Job Processor Overview

Jobs and job processors add scalability and redundancy to workflow-based solutions. 

The following Job Processors are available:

  • DPE Audio Processor
  • DPE Loudness Processor
  • DPE Video Processor
  • DPE Utility Processor

Job Processor Redundancy

For each Job Processor a main setup and a backup setup is available.

By using them you can install a Job Processor twice on a machine. Doing this enables you to continue job processing even when one of the processors is currently updated or maintained. Of course, you can achieve redundancy by also installing Job Processors on more than one machine.

Job Processor Scalability

Job Processors enable scalability on different levels:

  • Jobs can be executed concurrently by a single job processor. The allowed maximum concurrency for a job type is specified by its quota configuration, also see Configuring Job Processors.
  • Any Job Processors can be installed twice on a machine (main and backup).
  • Job Processors can be installed on many machines, building a processor farm.

Job Processor Setup

Besides the specific modules that are contained in a Job Processor, their setups are identical. In the following we use AudioProcessorSetup.exe as an example.

All our Job Processors are based on the DAVID SAF (Station Automation Framework), see also SAF Server And Admin 

After installation: If your Job Processor needs to access network shares then check if you have to authenticate share usage in the SAF Server startup script, also see Using SAF Server Startup Scripts and Running a SAF Server as Windows Service.

  1. Execute AudioProcessorSetupexe and click Next on the Welcome screen.

  2. Select the modules you want to install. These modules will only work with a valid license. To choose the Installation Folder open the according tab.

  3. Enter the DPE Service Root Address (see also DPE Server) to set the connection between the Job Processor and DPE Services: "//hostname:Port/DPEWebApplication” The default is set to the local machine (if not defined port 80 is used). If your DPE Server is configured to use HTTPS prefix the address with https://
  4. Enter the DigaSystem credentials to be used by the Job Processor. Click Install to start the installation process.

  5. The final window confirms the successful installation and offers to optionally open the SAF Administration tool and/or the SAF directory in an Explorer Window. 

  6. If you Finish the installation with the option “Start SAF Administrator” it will take about 1 minute for SAF Administrator to start. Meanwhile this message will be displayed:

    If the respective Computer.PAR file is missing, backend creates automatically a new one.

  7. The Job Processor will be started as desktop application. In a productive environment, we recommend to run the Job Processor as Windows Service and not as a desktop application, see Running SAF Server as Windows Service

Link to Start Job Processor

The setup creates a link in the installation folder which you have to use to start the Job Processor (after shutting the Job processor down). The name of the link is based on the name of the Job Processor:

You can also configure a Job Processor to run as Windows Service and therefore start automatically when Windows starts, see Running a SAF Server as Windows Service.

As an additional step, AudioProcessors also require LAME (lame_enc.dll) file in same directory as AudioProcessor for creating MP3 files.

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.