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 in a system module.
To create a distributed queue:
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.
If you do not specify a JNDI name for the distributed queue,
it will not be available for JNDI lookup even after it has been
targeted to a server resource. Therefore, you will only be able
to access the distributed queue using the
javax.jms.queueSession.createqueue() API or in
an application-scoped context.
Caution: If you click Finish at this point, the uniform distributed queue will be created without any targeting information. As a result, the uniform distributed queue will not be deployed and thus will not be available to applications until you manually select a subdeployment target, as described in Uniform distributed queues - specify subdeployments.
On the targeting page, you can either target the uniform distributed queue to system-selected JMS server(s), server instance(s), or cluster, or optionally proceed to an advanced targeting page where you can either select an existing subdeployment or create a new subdeployment. A subdeployment is a mechanism by which JMS module resources (such as standalone destinations, uniform distributed destinations, and connection factories) are grouped and targeted to server resources (such as JMS servers, server instance(s), or cluster).
Note: JMS administrators cannot create any subdeployment beginning with BEA_JMS_SUBDEPLOYMENT. This naming restriction is validated during the subdeployment creation process.
Upon clicking Finish, the configured uniform distributed queue is added to the module's Summary of Resources table, which displays its system-generated subdeployment name and its targets. You can also reconfigure subdeployment targets later if you wish. For more information about managing subdeployments, refer to Configure subdeployments in JMS system modules.
Upon clicking Finish, the configured uniform distributed queue is added to the module's Summary of Resources table, which displays the user-defined subdeployment name and its targets. You can also reconfigure subdeployment targets later if you wish. For more information about managing subdeployments, refer to Configure subdeployments in JMS system modules.
After you finish
If you want to configure additional parameters for the new uniform distributed queue, including general properties, thresholds and quotas, producer overrides, logging, and delivery failure properties, see Configure uniform distributed queues.