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. The Adapter supports the following property:
Senders may set this property to request that EMS compress the message before sending it to the server. Senders may set this property to prevent the EMS server from including the sender name in the message when the server sends it to consumers. JMS_TIBCO_PRESERVE_UNDELIVERED Specifies the message is to be placed on the undelivered message queue if the message must be removed. Specified in the FILE_OPTIONS element of the FileType section of the FilePublisher and FileSubscriber configuration files. Valid values are 'body' and 'null'
• When body is specified, the entire EMS message is tracked on the EMS server.
• When null is specified, only the header of the message is tracked.See the EMS documentation for additional information on properties.The JMS standard specifies two delivery modes for messages, PERSISTENT and NON_PERSISTENT. TIBCO EMS 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.More information about properties specific to TIBCO EMS can be found in the TIBCO Enterprise Message Service Java API Reference.
Copyright © TIBCO Software Inc. All Rights Reserved.