Destination Key beans control the sorting criteria of JMS destinations
If you use the getMBeanInfo
operation in MBeanTypeServiceMBean, supply the following value as this MBean's fully qualified interface name:
weblogic.j2ee.descriptor.wl.DestinationKeyBean
In addition to accessing this MBean by invoking a factory method, you can also access this MBean from the following MBean attributes:
|
This section describes the following attributes:
The expected property type for this destination key. This setting is ignored for message header field keys, which have an implied type.
Privileges | Read/Write |
Type | java.lang.String |
Default Value | String |
Legal Values |
|
Redeploy or Restart required | Changes take effect after you redeploy the module or restart the server. |
The name of this entity, represented in XML as a attribute
Many of the elements within the JMS module are named entities. All of the named entities encased by a type in the XML file must be unique. This is the identifier used to delineate a particular entity within the JMS module.
This attribute cannot be modified externally from the module (for example with a deployment plan) because it may be used inside the module referentially.
Privileges | Read/Write |
Type | java.lang.String |
Redeploy or Restart required | Changes take effect after you redeploy the module or restart the server. |
Optional information that you can include to describe this named JMS descriptor bean.
JMS module saves this note in the JMS descriptor file as XML
PCDATA. All left angle brackets (<) are converted to the XML
entity <
. Carriage returns/line feeds are
preserved.
If you create or edit a note from the Administration Console, the Administration Console does not preserve carriage returns/line feeds.
Privileges | Read/Write |
Type | java.lang.String |
Specifies a message sort key name or the name of a message header field on which to sort messages. Message header field keys ignore the key type and reference message header fields rather than message properties.
Note: For better performance, use message header fields as sorting keys, rather than message properties.
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
JMS_BEA_Size
JMS_BEA_UnitOfOrder
Privileges | Read/Write |
Type | java.lang.String |
Default Value | JMSMessageID |
Redeploy or Restart required | Changes take effect after you redeploy the module or restart the server. |
The direction (Ascending or Descending) in which this key will sort messages.
Selecting the Ascending
option for the JMSMessageID
property implies a FIFO (first in, first out) sort order (the
default for destinations). Select the Descending
option for a LIFO (last in, first out) sort order.
Privileges | Read/Write |
Type | java.lang.String |
Default Value | Ascending |
Legal Values |
|
Redeploy or Restart required | Changes take effect after you redeploy the module or restart the server. |
This section describes the following operations:
|
Return true if the given property has been explicitly set in this bean.
Operation Name | "isSet" |
Parameters | Object [] {
propertyName }
where:
|
Signature | String [] {
"java.lang.String" } |
Returns |
boolean
|
java.lang.IllegalArgumentException
Restore the given property to its default value.
Operation Name | "unSet" |
Parameters | Object [] {
propertyName }
where:
|
Signature | String [] {
"java.lang.String" } |
Returns |
void
|
java.lang.IllegalArgumentException