After creating a queue, you can change the queue's subdeployment, which is either a system-generated subdeployment (using the protected BEA_JMS_SUBDEPLOYMENT_XXXX name space) or a user-defined subdeployment. A subdeployment for JMS destinations is a mechanism by which queues and topics, and possibly connection factories, are grouped and targeted to a single JMS server. Queues and topics depend on the JMS servers they are targeted to for the management of persistent messages, durable subscribers, and message paging.
For example, if you want to co-locate a group of queues with a connection factory that is targeted to a specific JMS server, you can associate the queues with the subdeployment the connection factory belongs to, provided the connection factory is not already targeted to multiple JMS servers (for example, targeted to a server instance hosting multiple JMS servers).
To associate a queue with a subdeployment:
To manage existing subdeployments in a module, use the module's Subdeployment management page. For more information, see Configure subdeployments in JMS system modules.
After you finish