When importing and translating Rendezvous messages, tibemsd is only able to process standard message field types that are identified by name in the Rendezvous program application. Custom fields and fields identified using a field identifier cannot be imported to EMS.
When tibemsd imports and translates a Rendezvous message, it sets the
JMSDestination field of the EMS message to the value of the Rendezvous subject. Therefore, imported 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.
When tibemsd imports and translates a Rendezvous message, it sets the
JMSReplyTo field of the EMS message to the value of the Rendezvous reply subject, so that EMS clients can reply to the message.
Usually this value represents a Rendezvous subject. You must explicitly configure tibemsd to create a topic with a corresponding name, which exports messages to Rendezvous.
When tibemsd imports and translates a Rendezvous certified message, it sets the
JMSExpiration field of the EMS message to the time limit of the certified message.
Note that if the expiration property is set for a destination, it will override the
JMSExpiration value set by the message producer.
When tibemsd imports and translates a Rendezvous message, it uses the
JMSTimestamp header field to determine when the message was created. If the
JMSTimestamp field is not set, the
tibemsd ignores the expiration field, because expiration is based on an unknown creation time.
The Rendezvous sender must create a field called JMSTimestamp in order to enable message expiration.