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:
A dialog displays in the right pane showing the tabs associated with the SAF agent.
Caution: To preserve SAF message consistency, WebLogic Server prevents you from retargeting an existing SAF agent to a migratable target. Instead, you must 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.
After you finish
If you change a SAF agent target, you must stop and restart WebLogic Server.