Messages


JMS messages have a standard structure. This structure includes the following sections:

The JMS specification details a standard format for the header and body of a message. Properties are provider-specific and can include information on specific implementations or enhancements to JMS functionality. Table 1 describes the message properties available with TIBCO Enterprise Message Service.

Table 1 Summary of message properties (Sheet 1 of 2)
Property
Description
More Info
JMS_TIBCO_COMPRESS
Allows messages to be compressed for more efficient storage.
65
JMS_TIBCO_DISABLE_SENDER
Specifies that the user name of the message sender should not be included in the message, if possible.
68
JMS_TIBCO_IMPORTED
Set by the server when the message has been imported from TIBCO Rendezvous.
86
111
JMS_TIBCO_MSG_EXT
Extends the functionality of map messages to include submessages or arrays.
69
JMS_TIBCO_MSG_TRACE
Specifies the message should be traced from producer to consumer.
231
JMS_TIBCO_PRESERVE_UNDELIVERED
Specifies the message is to be placed on the undelivered message queue if the message must be removed.
67
JMS_TIBCO_SENDER
Contains the user name of the message sender.
68

The JMS standard specifies two delivery modes for messages, PERSISTENT and NON_PERSISTENT. TIBCO Enterprise Message Service also includes RELIABLE_DELIVERY. This delivery mode eliminates some of the overhead associated with the other delivery modes.

For consumer sessions, you can also specify that consumers do not need to acknowledge receipt of messages, if desired.

See Chapter 4, Working With Messages for more information about working with messages. Also, more information about properties specific to TIBCO Enterprise Message Service can be found in the TIBCO Enterprise Message Service Java API Reference included in the online documentation.

String Encoding

TIBCO Enterprise Message Service Java and C clients can use the functions and libraries provided for handling strings with specific character encodings. This is important for applications handling international data or any non-ASCII characters. See Character Encoding in Messages for more information about character encoding in TIBCO Enterprise Message Service clients.

Message Tracing and Monitoring

Administrators can configure the server to trace messages as they are processed. Message information can be written to the log file or to the console. Message monitoring topics can also be used to receive messages that provide details about each message’s processing. See Chapter 10, Monitoring Server Activity for more information about monitoring messages or tracing message activity.


TIBCO Enterprise Message Service™ User’s Guide
Software Release 4.3, February 2006
Copyright © TIBCO Software Inc. All rights reserved
www.tibco.com