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:
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.
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.
For more information about these fields, see Configuration Options.
Caution: If you click Finish at this point, the SAF imported destination will be created but 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 simply accept the parent JMS system module's default targets or proceed to an advanced targeting page where you can use the subdeployment mechanism for targeting this SAF imported destination.
Upon clicking Finish, the configured SAF imported destination is added to the module's Summary of Resources table, which displays its default targets. The default targeting will also be reflected by the Default Targeting Enabled checkbox on the SAF imported destination's Configuration: General page.
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.
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: