edocs Home > Oracle WebLogic Server Documentation > Administration Console Online Help > Configure uniform distributed

Configure uniform distributed queues

A distributed queue is a single unit of JMS queues that are accessible as a single, logical queue to a client (for example, a distributed queue has its own JNDI name). The members of the unit are usually distributed across multiple servers within a cluster, with each queue member belonging to a separate JMS server.

By 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 across a cluster.

The legacy weighted distributed queue feature is still available for users who prefer to manually fine-tune queue members to carry extra message load or have extra capacity. However, Oracle strongly recommends configuring uniform distributed queues to avoid possible administrative and application problems due to a weighted distributed queue not being deployed consistently across a cluster. For more information, see Create weighted distributed queues in a system module.

To configure a uniform distributed queue:

1. If necessary, configure a JMS system module for the queue. See Configure JMS system modules.

2. Before creating a queue resource in a module, optionally create other quota, template, and destination key resources in the module that can be referenced from within the uniform distributed queue:

   • Quotas are used to control the allotment of system resources available to uniform distributed queues. See Configure quotas for destinations.

   • Destination keys allow you to define the sort order of messages that arrive on a specific uniform distributed queue. See Configure destination keys.

3. Create uniform distributed queues in a system module

   After creating a uniform distributed queue, you can define a number of optional properties:

   1. Uniform distributed queues - configure general parameters

      Configuring optional General properties includes selecting a destination key for sorting messages as they arrive on the members of the uniform distributed queue, or modifying the load balancing policy.

   2. Uniform distributed queues - configure advanced parameters

      Configuring optional Advanced properties includes specifying unit-of-order parameters, attaching the credentials of message senders, or defining unit-of-work parameters.

   3. Uniform distributed queues - configure thresholds and quota

      Define upper and lower byte and/or message thresholds for the members of a uniform distributed queue, select a pre-configured quota specifying the maximum number of bytes or messages that the queue is allowed to store, or specify a maximum size allowed for messages on members of the uniform distributed queue.

   4. Uniform distributed queues - configure delivery overrides

      Define message delivery override values, such as message priority and time-to-deliver values, that can override those specified by a message producer.

   5. Uniform distributed queues - configure message logging

      Enable the logging of message life cycle information into a JMS message log file. The content of the message log always includes message ID and correlation ID, but you can also configure information like message type and user properties.

   6. Uniform distributed queues - configure delivery failure parameters

      Define default message delivery failure values, such as defining a message redelivery limit, selecting a message expiration policy, and specifying an error destination for expired messages.

4. If you skipped the targeting step when you created a uniform distributed queue, or want to want to change a uniform distributed queue's selected subdeployment, you can do so at anytime. See Uniform distributed queues - specify a subdeployment.

5. Optionally, add or remove security roles and policies to a distributed queue. See Uniform distributed queues - create security roles and Uniform distributed queues - configure security policies.

6. In the event that you need to troubleshoot a uniform distributed queue, you can temporarily pause all message production, insertion (in-flight messages), and consumption operations on all the members of a distributed queue. See Uniform distributed queues - pause message operations on server restart.

Related Tasks

• Uniform distributed queues - monitor statistics

• Delete distributed queues

Related Topics

• Understanding JMS Resource Configuration

• Configuring Clustered WebLogic JMS Resources

} } (document.images){ dcs_imgarray[dcs_ptr] = new Image; dcs_imgarray[dcs_ptr].src = dcs_src; WT[myMeta.name.substring(3)]=myMeta.content; } if DCSext[myMeta.name.substring(7)]=myMeta.content; } } } } for (N in DCS){P+=A( N, DCS[N]);} for (N in WT){P+=A( "WT."+N, WT[N]);} for (N in DCSext){P+=A( N, DCSext[N]);} //} aCrumb=aCookie[i].split("="); if (crumb==aCrumb[0]){ return aCrumb[1]; } } return null; } i=0;i