Jakarta Messaging Property Fields

EMS supports the Jakarta Messaging property fields described in EMS Message Properties.

Import

When translating an incoming Kafka message into an EMS message, the EMS server first converts any Jakarta Messaging Header Fields present in the Kafka message headers. Each remaining Kafka message header is then set as a Jakarta Messaging property field of type byte[] in the translated EMS message.

If the Kafka message is imported via a transport configured with schema_repository and the message payload contains a schema ID, the EMS server sets that schema ID in the
JMS_TIBCO_IMPORTED_SCHEMA_ID property of the translated EMS message.

Additionally, the EMS server will always set the JMS_TIBCO_IMPORTED property value to true on an imported message to indicate that the message did not originate from an EMS client.

Export

The EMS server converts the Jakarta Messaging properties and their values into key/value pairs (all property field values are converted to strings) and sets them as headers in the outgoing Kafka message.

The EMS server ignores any Jakarta Messaging property fields that are not set, or are set to null—it omits them from the exported message.