Transport Bridge Command Line Reference
Administrators use the transport bridge command line executable, tibbridge, to start a bridge process.
Each bridge process can implement one or more bridge objects (as defined in the realm). These bridge objects are independent: even though one process implements them all, messages do not cross from one bridge to another.
If the bridge objects change, or the transport definitions that they use change, you must explicitly restart the affected bridge process.
The bridges status table displays bridge processes as internal services. You cannot disable nor purge them using the GUI.
| Parameter | Arguments | Description |
|---|---|---|
| --realmserver
-rs |
URL | Required.
URL of the realm server. The bridge process contacts the realm server at this location to receive its bridge objects. Supply the location of the primary realm server or a satellite server (see Connect Port). |
| --secondary-realmserver
-s |
URL | Optional.
URL of the backup realm server. If the regular realm server is unavailable, the bridge process contacts the backup realm server at this location to receive its bridge objects. Supply the location of the backup realm server (see Connect Port). |
| --name
-n |
bridge_name | Optional (zero or more).
Bridge name. A bridge process implements one or more bridge objects. You may supply the name of a bridge object that this process implements. To implement several bridge objects in one process, supply each bridge name as a separate command line argument. Introduce each bridge object with the --name parameter. When absent, the process implements only the bridge named default. |
| --trace
-t |
level | Optional.
When present, the bridge process outputs trace messages to stderr. You may specify any of the standard log level strings (see "Log Levels" in TIBCO FTL Development). When omitted, the process does not output trace messages. |
| --tls.trust.file | path | Optional. (Required for TLS communication with a secure realm server.)
When present, the bridge process reads a trust file from path, and uses that trust data in communications with the secure realm server. See Running a Secure Realm Server. |
| --tls.trust.everyone | Optional.
The bridge process trusts any realm server without verifying trust in the server's certificate. |
|
|
--password-file
-pf |
path | Optional. (Required for authentication.)
When present, the bridge process reads a user name and password from the file at path, and authenticates itself to the realm server using those credentials. For details, see Password File. |
| --client-label
-c |
label | Optional.
When present, the bridge process uses this string as its client label. You can use this string to distinguish among fault-tolerant bridge processes in the realm server GUI. When absent, the bridge process uses the name argument as its client label. |
| --help
-h |
Print command line usage. |
Password File
If the realm server enables authentication and authorization, then you must configure credentials for the bridge process.
The bridge process authenticates itself to the realm server using credentials that it reads from an ASCII password file (see --password-file).
The password file consists of two lines. The first line contains the user name. The second line contains the password string.
The user name must be in the authorization group ftl. For details, see Realm Server Authorization Groups.
To hide the password from casual observers, you may first obfuscate the password using tibrealmadmin --mangle.