Bridge Service Configuration Parameters

This topic presents the FTL server configuration parameters that apply to the bridge service.

Example

The example configuration file has three sections: globals, services, and servers. Set bridge services configurations in the server section. 

# Sample FTLServer yaml configuration file that demonstrates starting a primary and backup bridge service
# Since we are are starting two bridge servers, one of them will end up being the backup.
# 
globals:
  core.servers:
    ftlserver1: localhost:8585
    ftlserver2: localhost:8685
    ftlserver3: localhost:8785
servers:
  ftlserver1:
    - ftlserver.properties:
        logfile: bridge1.log
    - realm:
        # Update this field accordingly (for windows use backward slashes)
        data: TIBCO_HOME/samples/yaml/ftlserver1/bridge
    - bridge:
        names:
          - brdg
        ft.weight: 100

  ftlserver2:
    - ftlserver.properties:
        logfile: bridge2.log
    - realm:
        # Update this field accordingly (for windows use backward slashes)
        data: TIBCO_HOME/samples/yaml/ftlserver2/bridge
    - bridge:
        names:
        - brdg
        ft.weight: 200
  ftlserver3:
    - ftlserver.properties:
        logfile: bridge3.log
    - realm:
        # Update this field accordingly (for windows use backward slashes)
        data: TIBCO_HOME/samples/yaml/ftlserver3/bridge
    - bridge:
        names:
          - brdg
        ft.weight: 300
Bridge Service Configuration Parameters
Parameter Arguments Description
names <bridge_name> Optional.

A list of bridge names.

A bridge service implements one or more bridge objects.

When absent, the bridge service implements only the bridge object named default.

label <label> Optional.

The bridge status page of the FTL server GUI presents client information about bridge objects. This parameter can help you can distinguish among bridge objects in fault-tolerant bridge services.

Specify the label parameter at the same level as the names parameter.

When present, the client label of a bridge object is a string that concatenates this < label> argument with the bridge name.

When absent, a bridge object uses only the bridge name argument as its client label.

ft.weight <weight>

Optional.

If a group of fault-tolerant bridges is configured, the bridge service with the highest weight becomes active. This applies to all logical bridges managed by the bridge service.

The value must be a positive integer greater than 0.

See Arranging Fault-Tolerant Bridge Services.