Enabling
An EMS server is part of exactly one FTL realm, so all EMS transports for TIBCO FTL use the same TIBCO FTL realm. Thus, some parameters are shared for every EMS transport instance. These parameters are found in
tibemsd.conf
.
To enable EMS transports for TIBCO FTL, you must set these parameters in the configuration file
tibemsd.conf
:
tibftl_transports
globally enables or disables message exchange with TIBCO FTL. The default value isdisabled
. To use EMS transports for TIBCO FTL, you must explicitly set this parameter toenabled
.ftl_url
specifies the URL at which the EMS server is connected to the FTL server. For a TLS connection, this URL starts withhttps://
rather thanhttp://
.ftl_trustfile
specifies the trust file that is used to validate the FTL server on a TLS connection.module_path
specifies the location of the TIBCO FTL shared library files. If the EMS server is configured to use FTL stores, the value of this parameter is ignored and the FTL shared library files corresponding to the hosting FTL server are used instead.
If connecting to a TIBCO FTL deployment that is configured for OAuth 2.0 authentication, the following parameters will also need to be set in tibemsd.conf
:
-
ftl_oauth2_server_url
specifies the URL of the OAuth 2.0 authorization server from which access tokens will be obtained for authenticating with TIBCO FTL. -
ftl_oauth2_client_id
specifies the OAuth 2.0 client ID to use when authenticating with the OAuth 2.0 authorization server to obtain access tokens. -
ftl_oauth2_client_secret
specifies the OAuth 2.0 client secret to use when authenticating with the OAuth 2.0 authorization server to obtain access tokens.
Additional optional parameters can be used to further configure how the EMS server and FTL server interact. See TIBCO FTL Transport Parameters.