When configuring uniform distributed queues, WebLogic Server
uniformly creates the necessary members on the JMS servers to which a
JMS module is targeted. This ensures the consistent configuration of all
distributed destination parameters, particularly in regards to
weighting, security, persistence, paging, and quotas.
The legacy weighted distributed queue feature is still
available for users who prefer to manually fine-tune distributed queue
members. However, BEA strongly recommends configuring uniform
distributed queues to ensure the consistent configuration and deployment
of queue members across a cluster. For more information on creating a
weighted distributed queue, see Create weighted
To create a distributed queue:
If you have not already done so, in the Change Center of the Administration Console, click Lock & Edit (see Use the Change Center).
Administration Console, expand Services >
Messaging and select JMS
JMS Modules table, click the name of JMS module
in which to configure the queue resource.
On the module's
Settings page, click the
New button in the Summary of
Create a New JMS System Module Resource page, use
the Type drop-down to select
Distributed Queue Properties page:
In Name, enter a name for the uniform
In JNDI Name, enter the JNDI name used
to look up the uniform distributed queue within the JNDI
namespace. Applications use the JNDI Name to look up the
distributed queue that does not have a JNDI Name can be
referenced by passing the Name of the distributed queue to
In Load Balancing Policy, specify a
policy (Round Robin or Random) for how messages are distributed to
the members of this uniform distributed queue.
Leave the Allocate Members Uniformly
check box enabled in order for WebLogic Server to uniformly create
and allocate the members of this uniform distributed queue.
Note: Once you create a uniform distributed queue,
you cannot rename it. Instead, you must delete it and create
another one that uses the new name.
On the targeting
In Subdeployments, select a
subdeployment for the uniform distributed queue. If necessary, you
can create a new subdeployment by clicking the Create a
New Subdeployment button. A subdeployment is a
mechanism by which JMS module resources (such as queues, topics,
and connection factories) are grouped and targeted to a server
resource (such as JMS servers, server instances, or
When a SubDeployment is selected, its targeted JMS server,
server, or cluster appear as selected in the
If you are not using subdeployments, in the
Targets box, select the JMS server, server,
or cluster on which to deploy the uniform distributed queue.