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 distributed queues.
To create a distributed queue:
Note: A
distributed queue that does not have a JNDI Name can be
referenced by passing the Name of the distributed queue to
javax.jms.queueSession.createqueue()
.
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.
When a SubDeployment is selected, its targeted JMS server, server, or cluster appear as selected in the Targets box.
You can also reconfigure deployment targets later if you wish. For more information about targeting uniform distributed queues, refer to Uniform distributed queues - configure targets.
The new uniform distributed queue is added to the module's Summary of Resources table.
![]() ![]() |