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.

Parameter Description
type Required. For all EMS transports for TIBCO FTL, the value must be tibftl.
TIBCO FTL Parameters

The syntax and semantics of these parameters are identical to the corresponding parameters in TIBCO FTL clients. For full details, see the TIBCO FTL documentation set.

endpoint Optional. Specify a TIBCO FTL endpoint name. To define multiple transports that use the same TIBCO FTL endpoint, include the same endpoint name in each transport definition.

If absent, the endpoint name defaults to the name of the EMS transport.

import_subscriber_name Optional. The name of the FTL subscriber this EMS transport for FTL creates when it receives messages. If not set, then an EMS transport that receives FTL messages creates a default FTL durable instead. See Destinations for details on the FTL durable name.
import_match_string Optional. Creates a content matcher object to filter messages. Specify content matchers using the syntax: 
{"fieldname1":value1,...,"fieldnameN":valueN}

The following rules must be observed:

  • Field name and value declarations must conform to the match string syntax described in the TIBCO FTL documentation.
  • The import_match_string must be specified on a single line. No manual line breaks may be inserted. Spaces are not allowed.

For example: 

import_match_string = {"Item":"Book","Title":"Outliers","Stocked":true}
export_format Optional. Specifies a format name to be used when a message is created.

If not provided, the EMS server passes NULL to the TIBCO FTL message create call, resulting in a dynamically formatted message.

export_constant Optional. Defines fields that are always set to a constant value. Each line adds additional constants. For example: 
export_constant = constant1,value1
export_constant = constant2,value2
export_constant = constant3,value3

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