EMS Message Properties
In the properties area, applications, vendors, and administrators on JMS systems can add optional properties. The properties area is optional, and can be left empty. The JMS specification describes the JMS message properties. This section describes the message properties that are specific to EMS.
TIBCO-specific property names begin with JMS_TIBCO. Client programs may use the TIBCO-specific properties to access EMS features, but not for communicating application-specific information among client programs.
The EMS properties are summarized in the following table and described in more detail in subsequent sections.
| Property | Description | More Info |
|---|---|---|
| JMS_TIBCO_COMPRESS | Allows messages to be compressed for more efficient storage. | Message Compression |
| JMS_TIBCO_DISABLE_SENDER | Specifies that the user name of the message sender should not be included in the message, if possible. | Including the Message Sender |
| JMS_TIBCO_IMPORTED | Set by the server when the message has been imported from TIBCO FTL. | Import |
| JMS_TIBCO_MSG_EXT | Extends the functionality of the MapMessage and StreamMessage body types to include submessages or arrays. | EMS Extensions to JMS Messages |
| JMS_TIBCO_MSG_TRACE | Specifies the message should be traced from producer to consumer. | Message Tracing |
| JMS_TIBCO_PRESERVE_UNDELIVERED | Specifies the message is to be placed on the undelivered message queue if the message must be removed. | Undelivered Message Queue |
| JMS_TIBCO_SENDER | Contains the user name of the message sender. | Including the Message Sender |
Copyright © 2021. Cloud Software Group, Inc. All Rights Reserved.