Bridge Service Configuration Parameters

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

Example

This example configuration file illustrates two ways to use the bridge section. First, it sets parameters for the bridge services in all servers. Second, it specifies a bridge service on each of three servers, without overriding any of the parameters from the global bridge section. 

globals:

    core.servers: # The set of core servers and their locations.
        ftl1: host1:8585
        ftl2: host2:8585
        ftl3: host3:8585

services:
    bridge:
        names:
          - bridge-1
          - bridge-2
        logfile: b-log
# ...

servers:

    ftl1:
        - realm: {}
        - bridge: {}

    ftl2:
        - realm: {}
        - bridge: {}

    ftl3:
        - realm: {}
        - bridge: {}
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 and not inherited, 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.

Tracing and Logging

Parameter Arguments Description
loglevel level Optional. Bridge services can inherit or override this value.

When present, the bridge service outputs log messages to stderr.

You may specify any of the standard log level strings (see “Tuning the Log Level” in TIBCO FTL Development). You can set a general log level, or custom log levels for different elements.

logfile logfile_prefix Optional. Bridge services can inherit or override this value.

When present, the bridge service logs to a rolling set of log files instead of the console. The logfile_prefix argument may denote a path. All of the directories in the path must already exist.

For more information about rotating log files, see “Log Output Targets” in TIBCO FTL Development.

When absent, the bridge service sends log output to the console, ignoring the parameters max.log.size and max.logs.

max.log.size size Optional. Bridge services can inherit or override this value.

Limits the maximum size, in bytes, of log files. The value must be greater than 100 kilobytes (102400 bytes).

max-logs logs Optional. Bridge services can inherit or override this value.

Limits the maximum number of rolling log files.