A SAF imported destination resource is a collection of imported SAF
destinations that represent JMS destinations in a remote server instance
or cluster. Each collection of SAF imported destinations is associated
with a remote SAF context resource, and optionally, a SAF
error handling resource. When a JMS producer sends messages to a SAF
destination, these messages are stored on the SAF destination for future
delivery. A SAF agent forwards the messages to the remote JMS
destination (that the imported destination represents) when the
destination is reachable, using the SAF remote context.
To create a SAF imported destination:
If you have not already done so, in the Change Center of the Administration Console, click Lock & Edit (see Use the Change Center).
Administration Console, expand Services >
Messaging and select JMS
JMS Modules table, click the name of JMS module
in which to configure the imported destination resource.
On the module's
Settings page, click the
New button in the Summary of
Create a New JMS System Module Resource page, use
the Type drop-down to select SAF
Note: Once you create a SAF imported destination
resource, you cannot rename it. Instead, you must delete it and
create another one that uses the new name.
SAF Imported Destination Properties page, define
the properties that will define your imported destination
Name -- Name for the SAF imported
JNDI Prefix -- Specifies a prefix that
is appended to the remote destination JNDI name.
Remote SAF Context -- Select a remote
context instance. If necessary, click Create a New
Remote Context. See Create SAF remote
Time to Live -- Default Time-To-Live
value (expiration time), in milliseconds, for JMS messages.
Enable Time To Live
Default -- Select to override the expiration time set
on JMS messages.
For more information about these fields, see Configuration Options.
On the targeting
In SubDeployments, select a
subdeployment for the SAF imported destination. If necessary, you
can create a new subdeployment by clicking the Create a
New Subdeployment button. A subdeployment is a
mechanism by which JMS module resources (such as queues, topics,
and connection factories) are grouped and targeted to a server
resource (such as JMS servers, server instances, or
When a SubDeployment is selected, its targeted JMS server,
server, or cluster appear as selected in the
If you are not using subdeployments, in the
Targets box, select the SAF Agent, cluster
or server instance(s) where you want to deploy imported
You can also reconfigure
deployment targets later if you wish. For more information about
targeting imported destinations, refer to Target SAF
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
If you want to configure additional parameters for the new SAF
imported destination or Store-and-Forward destinations, see: