# Export

When exporting an EMS message, `tibemsd` translates it to one of six SmartSockets message types .

The message has the following structure:

- The named field `JMSHeaders` is the first field (omitted when the transport parameter `export_headers` is `false`). It contains a submessage; see JMS Header Fields.
- The named field `JMSProperties` is the next field (omitted when the transport parameter `export_properties` is `false`). It contains a submessage; see JMS Property Fields.
- The data fields follow the JMS headers and properties (when present). For details about field names and types, see the third column of the following table.

  JMS Message Type | SmartSockets Message Type | Data Fields
  --- | --- | ---
  `JMSBytesMessage` | `T_MT_JMS_BYTES` | One unnamed field of type `T_MSG_FT_BINARY`
  `JMSMapMessage` | `T_MT_JMS_MAP` | Named fields; indeterminate order
  `JMSObjectMessage` | `T_MT_JMS_OBJECT` | One unnamed field of type `T_MSG_FT_BINARY`
  `JMSStreamMessage` | `T_MT_JMS_STREAM` | Unnamed fields in order
  `JMSTextMessage` | `T_MT_JMS_TEXT` | One unnamed field of type `T_MSG_FT_STR`
  All other JMS message types | `T_MT_INFO` | No data fields

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