Server Configuration Upload/Download
When configured to use FTL stores, the EMS server will first connect to the FTL server cluster and fetch the configuration information before beginning its start-up sequence. The JSON configuration must be available in the FTL server cluster prior to starting the EMS server. If no configuration is available in the cluster, the EMS server will start-up with a default configuration.
The tibemsjson2ftl tool can be used to upload JSON configuration files to a specified FTL server cluster. It can also download JSON configuration files from a specified cluster.
Running the tibemsjson2ftl Tool
When the EMS server doesn’t find an EMS server configuration in the FTL server cluster, its subsequent behavior is dependent on whether the -config_wait parameter has been set in the FTL server cluster configuration. If present, the EMS server will halt its start-up process until the configuration becomes available. This provides the user with a chance to upload their own EMS server configuration to the cluster. If the parameter is not present, the server will simply start with a default configuration.
The tibemsjson2ftl tool can be used to upload JSON-based EMS configuration files to a specified FTL server cluster. It can also download JSON configuration files from a specified cluster.
The tibemsjson2ftl tool is invoked from the command-line. The tool is dependent on the FTL C client libraries, so the LD_LIBRARY_PATH environment variable must be set before running it.
export LD_LIBRARY_PATH=<FTL_HOME>/lib:$LD_LIBRARY_PATH tibemsjson2ftl options
tibemsjson2ftl Options
The following table shows the options that are used with the tibemsjson2ftl tool.
| Option | Description |
|---|---|
-url url
|
The pipe-separated list of URLs of the FTL server cluster to connect to. The URLs must be in one of these forms:
|
-json pathname |
The absolute path to the JSON configuration file to be uploaded to the FTL server cluster. When the
|
-download
|
When specified, tibemsjson2ftl will download the JSON configuration from the FTL server cluster and write it to the file passed to
-json.
If this parameter is not specified, the tool will default to uploading the JSON configuration to the FTL server cluster. |
-trustfile path
|
Path to the trust file created in the Initializing FTL Server Cluster Security section. Required when connecting to a secure FTL server cluster. |
-user user
|
User name to use when connecting to an FTL server cluster that has authentication enabled. If the cluster’s authentication data was created based on the steps in Initializing FTL Server Cluster Security, the value passed to this option should be admin. |
-password password
|
Password to use when connecting to an FTL server cluster that has authentication enabled. This should be the same password written to the users.txt file in Initializing FTL Server Cluster Security. To hide the password from casual observers, see the Password Security section of the TIBCO FTL Administration guide. |
-oauth2_access_token token
|
The OAuth 2.0 access token to use when connecting to an FTL server cluster configured with OAuth 2.0 authentication. This option is not required when connecting to an FTL server cluster that uses a different authentication method. |
Examples
Example 1
Uploading configuration to an FTL server cluster:
tibemsjson2ftl -url http://hostname:8080 -json tibemsd.json
Example 2
Downloading configuration from an FTL server cluster:
tibemsjson2ftl -url http://hostname:8080 -json tibemsd.json -download
Example 3
Uploading configuration to a secure FTL server cluster:
tibemsjson2ftl -url https://hostname:8080 -json tibemsd.json -trustfile ftl-trust.pem -user admin -password password