After creating a SAF imported destination, you can change the SAF imported destination'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 standalone destinations, SAF imported destinations, and connection factories) are grouped and targeted to a server resource (such as SAF agents, server instances, or cluster).
For example, you can group a SAF imported destination with a connection factory in a subdeployment targeted to a specific server instance, which will guarantee that all these resources are co-located to avoid extra network traffic.
To associate a SAF imported destination 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.