Desktop ObjectServer architecture

You can use a desktop ObjectServer architecture to improve the performance of an ObjectServer that frequently experiences heavy loads.

The desktop ObjectServer architecture:

  • Reduces the workload of the central ObjectServer by shifting the load to specialized desktop ObjectServers
  • Improves desktop responsiveness; that is, the time between a desktop operator's action and its reflection in the desktop GUI
  • Reduces the likelihood of the desktop GUI freezing
  • Improves the end-to-end latency times in heavily-loaded, standard ObjectServer configurations
  • Maintains high data integrity and consistency by simultaneously updating the master ObjectServer

The desktop ObjectServer architecture consists of a master ObjectServer and one or more desktop ObjectServers that share the duties normally performed by a single ObjectServer. Dual server desktops (DSDs) connect to a single, master ObjectServer when writing data, but read and display alert data from desktop ObjectServers. The main functionality of the DSD is the same as a standard desktop; for operators, the DSD behaves identically to a standard desktop.

The desktop ObjectServer architecture is shown in the following figure.

Figure 1. Example dual server desktop architecture
This figure shows a master ObjectServer that uses two unidirectional gateways to forward event data to two desktop ObjectServers. IDUC connections are used to send the event data to two dual server desktops, which in turn use SQL connections to write data to the master ObjectServer.

The DSD connects simultaneously to the desktop ObjectServer and the master ObjectServer. Any operator actions (for example, tools or journal actions) that are performed in the DSD are sent directly to the master ObjectServer through a one-way SQL connection.

Alerts in the master ObjectServer are sent to the DSD through the desktop ObjectServer. This is achieved by using a unidirectional ObjectServer Gateway from the master ObjectServer to the desktop ObjectServer, and an IDUC connection from the desktop ObjectServer to the DSD.

If dual-write mode is enabled, updates are also sent to the desktop ObjectServer through another one-way SQL connection, as shown in the following figure.

Figure 2. Example dual server desktop architecture with dual-write mode enabled
This figure shows the dual server desktop architecture with dual-write mode enabled.