distributed queues in a system module
The legacy weighted distributed queue feature is for users who
prefer to manually create queue members to carry extra message load or
have extra capacity. However, BEA 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 on creating
a uniform distributed queue, see Create uniform
distributed queues in a system module.
To create a weighted 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,
select Distributed Queue from the list of JMS
Distributed Queue Properties page:
In Name, enter a name for the weighted
In JNDI Name, enter the JNDI name used
to look up the weighted 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 weighted distributed queue.
Clear the Allocate Members Uniformly
check box to specify that you want manually allocate the members
of this weighted distributed queue.
Note: Once you create a weighted distributed queue,
you cannot rename it. Instead, you must delete it and create
another one that uses the new name.
On the member
allocation page, select the existing queues that you want to add as
members of this weighted distributed queue by moving them from the
Available column into the
The new weighted distributed queue is added to the module's
Summary of Resources table.
To activate these changes, in the Change Center of the Administration Console, click Activate Changes. Not all changes take effect immediately—some require a restart (see Use the Change Center).