tibemsd Options

The following table describes the EMS server command-line options that have differing behavior with FTL stores, or which are unsupported with FTL stores.

Option Description
Options with Differing Behavior for FTL Stores
-forceStart

When using FTL stores, this option will discard corrupted records in both EMS and FTL.

In the event of disk corruption in FTL, the recommended course action is to move or delete the contents of the FTL store-specific data directory. Upon restart of the FTL server, the contents of the directory will be synced from other members of the FTL server cluster.

If this is not possible because no other cluster members are running, the -forceStart option can be enabled as a last resort in order to force the FTL server to discard corrupted records and start up.

Warning: The -forceStart option can result in data loss. If it must be used, make sure to first back up the contents of your FTL store-specific data directory. For production environments, it is advisable to consult with TIBCO Support prior to usage.
Options Unsupported for FTL Stores
-config

When using FTL stores, the EMS server reads its configuration directly from the FTL server cluster. The tibemsjson2ftl tool must be used to upload the EMS server configuration to the FTL server cluster.

This option is ignored when specified in the FTL server YAML configuration.

-license

When using FTL stores, the license must be configured through the license.url FTL yaml parameter or TIBEMS_LICENSE environment variable.

This option may cause unexpected behavior if specified in the FTL server YAML configuration.

-secondary

When using FTL stores, the EMS server roles are implicit, which makes the -secondary option irrelevant.

This option is ignored when specified in the FTL server YAML configuration.

-ft_active

-ft_activation

When using FTL stores, the specifics of fault-tolerance are handled by the FTL server cluster.

These options are ignored when specified in the FTL server YAML configuration.