FTL Server Executable

Each FTL server requires a minimum of 2 GB of free disk space. In addition, each persistence service-using disk persistence or swap requires an additional minimum of 1 GB of free disk space.

Administrators use tibftlserver, the FTL server command-line executable, to start an FTL server process. Each time an FTL server is started, the FTL server process must be ran by the same user.

Parameter Arguments Description
-h

--help

  The FTL server prints a usage message summarizing its command-line parameters.
-c

--config

<path> The FTL server reads the configuration file at <path>.
-n

--name

<name> This parameter designates the name of the FTL server.

This name selects one of the core servers.

The FTL server monitoring GUI displays the name that you supply so you can identify individual FTL server processes.

To run an auxiliary server in a Docker container with non-default host and port values, specify the name argument with this form: 
<name>@<host>:<port>
--init-security <password_specifier> When present, the FTL server generates new TLS data, and then immediately exits.

The TLS data files include ftl-trust.pem (trust) and ftl-tport.p12 (keystore).

The FTL server writes the TLS data files to its data directory. If it cannot write to the data directory, the server writes these files to the current directory.

When this flag is present, the FTL server ignores its --name argument.

The FTL server uses the <password_specifier> argument to secure the keystore file. For details, see "Password Security."

If the FTL server detects existing TLS files, it does not generate them anew. However, the FTL server does not decrypt or inspect existing files.

--init-auth-only   When present, the FTL server generates new authentication data, and then immediately exits.

The security data files include ftl-trust.pem (trust) and ftl-tport.p12 (keystore).

The FTL server writes the data files to its data directory. If it cannot write to the data directory, the server writes these files to the current directory.

For details, see Authentication and Authorization .

If the FTL server detects existing authentication files, it does not generate them anew. However, the FTL server does not decrypt or inspect existing files.

--core.servers <URL_list> Optional.

This parameter is a convenience for use with Docker.

When starting an FTL server in a Docker image using a default empty configuration file, specify the cluster of core servers in this <URL_list>.

<URL_list> is a pipe-separated list of core servers. Each server specification has this form: 

<name>@<host>:<port>
-l --loglevel <level>  

When present, the FTL Server logs at this level of detail. Supply one of these strings:

• off
• severe
• warn
• info
• verbose
• debug

Note that the output from verbose and debug can result in a very large output, and this level of detail is generally not useful unless TIBCO staff specifically requests it.

When this option is absent, the default value is info.
-lc --license <license_location>

Optional.

The path to a license file or the URL to the TIBCO Activation Service instance. The license file path must be absolute.

The URL to the TIBCO Activation Service instance might optionally include a fingerprint. If a fingerprint is provided, the FTL server only connects to the TIBCO Activation Service instance if the fingerprint matches the public certificate of the TIBCO Activation Service instance.

Syntax for a license file: file://pathname. If the pathname contains spaces, the entire value must be enclosed in double quotes.

Syntax for the TIBCO Activation Service instance: https://url?[fp=activation service fingerprint]. For example, path to a license file: file:///opt/deployment/license.bin, TIBCO Activation Service instance URL: https://activation.service:7070, TIBCO Activation Service instance URL with fingerprint: https://activation.service:7070?fp=ed686f46f7c0537751fd99017ea6d3eb754eceeb74198c7aabed77f4ebe42e36

The TIBFTL_LICENSE environment variable can be used in place of this parameter. For more information about the FTL server license requirements and behavior, see license_url.

--skip.auto.init.primary.on.no.contact <integer>

Optional.

In the simplified DR model, when you are preparing for DR failback following an unplanned DR failover, you can pass this parameter on the command line when starting FTL servers at the original primary site. For more information about when to do this, see Simplified Disaster Recovery.

The value passed to this parameter is a timestamp, equal to the number of seconds since the epoch.

This parameter is not needed if disaster recovery (DR) is not configured. This parameter is not allowed in the "classic" DR model. See Selecting a Disaster Recovery Model.

This parameter temporarily suppresses the behavior of the auto.init.primary.on.no.contact parameter in the FTL server yaml configuration file (see FTL Server Configuration Parameters). This is one of the methods available to you for preventing "split-brain" following an unplanned DR failover.

When the servers at the original primary site contact the DR site, this parameter is ignored until its value changes again. You may leave this parameter on the command line, so long as its value does not change.