# transports.conf

This file defines transports for importing messages from or exporting messages to external message services, such as TIBCO FTL, TIBCO Rendezvous, and TIBCO SmartSockets.

The format of the file is:

    [transport_name] # mandatory -- square brackets included
       type = tibftl | tibrv | tibrvcm | tibss  # mandatory
       [topic_import_dm = TIBEMS_PERSISTENT |
                          TIBEMS_NON_PERSISTENT |
                          TIBEMS_RELIABLE]
       [queue_import_dm = TIBEMS_PERSISTENT |
                          TIBEMS_NON_PERSISTENT |
                          TIBEMS_RELIABLE]
       [export_headers = true | false]
       [export_properties = true | false]
       transport-specific-parameters

Parameter Name | Description
--- | ---
[transport_name] | The name of the transport. Note that the square brackets [ ] DO NOT indicate that the transport_name is an option; they must be included around the name.
`type` | Transport type. `tibftl` identifies TIBCO FTL transport `tibrv` identifies TIBCO Rendezvous transport `tibrvcm` identifies TIBCO Rendezvous Certified Messaging transport `tibss` identifies TIBCO SmartSockets transport Each transport includes additional transport-specific-parameters.
`topic_import_dm` `queue_import_dm` | EMS sending clients can set the `JMSDeliveryMode` header field for each message. However, Rendezvous clients cannot set this header. Instead, these two parameters determine the delivery modes for all topic messages and queue messages that `tibemsd` imports on this transport. `TIBEMS_PERSISTENT | TIBEMS_NON_PERSISTENT | TIBEMS_RELIABLE` When absent, the default is `TIBEMS_NON_PERSISTENT`.
`export_headers` | When `true`, `tibemsd` includes JMS header fields in exported messages. When `false`, `tibemsd` suppresses JMS header fields in exported messages. When absent, the default value is `true`.
`export_properties` | When `true`, `tibemsd` includes JMS properties in exported messages. When `false`, `tibemsd` suppresses JMS properties in exported messages. When absent, the default value is `true`.
`transport-specific-parameters` | See Transport-specific Parameters.

Note: If you have multiple TIBCO Rendezvous transports configured in your `transports.conf` file, and if the EMS server fails to create a transport based on the last entry, the server will continue to traverse through the entries and attempt to create further transports.

Copyright © Cloud Software Group, Inc. All rights reserved.