EMS supports the ten predefined JMS header fields; see Header Fields.
These two header fields are special cases:
When importing a Rendezvous message to an EMS message, tibemsd
does not set any JMS header fields, except for the special cases noted above.
When exporting an EMS message to a Rendezvous message, tibemsd
groups all the JMS header fields (except for the special cases noted above) into a single submessage within the Rendezvous message. The field JMSHeaders
contains that submessage. Fields of the submessage map the names of JMS header fields to their values.
tibemsd
ignores any JMS header fields that are null or absentit omits them from the exported message.
You can instruct tibemsd
to suppress the entire header submessage in all exported messages by setting the transport property export_headers = false
.
Table 9 presents the mapping of JMS header fields to Rendezvous data types (that is, the type of the corresponding field in the exported message).
When importing a Rendezvous message to an EMS message, tibemsd
sets these JMS properties:
In addition to the two fields described above, when tibemsd
imports a certified message on a tibrvcm
transport, it can also set these properties (if the corresponding information is set in the Rendezvous message):
When exporting an EMS message to a Rendezvous message, tibemsd
groups all the JMS property fields into a single submessage within the Rendezvous message. The field JMSProperties
contains that submessage. Fields of the submessage map the names of JMS property fields to their values.
tibemsd
ignores any JMS property fields that are not set, or are set to nullit omits them from the exported message.
You can instruct tibemsd
to suppress the entire properties submessage in the exported message by setting the transport property export_properties = false
.
tibemsd
can export messages with any JMS message body type to TIBCO Rendezvous. Conversely, tibemsd
can import messages with any message type from TIBCO Rendezvous.
For information about JMS body types, see Message Bodies.
For information about the structure of messages, see JMS Message Structure.
When importing a Rendezvous message, tibemsd
translates it to an EMS message body types based on the presence of the fields in Table 10.
When exporting an EMS message, tibemsd
translates it to a Rendezvous message with the following structure:
JMSHeaders
contains a submessage; see JMS Header Fields. When the transport parameter export_headers
is false
, this field is omitted.JMSProperties
contains a submessage; see JMS Property Fields. When the transport parameter export_properties
is false
, this field is omitted.
JMS Body Type
|
Export Translation
|
---|---|
BytesMessage
|
The message data translates to a byte array that contains the bytes of the original EMS message.
The field
JMSBytes receives this data. It has type TIBRVMSG_OPAQUE .
|
ObjectMessage
|
The message data translates to a byte array containing the serialized Java object.
The field
JMSObject receives this data. It has type TIBRVMSG_OPAQUE .
|
StreamMessage
|
The message data translates to a byte array that encodes the objects in the original EMS message.
The field
JMSStream receives this data. It has type TIBRVMSG_OPAQUE .
|
TextMessage
|
The message data translates to a UTF-8 string corresponding to the text of the original EMS message.
The field
JMSText receives this data. It has type TIBRVMSG_STRING .
|
MapMessage
|
The message data fields map directly to top-level fields in the Rendezvous message. The fields retain the same names as in the original EMS message.
See also, Message Extensions.
|
Table 12 presents the mapping between EMS datatypes and Rendezvous datatypes. The mapping is bidirectional, except for the Rendezvous types that have no corresponding EMS type (for these types the mapping is marked as unidirectional in the middle column of Table 12).
TIBCO Enterprise Message Service™ User’s Guide Software Release 4.3, February 2006 Copyright © TIBCO Software Inc. All rights reserved www.tibco.com |