# Export

When exporting an EMS message, `tibemsd` translates it to a TIBCO FTL message with the following structure:

- When `export_headers` is enabled on the EMS transport, JMS header fields are converted to TIBCO FTL message fields. See JMS Header Fields. When the transport parameter `export_headers` is `false`, these fields are omitted.
- When `export_properties` is enabled on the EMS transport, JMS property fields are converted to TIBCO FTL message fields. See JMS Property Fields. When the transport parameter `export_properties` is `false`, these fields are omitted.
- When translating the data fields of an EMS message, the results depend on the JMS body type. specifies the mapping.

  JMS Body Type | Export Translation
  --- | ---
  `MapMessage` | An FTL message of the format specified. If no format was specified, it is a dynamically formatted FTL message.
  `BytesMessage` | An FTL message with one opaque field with the key of `_data`.
  `TextMessage` | FTL message with a`_text` field.
  `Message` | Empty FTL message.
  `ObjectMessage` | Not converted. Messages with this JMS body type cannot be exported to TIBCO FTL.
  `StreamMessage` | Not converted. Messages with this JMS body type cannot be exported to TIBCO FTL.

Copyright © Cloud Software Group, Inc. All rights reserved.