Change SAF agent targets

After you create a SAF agent, you can retarget it to a different server instance, cluster, or migratable target in your domain. A migratable target is a logical target that serves as a grouping of services, such as a SAF agent, and which is active on only server member in a cluster. High availability is achieved by migrating a migratable target from one server member to another when a problem occurs on the original server. A recommended best practice is to target the SAF agent to a migratable target, so that a member server will not be a single point of failure. You can manually migrate a migratable target or you configure it for automatic migration.

To retarget your SAF agent to a different server instance, cluster, or migratable target:

If you have not already done so, in the Change Center of the Administration Console, click Lock & Edit (see Use the Change Center).
In the left panel of the console, expand Services > Messaging and select Store-and-Forward Agents.
On the Store-and-Forward Agents page, select the SAF agent that you want to assign to a server, cluster, or migratable target.
A dialog displays in the right pane showing the tabs associated with the SAF agent.
Select the
Targets tab to display the following targeting options.
1. Independent Servers -- Select a server or servers where the SAF agent will be deployed. The SAF agent will be available on all the selected servers.
2. Clusters -- Select a cluster where the SAF agent will be deployed. The SAF agent will be available on all servers in the selected cluster.
3. Migratable Targets -- Select a WebLogic Server migratable target where the SAF agent will be deployed. When WebLogic Server is first booted, the SAF agent is initially available only on the user-preferred server. After that, the SAF agent can be migrated to another server listed in the migratable target.
  Caution: To preserve SAF message consistency, WebLogic Server prevents you from retargeting an existing SAF agent to a migratable target. Instead, delete the existing SAF agent and configure a new one with the same values and target it to a migratable target.
  
  Note: When a SAF agent is targeted to a migratable target, it cannot use the default store, so a custom store must be configured and targeted to the same migratable target. In addition, a migratable SAF agent cannot be targeted to any other targets, including an entire cluster. Therefore, if you want to increase throughput by importing a JMS destination to multiple SAF agents on separate servers in a cluster, then create a migratable target for each server in the cluster, and then create separate SAF agents and target them to each migratable target.
  For more information on configuring a migratable target for SAF agents, see Configure migratable targets for JMS-related services.
Select a target on which to deploy the SAF agent.
Click Save.
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 change a SAF agent target, stop and restart WebLogic Server. } } (document.images){ dcs_imgarray[dcs_ptr] = new Image; dcs_imgarray[dcs_ptr].src = dcs_src; WT[myMeta.name.substring(3)]=myMeta.content; } if DCSext[myMeta.name.substring(7)]=myMeta.content; } } } } for (N in DCS){P+=A( N, DCS[N]);} for (N in WT){P+=A( "WT."+N, WT[N]);} for (N in DCSext){P+=A( N, DCSext[N]);} //} aCrumb=aCookie[i].split("="); if (crumb==aCrumb[0]){ return aCrumb[1]; } } return null; } i=0;i