Redundancy

Given a minimal configuration of a single Director and single Broker, Engines, and Drivers log in to the Director, but failure of the Director (such as in the case of hardware or network failure) means a Driver or Engine not logged in, is no longer able to establish a connection.

To prevent this, redundancy can be built into the GridServer architecture. One method is to run a second Manager with a Secondary Director, and configure Engines and Drivers with the address of both Directors. If the Primary Director fails, Engines and Drivers contact the Secondary Director, which contains identical Engine configurations and route Engines and Drivers to Brokers in the same manner as the Primary Director. The figure above shows an implementation with two Managers.

In addition to redundant Directors, a Broker can have a backup on another Manager. A Broker can be designated a Failover Broker on a Manager during installation or in the Manager Configuration page. A Failover Broker acts as a backup Broker for times when other Brokers are offline. Under normal operation, they are idle.

For more information about redundancy, see the TIBCO GridServer® Administration.