> Import Issues
> This section presents issues associated with importing messages to EMS from SmartSockets—whether on a topic or a queue.
> Import Destination Names Must be Unique

> | When a topic and a queue share the same name, at most one of them may set the import property. For example, if a topic foo.bar and a queue foo.bar are both defined, only one may specify the import property.

> JMSReplyTo
> When tibemsd imports and translates a SmartSockets message, it sets the JMSReplyTo field of the EMS message to the value of the SmartSockets reply_to header, so that EMS clients can reply to the message.
> Usually this value represents a SmartSockets subject. You must explicitly configure tibemsd to create a topic with a corresponding name, which exports messages to SmartSockets.
> Guaranteed Delivery

> | For full end-to-end guaranteed delivery from SmartSockets to EMS, all three of these conditions must be true:
> ● | SmartSockets senders must send messages with guaranteed message delivery (GMD).
> ● | The transport definition must set topic_import_dm or queue_import_dm (as appropriate) to TIBEMS_PERSISTENT.
> ● | A durable subscription for the EMS topic or queue must exist.

> For export guarantees, see Guaranteed Delivery.

Copyright © TIBCO Software Inc. All Rights Reserved.