OTN Home > Oracle WebLogic Server 12.2.1.2.0 Documentation > Administration Console Online Help > Configure Store-and-Forward Agents

Administration Console Online Help

Previous Next Open TOC in new window
Content starts here

Configure Store-and-Forward Agents


The Store-and-Forward (SAF) service enables WebLogic Server to deliver messages reliably between applications that are distributed across WebLogic Server instances. If the destination is not available at the moment the messages are sent, either because of network problems or system failures, then the messages are saved on a local server instance, and are forwarded to the remote destination once it becomes available.

SAF agents are responsible for store-and-forwarding messages between local sending and remote receiving endpoints. 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.

The main steps for configuring SAF services are:

  1. Create Store-and-Forward agents.
  2. Optionally, optionally configure additional properties for a SAF agent, such as basic and advanced general properties, thresholds and quotas, or SAF log file rotation parameters.
  3. Optionally, configure a persistent store if you want a dedicated store for stored-and-forwarded messages instead of using the default store. For more information about configuring a persistent store, see Configure custom persistent stores.
  4. Optionally, configure a Path Service if the sending-side is a cluster and the JMS producer is associated with a Unit-of-Order, which enables JMS message producers to group ordered messages into a single unit. See Create path services.

    For more information about JMS Unit-of-Order, see Using Message Unit-of-Order.

  5. Configure store-and-forward destinations for JMS modules, as described in Configure JMS SAF.
  6. If you skipped the targeting step when you created a SAF agent, or want to modify the current targeting parameters, you can do so at anytime. You can retarget a SAF agent to a different server instance, cluster, or migratable target in your domain. Migratable targets define a set of WebLogic Server instances in a cluster that can potentially host a pinned service, such as a SAF agent. See Change SAF agent targets.

    Note: A recommended best practice is to target a SAF agent to a migratable target, so that a member server will not be a single point of failure. A SAF agent can also be automatically migrated from an unhealthy server instance to a healthy server instance, with the help of the server health monitoring services. However, if a SAF agent is targeted to a migratable target, it cannot be targeted to any other targets, including an entire cluster.

Related Tasks

Related Topics


Back to Top