Arranging Fault-Tolerant Bridge Services

You can configure two or more bridge services for fault-tolerant operation. Although this feature ensures automatic and quick recovery, failover might leave some messages unforwarded.

Weights can be specified in the FTL bridge service to coordinate its fault-tolerant operations to set a precedence order among all the bridge server instances. If a group of fault-tolerant bridges is configured, the bridge service with the highest weight becomes active. For example, if ft.weight is set on server 1 at 100, server 2 at 200, and server 3 at 300, server 3 will become active. This applies to all logical bridges managed by the bridge service. To see how to set this up, see the sample configuration file in Bridge Service Configuration Parameters.

Before you begin

Fault-tolerant bridge services rely on the group facility to coordinate fault tolerance.

    Procedure
  1. Configure bridge objects in the realm definition (see Transport Bridge Configuration).
  2. Configure two or more bridge services in separate FTL servers. Specify the bridges in the common section, or specify identical configuration parameters for each FTL server that provides the bridge service (see Bridge Service Configuration Parameters).
Result

The group facility automatically ensures that only one of the fault-tolerant bridge services is active at a time. The bridge service with the highest weight becomes active. This applies to all logical bridges managed by the bridge service. See Bridge Service Configuration Parameters to assign weight.