edocs Home > Oracle WebLogic Server Documentation > Administration Console Online Help > JMS Destination Key

JMS Destination Key

Column Display     Related Tasks     Related Topics

A JMS destination key allows you to define the sort order of messages that arrive on a specific JMS queue or topic.

This page summarizes the JMS destination keys that have been created for this JMS module.

Column Display

You can show fewer or additional data points on this page by expanding Customize this table and modifying the Column Display list. Each data point displays in its own table column.

The following table lists all of the data points that you can display in columns on this page.

Name Description
Name of

Name of JMS destination key.

Sort Key

The message property name or the name of a message header field on which to sort. Message header field keys start with the letters "JMS" and ignore the Key Type field. (For better performance, use message header fields as sorting keys, rather than message properties.)

Range of Values: The JMS Property name (including user properties) or message header fields that can be sorted on are:

  • JMSMessageID

  • JMSTimestamp

  • JMSCorrelationID

  • JMSPriority

  • JMSExpiration

  • JMSType

  • JMSRedelivered

  • JMSDeliveryTime

Note: This attribute is not dynamically configurable.

MBean Attribute:
JMSDestinationKeyMBean.Property

Changes take effect after you redeploy the module or restart the server.

Key Type

The expected sort key type for this JMS destination key. (This field is ignored for message header field keys, which have an implied type.)

MBean Attribute:
JMSDestinationKeyMBean.KeyType

Changes take effect after you redeploy the module or restart the server.

Direction

The direction (Ascending or Descending) in which this key will sort messages. Select Ascending for a FIFO (first in, first out) sort order. Select Descending for a LIFO (last in, first out) sort order.

Note: This attribute is not dynamically configurable.

MBean Attribute:
JMSDestinationKeyMBean.Direction

Changes take effect after you redeploy the module or restart the server.

Related Tasks

Related Topics