If the export_headers is defined as
true in the common EMS transport properties, the EMS server converts the JMS header fields and their values to TIBCO FTL fields and values and adds them to the outgoing message. This allows TIBCO FTL to use content matchers on the fields.
If the export_headers property is
false, then the JMS header fields and their values are
not included in the exported TIBCO FTL message. This includes the destination name. That is, if
export_headers = false for the transport, then the message exported to TIBCO FTL will not contain the destination name.
When converting the JMS header fields to TIBCO FTL message fields, header fields are given the prefix _emshdr:. For example, the JMSDeliveryMode header field is assigned the field name
_emshdr:JMSDeliveryMode when inserted into the TIBCO FTL message.
Table 68 presents the mapping of JMS header fields to TIBCO FTL message field name and types (that is, the name and type of the corresponding field in the exported message).
If export_properties is defined as
true in the common EMS transport properties, the EMS server converts the JMS properties and their values to TIBCO FTL fields and values and adds them to the outgoing message. This allows TIBCO FTL to use content matchers on the fields.
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 exclude the properties fields from the exported message by setting the transport property
export_properties = false.
tibemsd can export messages with most JMS message body types to TIBCO FTL. However, Object messages and Stream messages cannot be exported. They are discarded with a warning.
tibemsd can import messages with any message format from TIBCO FTL.
When importing a TIBCO FTL message, tibemsd translates it to an EMS message body type based on the TIBCO FTL message format, as shown in
Table 69.
When exporting an EMS message, tibemsd translates it to a TIBCO FTL message with the following structure:
When tibemsd converts messages, it converts fields individually, based on field type. Some field types are equivalent between EMS and TIBCO FTL, while converting others may result in some information loss of data type, or require additional formatting.
Not all TIBCO FTL field types are supported by EMS. When tibemsd imports a TIBCO FTL message, these fields are converted into EMS sub-messages as shown below.
When exporting an EMS message, tibemsd translates it to a TIBCO FTL message. Not all field types that are supported by EMS map to TIBCO FTL. When
tibemsd converts these fields, some information about data size is lost. The EMS fields are converted to TIBCO FTL fields as shown here: