![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |
tibemsd connects to SmartSockets RTservers in the same way as any other SmartSockets client. Transport definitions (in the file transports.conf) configure the behavior of these connections. You must properly configure these transports.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.
Table 77 SmartSockets: Transport Parameters 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. tibemsd uses these two parameters to authenticate itself to the SmartSockets servers. When absent, the default project is rtworks. When absent, the default is best_effort. 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. 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.
• 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.This parameter applies only when the transport’s delivery_mode parameter is either gmd_all or gmd_some.
• 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 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.When absent, the default is TIBEMS_NON_PERSISTENT. These examples from transports.conf illustrate the syntax of transport definitions.Destination Name—Syntax and SemanticsEMS destination names consist of tokens separated by the dot (.) character. SmartSockets subjects consists of tokens preceded by the slash (/) character (like UNIX directory pathnames).For example, the EMS name foo.bar.baz corresponds to the SmartSockets name /foo/bar/baz. (Remember that SmartSockets names must begin with a leading slash, but EMS names need not begin with a leading dot. A leading dot indicates an empty element preceding it.)The slash and dot characters have complementary roles in EMS and SmartSockets. In EMS slash is an ordinary character, while dot is a separator. In SmartSockets slash is a separator, while dot is an ordinary character. To translate names between EMS and SmartSockets, substitute these characters one for another. For example, the EMS name foo/bar.baz corresponds to the SmartSockets name /foo.bar/baz. However, to avoid confusion, we discourage using either slash or dot as ordinary characters.Although both EMS and SmartSockets both interpret the star (*) character as a wildcard, they differ in its semantics. In this aspect, the mapping is not one-to-one.In EMS, star can match any whole token of a name, but not part of a token. In SmartSockets, star can match part of an token—for example, /foo/b*/baz matches /foo/bar/baz and /foo/box/baz.In EMS the greater-than (>) character is a wildcard that matches any number of trailing tokens. In SmartSockets a string of three dots (...) signifies identical semantics.
![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |