Target queues

After you create a queue, you can target it to a single JMS server. Queues depend on the JMS servers they are targeted to for the management of persistent messages, durable subscribers, and message paging.

You can also associated a queue with a configured SubDeployment. A SubDeployment is a mechanism by which JMS module resources (such as queues, topics, and connection factories) are grouped and targeted to a server resource (such as JMS servers, server instances, or cluster). For example, if you want to co-locate a group of destinations with a connection factory that is targeted to a specific JMS server, you can associate the destination with the SubDeployment the connection factory belongs to, provided the connection factory is not already targeted to multiple JMS servers.

To target queues:

If you have not already done so, in the Change Center of the Administration Console, click Lock & Edit (see Use the Change Center).
In the Administration Console, navigate to the queue resource that you want to configure:
- Navigate to JMS Resources in System Modules
- Navigate to JMS resources in an application module
Click the Target tab.
In the SubDeployments field, select a SubDeployment to associate with the queue.
In the JMS Server section, select the JMS server on which you want to deploy the queue. When a SubDeployment is selected, its targeted JMS server appears as selected.
Note: To temporarily stop this queue from receiving messages, you can un-target it from its JMS server by deselecting it.
Save your changes:
- Save Changes to JMS Resources in System Modules
- Save changes to JMS resources in an application module
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).