Introduction and Roadmap

This section describes the contents and organization of this guide—Configuring and Managing WebLogic Store-and-Forward.

Document Scope and Audience

This document is a resource for system administrators responsible for configuring, managing, and monitoring the WebLogic Store-and-Forward service for use with WebLogic JMS and Web Services Reliable Messaging (WSRM).

The topics in this document are relevant to production phase administration, monitoring, or performance tuning topics. This document does not address the pre-production development or testing phases of a software project. For links to WebLogic Server documentation and resources for these topics, see Related Documentation.

It is assumed that the reader is familiar with WebLogic Server system administration. This document emphasizes the value-added features provided by WebLogic SAF and key information about how to use WebLogic Server features and facilities to maintain WebLogic Server in a production environment.

Guide to This Document

This chapter, Introduction and Roadmap, introduces the organization of this guide.
Understanding the Store-and-Forward Service, explains the Store-and-Forward service concepts and features, and describe how they work with WebLogic Server.
Configuring SAF for JMS Messages, describes how to configure the Store-and-Forward resources for JMS messages.
Monitoring and Managing SAF Agents, describes how to describes how to monitor and manage the run-time statistics for your Store-and-Forward service.
Troubleshooting WebLogic SAF, explains how to configure and manage SAF message life cycle logs for stored and forwarded JMS messages, describes SAF debugging tools, and provides a list of frequently asked questions concerning SAF configuration issues.

Related Documentation

For comprehensive guidelines for developing, deploying, and monitoring WebLogic Server applications, see the following documents:

Configuring and Managing WebLogic JMS contains instructions for configuring and managing JMS resources, such as JMS servers, JMS modules, and the Path Service.
Using Web Service Reliable Messaging in Programming WebLogic Web Services contains instruction for using SAF with Web Services Reliable Messaging (WSRM).
Using the WebLogic Persistent Store in Configuring WebLogic Server Environments provides information about the benefits and usage of the system-wide Persistent Store.

Samples and Tutorials for the System Administrator

In addition to this document, BEA Systems provides a variety of code samples and tutorials that show WebLogic Server configuration and API use, and provide practical instructions on how to perform key development tasks. BEA recommends that you run some or all of the samples before configuring your own system.

Examples Available for Download

Additional API examples for download at http://codesamples.projects.dev2dev.bea.com. These examples are distributed as ZIP files that you can unzip into an existing WebLogic Server samples directory structure.

You build and run the downloadable examples in the same manner as you would an installed WebLogic Server example. See the download pages of individual examples for more information at https://codesample.projects.dev2dev.bea.com.

New and Changed SAF Features In This Release

Client-Side Store-and-Forward Messages
For a comprehensive listing of the new WebLogic Server features introduced in release 9.2, see " What's New in WebLogic Server 9.2" in Release Notes.

Client-Side Store-and-Forward Messages

The WebLogic Store-and-Forward (SAF) service introduced in release 9.0 enables WebLogic Server to reliably deliver JMS messages between server-side JMS applications distributed across WebLogic Server clusters, domains, and server instances. In release 9.2, the SAF client provides a mechanism whereby standalone clients can reliably send JMS messages to server-side JMS destinations, even when the SAF client cannot reach the JMS destination due to a network connection failure (e.g., a temporary blip or a network failure). While disconnected, messages sent by a SAF client are stored locally on the client and are forwarded to server-side JMS destinations once the client is reconnected.