After creating a foreign server, you can change the foreign server'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 is a mechanism by which JMS module resources (such as destinations, connection factories, and foreign servers) are grouped and targeted to a server resource (such as JMS servers, server instances, or cluster).
For example, you can group a foreign server with a connection factory in a subdeployment targeted to a specific JMS server, which guarantees that all these resources are co-located to avoid extra network traffic. Another advantage of such a configuration would be if the targeted JMS server needs to be migrated to another WebLogic server instance, then the foreign server and all its connections will also migrate along with the JMS server's destinations. However, when standalone queues or topics are members of a subdeployment, a foreign server can only be targeted to the same JMS server.
To associate a foreign server 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.