Administration Console Online Help
JMS Queue --> Configuration --> General
Tasks Related Topics Attributes
Overview
This tab defines general configuration attributes for a queue destination. After defining a JMS server, you can configure its queues. You can configure one or more queues for each JMS server.
Note: You configure queues explicitly or by configuring a JMS template that can be used to define multiple queues with similar attribute settings, as described in JMS Template Tasks.
Tasks
Creating a JMS Queue
Related Topics
"WebLogic JMS Fundamentals" in Programming WebLogic JMS
"Managing WebLogic JMS" in Programming WebLogic JMS
"Developing a WebLogic JMS Application" in Programming WebLogic JMS
Attributes
Table 2-1
|
Attribute Label
|
Description
|
Value Constraints
|
|
Name
|
The name of this queue destination configuration. WebLogic Server uses an MBean to implement and persist the configuration.
MBean: weblogic.management.
configuration.
JMSQueueMBean
Attribute: Name
|
|
|
JNDIName
|
The JNDI name used to look up this queue destination within the JNDI namespace. If not specified, the destination name is not advertised through the JNDI namespace and cannot be looked up and used.
This attribute is not dynamically configurable.
MBean: weblogic.management.
configuration.
JMSQueueMBean
Attribute: JNDIName
|
|
|
Replicate JNDI Name In Cluster
|
Specifies whether the JNDI name for this queue destination (if specified) is replicated across the cluster. If this option is not selected, then the JNDI name for the queue (if specified) is only visible on the server hosting this queue.
This attribute is not dynamically configurable.
MBean: weblogic.management.
configuration.
JMSQueueMBean
Attribute: JNDINameReplicated
|
Default: true
Valid values:
|
|
Enable Store
|
Specifies whether this queue destination supports persistent messaging by using the JMS store specified by the JMS server.
default - The queue destination uses the JMS store defined for the JMS server--if one is defined--and supports persistent messaging. However, if a JMS store is not defined for the JMS server, then persistent messages are automatically downgraded to non-persistent.
This attribute is not dynamically configurable.
MBean: weblogic.management.
configuration.
JMSQueueMBean
Attribute: StoreEnabled
|
Default: default
Valid values:
|
|
Template
|
The JMS template from which this queue destination is derived.
If a JMS template is specified, the queue destination attributes that are set to their default values will inherit their values from the JMS template at run time. However, if this attribute is not defined, then the attributes for the queue destination must be specified as part of the destination.
The Template attribute setting per destination is static. The JMS template's attributes, however, can be modified dynamically.
MBean: weblogic.management.
configuration.
JMSQueueMBean
Attribute: Template
|
|
|
Destination Keys
|
The sort ordering for messages that arrive on this queue destination.
The keys are ordered from most significant to least significant. If more than one key is specified, a key based on the JMSMessageID property can only be the last key in the list.
Note: If JMSMessageID is not defined in the key, it is implicitly assumed to be the last key and is set as "ascending" (first-in, first-out) for the sort order.
MBean: weblogic.management.
configuration.
JMSQueueMBean
Attribute: DestinationKey
|
|
