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 absent—it 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 72 presents the mapping of JMS header fields to Rendezvous data types (that is, the type of the corresponding field in the exported message).
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.
The tibemsd server ignores any JMS property 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 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.
When importing a Rendezvous message, tibemsd translates it to an EMS message body type based on the presence of the field in
Table 74.
When exporting an EMS message, tibemsd translates it to a Rendezvous message with the following structure:
Table 76 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 76).