Copyright © TIBCO Software Inc. All Rights Reserved
Copyright © TIBCO Software Inc. All Rights Reserved


Chapter 14 Working with TIBCO FTL : Overview

Overview
TIBCO Enterprise Message Service (release 8.2 and later) can exchange messages with TIBCO FTL (4.1 and later).
Scope
EMS can import messages from TIBCO FTL to an EMS queue (but queues cannot export).
Figure 17 EMS Transports for TIBCO FTL
 
Message Translation
EMS and TIBCO FTL use different formats for messages and their data. When tibemsd imports or exports a messages, it translates the message and its data to the appropriate format; for details, see Message Translation.
Configuration
In classic EMS configuration, the tibemsd uses definitions and parameters in three configuration files to guide the exchange of messages with TIBCO FTL. In JSON-configured servers, all configuration options are in the same file.
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 is disabled. To use EMS transports for TIBCO FTL, you must explicitly set this parameter to enabled.
ftl_url specifies the URL at which the EMS server should connect to the realm server.
module_path specifies the location of the TIBCO FTL shared library files.
Transports
Transport definitions (in the configuration file transports.conf) specify the communication protocol between EMS and TIBCO FTL; for details, see Configuring EMS Transports for TIBCO FTL.
Destinations
Destination definitions (in the configuration files topics.conf and queues.conf) can set the import and export properties to specify one or more EMS transport for TIBCO FTL:
import instructs tibemsd to import messages that arrive on those transports from TIBCO FTL, and deliver them to the EMS destination. When a destination is configured to import a given tibftl transport, the EMS server creates a single FTL subscriber for the transport.
export instructs tibemsd to take messages that arrive on the EMS destination, and export them to TIBCO FTL using those EMS transports for TIBCO FTL. When a destination is configured to export a given tibftl transport, the EMS server creates a single FTL publisher for the transport.
For details, see Topics, and Queues.

Copyright © TIBCO Software Inc. All Rights Reserved
Copyright © TIBCO Software Inc. All Rights Reserved