• Navigate to JMS resources in system modules
• Navigate to JMS resources in an application module

1. In Name, a name for the uniform 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.

2. In JNDI Name, enter the JNDI name used to look up the distributed queue within the JNDI namespace.

   Note: A distributed queue that does not have a JNDI Name can be referenced by passing the Name of the distributed topic to javax.jms.QueueSession.createQueue().

3. Optionally, in Template, select a template to define configuration values.
4. In Load Balancing Policy, specify a policy (Round Robin or Random) for how messages are distributed to the members of this distributed queue.
5. In Forward Delay, specify the amount of time, in seconds, that a queue member with messages, but with no consumers, will wait before forwarding its messages to other queue members that do have consumers.
6. In Reset Delivery Count On Forward, species whether or not the delivery count is reset during message forwarding between distributed queue members.
7. Optionally, in Destination Keys, specify keys for sorting messages.
8. In Default Targeting Enabled, specify if this destination uses default targeting. Oracle recommends that destinations, regardless of their type, use Advanced Targeting to ensure that they are directly targeted to a JMS server or SAF agent.

For more information about these fields, see Configuration Options.

• Save changes to JMS resources in system modules
• Save changes to JMS resources in an application module