The Store-and-Forward (SAF) service uses SAF agents to deliver messages reliably between applications that are distributed across WebLogic Server instances. A SAF agent can be configured to have only sending capabilities, receiving capabilities, or both. JMS SAF only requires a sending agent on the sending side for JMS messages. Whereas, WSRM SAF requires both a sending agent and a receiving agent.
To configure a SAF agent:
Note: Once you create a SAF agent, you cannot rename it. Instead, you must delete it and create another one that uses the new name.
Note: When a SAF agent is targeted to a migratable target, it cannot use the default store. Therefore, a custom store must be configured and targeted to the same migratable target.
Note: JMS SAF users should select Sending-only since JMS SAF doesn't require a configured receiving agent.
Note: 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. However, if a SAF agent is targeted to a migratable target, it cannot be targeted to any other server targets, including an entire cluster. See Configure migratable targets for JMS-related services.
After you finish
You can optionally configure additional properties for the new SAF agent, such as basic and advanced general properties, thresholds and quotas, or log file rotation parameters.