Skip navigation.
Downloads | Product Documentation | Support

Administration Console Online Help

# Specify subdeployments for SAF imported destinations

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:

1. If you have not already done so, in the Change Center of the Administration Console, click Lock & Edit (see Use the Change Center).
2. In the Administration Console, navigate to the SAF imported destination resource that you want to configure:
   - Navigate to JMS Resources in System Modules
   - Navigate to JMS resources in an application module
3. Click the Subdeployment tab.
4. In the Subdeployments drop-down, select a subdeployment to associate with the SAF imported destination.

   To manage existing subdeployments in a module, use the module's Subdeployment management page. For more information, see Configure subdeployments in JMS system modules.

5. Save your changes:
   - Save Changes to JMS Resources in System Modules
   - Save changes to JMS resources in an application module
6. 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).