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


Chapter 14 Working with TIBCO FTL : Configuring EMS Transports for TIBCO FTL

Configuring EMS Transports for TIBCO FTL
EMS transports mediate the flow of messages between TIBCO Enterprise Message Service and TIBCO FTL.
In TIBCO FTL, transport refers to the underlying mechanism that moves message data between FTL publishers and subscribers.
The EMS server joins a TIBCO FTL realm as any other TIBCO FTL client would. EMS transport definitions (in the file transports.conf) configure the behavior of these connections.
All messages received from the transports for TIBCO FTL that are configured in the transports.conf file are processed in a single TIBCO FTL event queue.
After being dispatched from the TIBCO FTL event queue, all TIBCO FTL messages that are imported through an EMS transport are processed by the EMS server. The EMS server creates JMS message copies of the incoming TIBCO FTL messages and begins processing them as EMS messages. EMS transports for TIBCO FTL determine how the messages are converted to EMS messages.
If the EMS server cannot keep up with the rate of incoming TIBCO FTL messages, by default, the FTL library begins discarding incoming messages.
Queue Limit Policies
In order to limit the number of pending messages in TIBCO FTL queues, EMS server properties allow you to set a queue limit policy, as you would for TIBCO FTL client applications. When the queue limit for the EMS transport is reached, the FTL library discards a set number of messages if the event queue discard policy dictates so. Review the FTL discard policy and related parameters for more information.
Requirements
In order to successfully deploy the EMS transport for TIBCO FTL, your TIBCO FTL deployment must meet the following requirements:
In TIBCO FTL, specify a discard policy of new when the EMS server’s subscriber name is specified.
EMS Transport for FTL Definitions
transports.conf contains zero or more transport definitions. Each definition begins with the name of a transport, surrounded by square brackets. Subsequent lines set the parameters of the transport.
 
{"fieldname1":value1,...,"fieldnameN":valueN}
The import_match_string must be specified on a single line. No manual line breaks may be inserted. Spaces are not allowed.
Example
These examples from transports.conf illustrate the syntax of EMS transport for FTL definitions.
[FTL1]
type = tibftl
endpoint = EP1
import_subscriber_name = sub1
  import_match_string = {"f1":"foo","f2":true}
export_format = format-1
export_constant = constant1,value1
export_constant = constant2,value2
export_constant = constant3,value3
[FTL2]
type = tibftl
 

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