FTL Server Configuration Parameters

Supply a map from server names to their locations.

  server_name: host:port

Include in this map only core servers. Omit any auxiliary servers.

When present, the FTL server stores its working data files in this path location. The directory at path must exist, as the FTL server does not create it automatically.

Servers within a local network can share a data directory, or they can use unique locations.

When absent, the default path is the current directory.

Include an ftl configuration map with a server parameter to specify the host and port for a specific auxiliary server.

For an example, see "Auxiliary Servers."

Force the FTL server to be reachable at only this address, regardless of core.servers settings.

Set the limit for the amount of spin time , in microseconds, for an FTL server receiving data from a connection. The default is 0. This is an ftl (not globals) setting.

Use caution with this parameter and adjust it only when necessary and with full understanding of its effect on CPU and thread performance. The default value should provide optimal performance in most cases.

When present, authentication is enabled, so that the realm service requires and verifies user name and password credentials from client processes, affiliates, browsers, and tibftladmin.

If the URL protocol is file://, the FTL server reads authentication data from a flat file at this location.

Otherwise, the FTL server contacts an external authentication service at this URL.

When absent, authentication is disabled, so that the FTL server neither requires nor verifies credentials.

Optional.

The FTL server identifies itself to an external authentication service using this user name credential.

Optional.

The FTL server identifies itself to an external authentication service using this password credential.

To hide the password from casual observers, see Password Security.

Optional.

When the authentication service URL uses the https:// protocol, use this parameter to specify the location of the authentication service's public certificate file (in PEM format). The FTL server uses the certificate to verify the identify of the external authentication service.

https://host1:port1|https://host2:port2|https://host3:port3

A satellite receives its realm definition and accepts realm updates from any primary realm service.

The realm service in a satellite does not accept client connection requests until it first receives a realm definition from a primary.

Supply a pipe-separated URL list of primary FTL servers.

The primaries initiate the connection to disaster recovery servers.

Supply a pipe-separated URL list of primary disaster recovery FTL servers.

(You must also configure the disaster recovery servers using the drfor parameter.)

FTL servers use this timeout, in seconds, for two purposes:

Connection Timeout

An FTL server waits for this timeout interval before repeating its connection request to an affiliated FTL server.

Heartbeat Timeout

An FTL server determines that an affiliate is unavailable when the affiliate's heartbeat signal is silent for this timeout interval.

Supply a positive number.

When absent, the default value is 3 seconds.

An FTL server sends its heartbeat signal at hb_interval, in seconds.

Supply a positive number.

When absent, the default value is 1 second.

An FTL server authenticates itself to affiliates with this username.

An FTL server authenticates itself to affiliates with this password.

To hide the password from casual observers, see Password Security.

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

When this parameter is absent, the default level is info.

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

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

When absent, the default behavior rejects all cross-origin requests.

When present, allow REST requests that originate from URLs in an array of strings. The realm service rejects cross-origin requests from any other origin.

The special value * allows all origins.

The password argument encrypts the TLS key file.

To hide the password from observers, see Password Security.

Secure FTL servers use this parameter to supply the file path to a local copy of the trust file.

When both are present, this parameter overrides tls.trust.everyone.

The FTL server trusts any other FTL server without verifying trust in the other service's certificate.

The FTL server reads a public TLS certificate from this file. It uses the certificate to authenticate itself to clients.

The certificate file must be in PEM format.

The FTL server reads an encrypted TLS private key from this file. It uses the key to authenticate itself to clients, and to encrypt TLS communication with clients.

The key file must be in PEM format.

The FTL server decrypts the private key using this password.

In the event that a flaw is discovered in the default cipher suite or protocols, TIBCO will issue a security announcement, and indicate new values for these settings.