Table of Contents
Working with the DHDOS
The server software plays a central role for the interconnection of DHD devices and DHDOM entities. It controls the DHD devices, receives data from these devices, sends this data to connected applications (DHDOM) on the same or several PCs and processes data of these clients.
Example 1 - DHDOS and DHDOM on the same PC
In the easiest case, the DHD Operation Server (DHDOS) and the client software DHD Operation Manager (DHDOM) are running on the same PC. This is particularly proper to control, an Series 52 Core device or to backup snapshots from a Core device.
Example 2 - networked server/client structure
This example shows a networked server/client structure. The software DHDOS is running on a server PC, which is connected to the office network and a number of client PCs (e.g., in several studios), each with a running entity of the DHD Operation Manager (DHDOM). Through a second ethernet interface the server PC is connected to the DHD devices.
Example 3 - server/client structure with redundant DHDOS
In this case the server/client structure of the previous example is enhanced by a second, redundant entity of the DHD Operation Server (DHDOS). This copy of the DHDOS runs redundant in slave mode on a second PC and observes the processes of the master DHDOS. It is not directly connected to the device. The slave remains in this state until the master fails. If this happens, the slave gets the control of the devices and handles the communication between the several client PCs.
