Open topic with navigation

# FTL Server Executable

Each FTL server requires a minimum of 2GB of free disk space. In addition, each persistence service using disk persistence or swap requires an additional minimum of 1GB of free disk space. For details on these features, see Persistence Architecture.

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 executed by the same user. Each time an FTL server is started, the FTL server process must be executed 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 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`.

Did you find this helpful?

Yes No
Great!
Thanks for taking the time to give us some feedback.
Sorry about that

Why wasn't this helpful? (check all that apply)

Could not find what I was looking for
Instructions confusing or unclear
Instructions did not work

Want to tell us more?

Please select at least one option or provide details about the issue!!

Error occurred while submitting feedback.

Error2 occurred while submitting feedback.

TIBCO FTL® - Enterprise Edition

Copyright © 2009-2024. Cloud Software Group, Inc. All Rights Reserved.