Skip navigation.
Downloads | Product Documentation | Support

Administration Console Online Help

# Uniform Distributed Queue: Configuration: General

Configuration Options Advanced Configuration Options Related Tasks Related Topics

Use this page to define the general configuration parameters for a distributed queue, such as selecting a destination key for sorting messages as they arrive on the distributed queue members.

#### Configuration Options

Name | Description
--- | ---
Name | The name of this distributed queue. MBean Attribute: `JMSDestinationMBean.Name` Changes take effect after you redeploy the module or restart the server.
JNDI Name | The name used to bind a virtual destination to the JNDI tree. Applications can use the JNDI name to look up the virtual destination. If not specified, then the destination is not bound into the JNDI namespace. MBean Attribute (Does not apply to application modules): `DistributedDestinationBean.JNDIName`
Load Balancing Policy | Determines how messages are distributed to the members of this destination. Choose from the following distribution techniques: Round-Robin - The system maintains an ordering of physical topic members within the set by distributing the messaging load across the topic members one at a time in the order that they are defined in the configuration file. Each WebLogic Server instance maintains an identical ordering, but may be at a different point within the ordering. If weights are assigned to any of the topic members in the set, then those members appear multiple times in the ordering. Random - The weight assigned to the topic members is used to compute a weighted distribution for the members of the set. The messaging load is distributed across the topic members by pseudo-randomly accessing the distribution. In the short run, the load will not be directly proportional to the weight. In the long run, the distribution will approach the limit of the distribution. A pure random distribution can be achieved by setting all the weights to the same value, which is typically set to 1. MBean Attribute (Does not apply to application modules): `UniformDistributedDestinationBean.LoadBalancingPolicy`
Forward Delay | The number of seconds after which a uniform distributed queue member with no consumers will wait before forwarding its messages to other uniform distributed queue members that do have consumers. The default value of -1 disables this feature so that no messages are forwarded to other uniform distributed queue members. MBean Attribute (Does not apply to application modules): `UniformDistributedQueueBean.ForwardDelay` Secure value: `-1`
Destination Keys | The list of potential destination keys for for sorting the messages that arrive on a JMS destination. The keys are ordered from most significant to least significant. If more than one key is specified, a key based on the JMSMessageID 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" (FIFO) for the sort order. MBean Attribute (Does not apply to application modules): `DestinationBean.DestinationKeys` Changes take effect after you redeploy the module or restart the server.

#### Advanced Configuration Options

Name | Description
--- | ---
Production Paused At Startup | Specifies whether new message production is paused on a destination at startup. default If a JMS template is specified, then this value inherits the template's Production Paused At Startup value. If no JMS template is configured for the destination, then the Default value is equivalent to false. false Production Paused is explicitly disabled for this destination. true Production Paused is explicitly turned on for this destination. MBean Attribute (Does not apply to application modules): `DestinationBean.ProductionPausedAtStartup` Changes take effect after you redeploy the module or restart the server.
Consumption Paused At Startup | Specifies whether consumption is paused on a destination at startup. default If a JMS template is specified, then this value inherits the template's Consumption Paused At Startup value. If no JMS template is configured for the destination, then the Default value is equivalent to false. false Consumption Paused is explicitly disabled for this destination. true Consumption Paused is explicitly turned on for this destination. MBean Attribute (Does not apply to application modules): `DestinationBean.ConsumptionPausedAtStartup` Changes take effect after you redeploy the module or restart the server.
Insertion Paused At Startup | Specifies whether new message insertion is paused on a destination at startup. default If a JMS template is specified, then this value inherits the template's Insertion Paused At Startup value. If no JMS template is configured for the destination, then the Default value is equivalent to false. false Insertion Paused is explicitly disabled for this destination. true Insertion Paused is explicitly turned on for this destination. MBean Attribute (Does not apply to application modules): `DestinationBean.InsertionPausedAtStartup` Changes take effect after you redeploy the module or restart the server.
Unit-of-Order | Specifies whether WebLogic Server creates a system-generated Unit- of-Order name that is statistically unique for a destination. Any message arriving at this destination that does not already belong to a unit-of-order is assigned this default unit-of-order name. The initial use case is to replace the deprecated "ordered redelivery" feature. MBean Attribute (Does not apply to application modules): `DestinationBean.DefaultUnitOfOrder` Changes take effect after you redeploy the module or restart the server.
Unit-of-Order Routing | Determines how a distributed destination member is selected as the destination for a message that is part of a unit-of-order. Hash, indicates that a message producer computes the member destination from the `hashCode` of the unit-of-order. PathService indicates that the configured Path Service determines the member destination. Unit-of-Order Routing can be set programmatically with WLProducer, or administratively on the connection factory or destination. Unit of Order Routing is not dynamically configurable. MBean Attribute (Does not apply to application modules): `UniformDistributedDestinationBean.UnitOfOrderRouting` Changes take effect after you redeploy the module or restart the server.
Attach Sender | Specifies whether messages landing on this destination should attach the credential of the sending user. Supports The JMSXUserID property is set with the security principal of the sending user if requested. The sender can request its identity to be attached to its messages by using a ConnectionFactory with `AttachJMSXUserID="true"`. Never The JMSXUserID property is never be set with the security principal of the sending user. Always The JMSXUserID property is always set with the security principal of the sending user. This attribute is dynamically configurable. A dynamic change of this attribute will affect only messages received after the update has been made. MBean Attribute (Does not apply to application modules): `DestinationBean.AttachSender`
Local JNDI Name | The local JNDI name used to look up the destination within the JNDI namespace of the server where the destination resource is targeted. In a clustered environment, this name is bound only on the local server instance and is not propagated to the rest of the cluster. A destination can have both a local JNDI name and a (global) JNDI name. MBean Attribute (Does not apply to application modules): `DestinationBean.LocalJNDIName`
SAF Export Policy | Specifies whether a user can send messages to a destination using Store-and-Forward. All All users can send messages to this destination using Store-and-Forward. None Remote users can not send messages to a destination using Store-and-Forward. This attribute is dynamically configurable. A dynamic change of this attribute will affect only messages sent after the update has been made. MBean Attribute (Does not apply to application modules): `UniformDistributedDestinationBean.SAFExportPolicy` Changes take effect after you redeploy the module or restart the server.
Messaging Performance Preference | Specifies the destination's peformance preference in regards to message latency or throughput. The lower the value, the more the destination will emphasize latency over throughput. Conversely, the higher the value, the more the destination will emphasize throughput over latency. MBean Attribute (Does not apply to application modules): `UniformDistributedDestinationBean.MessagingPerformancePreference` Minimum value: `0` Maximum value: `100`

Related Tasks

- Configure queues
- Configure destination keys

Related Topics

- Configuring and Managing WebLogic JMS
- Programming WebLogic JMS