The JMS Headers panel allows you to configure the headers of your requests and their options.
|JMSCorrelationID||The JMS message header property. See below for more information.|
|JMSReplyTo||The JMS message header property. See below for more information.|
|JMSType||The JMS message header property. See below for more information.|
|JMSPriority||The JMS message header property. See below for more information.|
|JMSDeliveryMode||The JMS message header property. See below for more information.|
|TimeToLive||Specifies the time period for which a request will remain valid (in milliseconds). If set to zero, or if no value is specified, the request will never expire.|
|Send As BytesMessage||Sets the type of outgoing messages to BytesMessage.|
|Add SoapAction as property||
|Durable Subscription Name||
Sets a durable subscription name, the default name is
|ClientID||Sets a client ID for the JMS connection.|
|Message Selector||Specifies a message selector that determines which message to receive.|
The header can also contain some application-specific information stored as keyword/value properties. However, not all providers allow storing an arbitrary amount of data in the header. It is a good idea to keep most application-specific data in the message body.
JMSCorrelationID associates a message with some other message or application-specific ID. Usually, this is done to determine to which message a reply is sent.
JMSReplyTo indicates the JMS topic or JMS queue where replies should be addressed.
The most important header value is
JMSType. This string is used to determine what kind of message is sent. Handlers often examine the
JMSType value to understand how they should handle an incoming message.
JMSPriority indicates the importance of the message from 0 to 9, where 0 is the least important and 9 is the most important. 4 indicates normal priority, and values over 5 indicate the messages have high priority.
The JMS delivery mode ensures that the message is not lost in transit.
|Note:||The mode applies only to delivery, not to storage after receipt.|
Persistent messages cannot be lost in transit without causing problems.
Non-persistent messages can occasionally be lost without negative effects.
You specify message selectors in JMS headers. Message selectors can filter out messages that have specific parameters. For example, you can command a message selector to receive only messages with the
JMSType value equal to
atg.das.Startup. Message selectors can work both with system properties and with application-specific header properties.