Export
When exporting an EMS message to a Rendezvous message,
tibemsd
groups all the Jakarta Messaging header fields into a single submessage within the Rendezvous message. The field
JMSHeaders
contains that submessage. Fields of the submessage map the names of Jakarta Messaging header fields to their values.
The
tibemsd
server ignores any Jakarta Messaging header fields that are not set, or are set to null—it omits them from the exported message.
You can instruct
tibemsd
to suppress the entire header submessage in the exported message by setting the transport property
export_headers = false
.
The following table shows the mapping of Jakarta Messaging header fields to Rendezvous data types (that is, the type of the corresponding field in the exported message).
Jakarta Messaging Header Name | Rendezvous Type |
---|---|
JMSDeliveryMode
|
TIBRVMSG_U8 |
JMSDeliveryTime
|
TIBRVMSG_U64
|
JMSPriority
|
TIBRVMSG_U8
|
JMSTimestamp
|
TIBRVMSG_U64
|
JMSExpiration |
TIBRVMSG_U64 |
JMSType |
TIBRVMSG_STRING
|
JMSMessageID |
TIBRVMSG_STRING
|
JMSCorrelationID |
TIBRVMSG_STRING
|
JMSRedelivered
|
TIBRVMSG_BOOL
|
JMSDestination
|
send subject in TIBCO Rendezvous |
JMSReplyTo
|
reply subject in TIBCO Rendezvous |