Skip to main content
Skip table of contents

DigaTransfer: Running 2 or more DigaTransfer Broker at a station

DigaTransfer Broker can store the received tasks into a database. When choosing to use a DigaSystem database as target for this task list usually the invisible table DISPATCH_TASKS is used which is generated by Admin tool when creating the administrative tables.
If you are running more than one DigaTransfer Broker it is necessary to assign individual tables to each instance of DigaTransfer Broker.
Please contact DAVID support. They offer SQL scripts to generate additional administrative tables. 

JavaScript errors detected

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

If this problem persists, please contact our support.