Skip navigation.
Downloads | Product Documentation | Support

Administration Console Online Help

# Create SAF imported destinations in JMS system modules

Before you begin

- Create SAF remote contexts
- Configure SAF error handling resources

SAF imported destinations are collections of SAF queues and topics that locally represent JMS queues or topics on a remote server instance or cluster. Each collection of imported destinations is associated with a remote SAF context. They can also share the same JNDI prefix, time-to-live default (message expiration time), and SAF error handling policy.

To create SAF imported destinations:

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, expand Services > Messaging and select JMS Modules.
3. In the JMS Modules table, click the name of JMS module in which to configure the imported destination resource.
4. On the module's Settings page, click the New button in the Summary of Resources table.
5. On the Create a New JMS System Module Resource page, select SAF Imported Destinations from the list of JMS resources, and then click Next.
6. On the SAF Imported Destination Properties page, define the SAF imported destination's basic properties:
   1. Name -- Enter a name for the SAF imported destinations resource.

      Once you create a SAF imported destination, you cannot rename it. Instead, you must delete it and create another one that uses the new name.

   2. JNDI Prefix -- Specify a prefix that is appended to the remote destination JNDI name.

      If you do not specify a JNDI name for the SAF imported destination, it will not be available for JNDI lookup even after the SAF imported destination has been targeted to a server resource. Therefore, you will only be able to access the SAF imported destination in an application-scoped context.

   3. Remote SAF Context -- Select a remote context instance. If necessary, click Create a New Remote Context to create one. See Create SAF remote contexts.
   4. SAF Error Handling -- Select an error handling instance. If necessary, click Create a New Error Handling to create one. See Create SAF error handling resources.
   5. Enable SAF Default Time-to-Live -- Select to override the expiration time set on JMS messages with the value specified in the SAF Default Time-to-Live field.
   6. SAF Default Time-to-Live -- Specify a default Time-to-Live value, in milliseconds, for JMS messages. The expiration time set on JMS messages will override this value unless the Enable SAF Default Time-to-Live check box is selected

   For more information about these fields, see Configuration Options.

7. Click Next to proceed to the targeting page or click Finish to create the SAF imported destination.

   Caution: If you click Finish at this point, the SAF imported destination will be created without any targeting information. As a result, the SAF imported destination will not be deployed and thus will not be available to applications until you manually select a subdeployment target, as described in Specify subdeployments for SAF imported destinations.

   On the targeting page, you can either target the SAF imported destination to system-selected SAF agents(s), server instance(s), or cluster, or optionally proceed to an advanced targeting page where you can either select an existing subdeployment or create a new subdeployment. A subdeployment is a mechanism by which JMS module resources (such as standalone destinations, uniform distributed destinations, and connection factories) are grouped and targeted to server resources (such as JMS servers, SAF agents, server instances, or cluster).

8. For basic system-selected targeting, in the Targets box simply select a SAF agent(s), server instance(s), or cluster, and then click Finish. A system-owned subdeployment is automatically generated for the SAF imported destination and the selected target(s), using the BEA_JMS_SUBDEPLOYMENT_XXXX name space, where XXXX is the name of the parent module.

   Note: JMS administrators cannot create any subdeployment beginning with BEA_JMS_SUBDEPLOYMENT. This naming restriction is validated during the subdeployment creation process.

   Upon clicking Finish, the configured SAF imported destination is added to the module's Summary of Resources table, which displays its system-generated subdeployment name and its targets. You can also reconfigure subdeployment targets later if you wish. For more information about managing subdeployments, refer to Configure subdeployments in JMS system modules.

9. For advanced targeting, click Advanced Targeting, which allows you to select an existing subdeployment or to create a new one.
   - To select an existing subdeployment for the SAF imported destination, select one from the Subdeployments drop-down. When a valid subdeployment is selected, its targeted SAF agent(s), server(s), or cluster appear as selected in the Targets box. (A subdeployment with standalone destinations can only be targeted to a single JMS server.) Click Finish to add the SAF imported destination to the selected subdeployment.
   - To create a new subdeployment for the SAF imported destination, click the Create a new Subdeployment button. On the Subdeployment Properties page, enter a name for the subdeployment, and then click OK. On the ensuing subdeployment targeting page, select a SAF agent(s), server instance(s), or cluster in the Targets box. (A subdeployment with standalone destinations can only be targeted to a single JMS server.) Click Finish to add the SAF imported destination to the new subdeployment.

   Upon clicking Finish, the configured SAF imported destination is added to the module's Summary of Resources table, which displays the user-defined subdeployment name and its targets. You can also reconfigure subdeployment targets later if you wish. For more information about managing subdeployments, refer to Configure subdeployments in JMS system modules.

10. 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).

After you finish

You can configure additional parameters for the new SAF imported destination, such as selecting how unit-of-order messages should be routed. You can also now create new SAF queues and SAF topics for your imported destinations group. For more information, see:

- Configure SAF imported destinations
- Create SAF queues
- Create SAF topics