> Export Issues
> This section presents issues associated with exporting messages from EMS to SmartSockets.
> JMSReplyTo
> Topics
> Consider an EMS message in which the field JMSReplyTo contains a topic. When exporting such a message to SmartSockets, you must explicitly configure tibemsd to import replies from SmartSockets to that reply topic.
> Temporary Topics
> Consider an EMS message in which the field JMSReplyTo contains a temporary topic. When tibemsd exports such a message to SmartSockets, it automatically arranges to import replies to that temporary topic from SmartSockets; you do not need to configure it explicitly.
> Wildcard Subscriptions
> Star Wildcard
> Both EMS and SmartSockets interpret the star character (*) as a wildcard—but with different semantics. EMS accepts star only as a whole element, which matches a whole element. In contrast, SmartSockets accepts star as part of an element, matching a substring within the element.
> When a SmartSockets client subscribes to foo.bar*, then configure tibemsd to export the superset foo.*; RTserver narrows the set by delivering only messages that match subscribers. For a full discussion of the differences between EMS and SmartSockets wildcards, see Destination Name—Syntax and Semantics.
> Guaranteed Delivery

> | For full end-to-end guaranteed delivery to SmartSockets from EMS, both of these conditions must be true:
> ● | EMS senders must send persistent messages.
> ● | The transport definition must set delivery_mode to gmd_some or gmd_all (as appropriate).

> To preserve undelivered GMD messages in the EMS undelivered queue, see preserve_gmd on page 394. For import guarantees, see Guaranteed Delivery.

Copyright © TIBCO Software Inc. All Rights Reserved.