edocs Home > BEA WebLogic Server 10.0 Documentation > Administration Console Online Help > Create Store-and-Forward agents

Administration Console Online Help

    Previous Next  Open TOC in new window 
Content starts here

Create Store-and-Forward agents


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.

In a clustered server environment, a SAF agent can be targeted to a migratable target. A migratable target is a special target that can serve as a grouping of migratable JMS services, such as a SAF agent, and which is active on only one server member in a WebLogic cluster. In a cluster, 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. This way the SAF agent can be manually migrated from an unhealthy server onto a healthy server, either in the event of server crash or for scheduled maintenance.

To configure a SAF agent:

  1. If you have not already done so, in the Change Center of the Administration Console, click Lock & Edit (see Use the Change Center).
  2. In the left panel of the console, expand Services > Messaging and select Store-and-Forward Agents.
  3. On the Summary of Store-and-Forward Agents page, click New.

    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.

  4. On the Create a New Store-and-Forward Agent page:
    1. Name -- Name for the SAF agent.
    2. Persistent Store -- Select a custom persistent store if you want a dedicated store for SAF messages or click Create a New Store to configure a new custom store. If you leave this field set to none, then the SAF agent will use the default file store that is automatically configured on each targeted server instance. For more information about configuring stores, see Configure persistent stores.

      Note: When a SAF agent is targeted to a migratable target (see Step 4), it cannot use the default store, so a custom store must be configured and targeted to the same migratable target.

    3. Agent Type -- Select one of the following:
      • Sending-only -- Configures an agent that stores messages in persistent storage, forwards messages to the receiving side, and re-transmits messages when acknowledgements do not come back in time.
      • Receiving-only -- Configures an agent that detects and eliminates duplicate messages sent by a receiving agent, and delivers messages to the final destination.
      • Both -- Configures an agent that has sending and receiving agent functionality.

      Note: JMS SAF users should select Sending-only since JMS SAF doesn't require a configured receiving agent.
    4. Click Next.
  5. On the Selects Targets page, select the server instance, cluster, or migratable target where you want to deploy the SAF agent.

    A migratable target is a special target that can serve as a grouping of JMS-related services, such as SAF agents, and which is active on only server member in a WebLogic cluster. In a cluster, 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. See Configure migratable targets for JMS-related services.

    Note: If a SAF agent is targeted to a migratable target, it cannot be targeted to any other targets, including an entire cluster. See Configure migratable targets for JMS-related services.

  6. Click Finish.
  7. 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

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.


  Back to Top