Transport 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 SmartSockets transports, the value must be tibss.
SmartSockets Parameters

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

server_names The value is a comma-separated list specifying connections to one or more SmartSockets RTservers.

Each item in the list has the form protocol:hostname:port. You may omit any of the three parts. The default hostname is the local host computer. The default protocols and ports vary with hardware and operating system platforms; on Windows platforms, the default protocol is tcp and the default port is 5101.

A list of several servers specifies fault tolerance—tibemsd attempts to connect to them in the order listed.

When this parameter is absent, the default instructs the EMS server to attempt to connect to an RTserver on the local host computer (the same computer as the EMS server), using default protocols and ports.

username

password

tibemsd uses these two parameters to authenticate itself to the SmartSockets servers.
project SmartSockets uses projects to maintain orthogonal subject name-spaces.

When absent, the default project is rtworks.

delivery_mode This parameter determines the quality of service with which delivers messages to the SmartSockets server over this transport:

 best_effort | gmd_all | gmd_some | ordered

When absent, the default is best_effort.

lb_mode SmartSockets servers balance the message load by distributing messages among several clients. This parameter determines the load balancing regimen for messages that this transport exports to the SmartSockets server.

 none | round_robin | weighted | sorted

When absent, the default is none.

override_lb_mode enable instructs the RTserver to deliver all messages on this client connection—even if other clients participate in load balancing. For example, even though many order-processing clients might share the load of order messages, a message logging facility would require all order messages, rather than a subset.

disable informs the RTserver that this client (that is, the EMS server) participates in load balancing (for example, sharing the load with other EMS servers).

When absent, the default is enable.

gmd_file_delete SmartSockets clients keep data for guaranteed message delivery (GMD) in a store file.

disable instructs tibemsd to open the existing GMD store file.

enable instructs tibemsd to delete the GMD store file and create a new one when creating this transport.

When absent, the default is disable.

import_ss_headers This parameter governs the import of SmartSockets message headers to EMS properties.

The value can be none, type_num, or all. For complete details, see SmartSockets Message Properties.

When absent, the default value is none.

preserve_gmd This parameter determines the behavior of the EMS server when it has exported a GMD message to SmartSockets, and SmartSockets cannot deliver that message. When SmartSockets returns the undelivered message, EMS can either preserve it in the EMS undelivered message queue, or discard it.
  • always instructs EMS to preserve all undelivered GMD messages in the EMS undelivered message queue.
  • receivers instructs EMS to preserve only those undelivered GMD messages that SmartSockets could not deliver despite the existence of one or more GMD receivers. That is, if SmartSockets cannot deliver a message because no GMD receivers exist, then EMS does not preserve the undelivered message.
  • never instructs EMS to discard all undelivered SmartSockets GMD messages.

When absent, the default value is never.

This parameter applies only when the transport’s delivery_mode parameter is either gmd_all or gmd_some.

When the EMS server preserves a GMD message, it follows these rules to convert the returned SmartSockets message to an EMS message:

  • Follow all general rules for importing messages; see Message Translation.
  • Disregard the value of the import_ss_headers parameter, and instead import all SmartSockets headers (as if the value of import_ss_headers were all). For a list of headers, see SmartSockets Message Properties.
  • Set the value of JMS_TIBCO_SS_EXPIRATION to the current time—that is, the time at which the SmartSockets server returned the undelivered message to EMS. (Notice that the this header would otherwise remain unused, since GMD messages do not expire.)
EMS Parameters
topic_import_dm

queue_import_dm

EMS sending clients can set the JMSDeliveryMode header field for each message. However, SmartSockets 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.

Example

These examples from transports.conf illustrate the syntax of transport definitions. 

[SS01]
   type = tibss
   server_names = rtHost1
   username = emsServer6
   password = myPasswd
   project = sales_order_entry

[SS02]
   type = tibss
   server_names = tcp:rtHost2A:5555, ssl:rtHost2B:5571
   username = emsServer6
   password = myPasswd
   project = mfg_process_control
   override_lb_mode = enable
   delivery_mode = gmd_some