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 and the optional import_subscriber_name transport property is not set, tibemsd creates a single default FTL durable for the transport with the following name: <server name>:<transport name>. For example, if tibemsd.conf has server = EMS-SERVER and transports.conf has a [FTL1] transport defined, the corresponding durable name comes as EMS-SERVER:FTL1. However, if import_subscriber_name is set, then tibemsd creates a FTL subscriber by that name instead of the aforementioned FTL durable.
  Note: An FTL administrator can monitor the status of this default FTL durable and, if relevant, the FTL administrator can decide to configure it as static and alter its behavior.
• 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.