Configuring and Managing WebLogic JMS

     Previous  Next    Open TOC in new window  Open Index in new window  View as PDF - New Window  Get Adobe Reader - New Window
Content starts here

Introduction and Roadmap

The following sections describe the contents and organization of this guide—Configuring and Managing WebLogic JMS.


Document Scope and Audience

This document is a resource for system administrators who configure, manage, and monitor WebLogic JMS resources, including JMS servers, stand-alone destinations (queues and topics), distributed destinations, and connection factories.

The document is relevant to production phase administration, monitoring, and performance tuning. It 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 Server JMS and key information about how to use WebLogic Server features and facilities to maintain WebLogic JMS in a production environment.


Guide to This Document


Related Documentation

This document contains JMS-specific configuration and maintenance information.

For comprehensive information on developing, deploying, and monitoring WebLogic Server applications:


JMS Samples and Tutorials for the JMS Administrator

In addition to this document, BEA Systems provides JMS code samples and tutorials that document JMS configuration, API use, and key JMS development tasks. BEA recommends that you run some or all of the JMS examples before configuring your own system.

Avitek Medical Records Application (MedRec) and Tutorials

MedRec is an end-to-end sample J2EE application shipped with WebLogic Server that simulates an independent, centralized medical record management system. The MedRec application enables patients, doctors, and administrators to manage patient data using a variety of different clients.

MedRec demonstrates WebLogic Server and J2EE features, and highlights BEA-recommended best practices. MedRec is included in the WebLogic Server distribution, and can be accessed from the Start menu on Windows machines. For Linux and other platforms, you can start MedRec from the WL_HOME\samples\domains\medrec directory, where WL_HOME is the top-level installation directory for WebLogic Platform.

JMS Examples in the WebLogic Server Distribution

This release of WebLogic Server optionally installs API code examples in WL_HOME\samples\server\examples\src\examples, where WL_HOME is the top-level directory of your WebLogic Server installation. You can start the examples server, and obtain information about the samples and how to run them from the WebLogic Server Start menu.

Additional JMS Examples Available for Download

Additional API examples for download at 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


New and Changed JMS Features In This Release

WebLogic Server 9.2 includes the following improvements in the administration, availability, and performance of WebLogic JMS.

Note: WebLogic JMS changed substantially in version 9.0, and these changes apply to later releases as well.

Client-Side Store-and-Forward for Reliable JMS Messaging

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. For example, a JMS message producer connected to a local server instance can reliably forward messages to a JMS destination on a remote server instance, even though the remote destination may be temporarily unavailable when the message was sent.

In release 9.2, the JMS SAF Client provides a store-and-forward mechanism whereby standalone JMS clients can reliably send messages to server-side JMS destinations, even when a JMS client cannot temporarily reach a destination (for example, due to a network connection failure). While disconnected from the server, messages sent by a JMS SAF client are stored locally on the client and are forwarded to server-side JMS destinations when the client reconnects.

See Reliably Sending Messages Using the JMS SAF Client in Programming Stand Alone Clients.

Automatic Failover for JMS Message Consumers

With the automatic JMS client reconnect feature, if a server or network failure occurs, some JMS client objects will attempt to transparently failover to another server instance, if one is available. In release 9.1 or later, WebLogic JMS message producers automatically attempt to reconnect to an available server instance without any manual configuration or changes to existing client code. For release 9.2, you can use the Administration Console or WebLogic JMS APIs to configure WebLogic JMS message consumers to automatically reconnect to an available server instance.

See Automatic Failover for JMS Clients in Programming WebLogic JMS.

Unit-of-Work Message Groups

Release 9.0 introduced the Message Unit-of-Order feature, which groups messages by delivering messages within the unit one at a time. However, some applications need an even more restricted notion of a group. Therefore, release 9.2 introduces the Unit-of-Work feature, which allows applications to send JMS messages, identifying some of them as a group and allowing the consumer to process them as such. For example, an application can designate a set of messages that need to be delivered to a single client without interruption, so that the messages can, indeed, be processed as a unit.

See Unit-of-Work Message Groups in Programming WebLogic JMS

WebLogic Store Administration

The WebLogic Store administration utility allows you to troubleshoot a WebLogic Store or to extract its data. The most common uses-cases for store administration are for compacting a file store to reduce its size and for dumping the contents of a file store or JDBC store to an XML file for troubleshooting purposes. This utility can be run from a Java command line or from WLST.

See Administering a Persistent Store in Configuring WebLogic Server Environments.

Improved Non-Persistent Messaging Performance with One-Way Message Sends

You may greatly improve the performance of typical non-persistent messaging by using one-way message sends. By enabling the "One-Way Send Mode" option on your connection factory, its associated producers can send messages without internally waiting for a response from the target destination's host JMS server. You can choose to allow queue senders and topic publishers to do one-way sends, or limit this capability to topic publishers only. You can also configure a one-way window size to determine when a two-way message is required to regulate producer before they can continue making additional one-way sends.

See Using One-Way Message Sends for Improved Non-Persistent Message Performance in WebLogic Server Performance and Tuning.

JMS Delivery Count Message Property

JMSXDeliveryCount is a system generated property that specifies the number of message delivery attempts, where the first attempt is 1, the second is 2, and so on. WebLogic Server makes a best effort to persist the delivery count, so that the delivery count does not reset back to one after a server reboot. See Message Property Fields in Programming WebLogic JMS.

Deprecation of Messaging Bridge Adapter for WLS 5.1

BEA WebLogic Server 5.1 is retired and is no longer supported. In this release, the Messaging Bridge adapter used to interoperate with WebLogic Server 5.1 is deprecated and will be removed in the next major release. See WebLogic Server 5.1 End-of-Life Announcement in Supported Configurations.


WebLogic Server Value-Added JMS Features

WebLogic JMS provides numerous WebLogic JMS Extension APIs that go above and beyond the standard JMS APIs specified by the JMS 1.1 Specification. Moreover, it is tightly integrated into the WebLogic Server platform, allowing you to build secure J2EE applications that can be easily monitored and administered through the WebLogic Server console. In addition to fully supporting XA transactions, WebLogic JMS also features high availability through its clustering and service migration features, while also providing interoperability with other versions of WebLogic Server and third-party messaging providers.

The following sections provide an overview of the unique features and powerful capabilities of WebLogic JMS.

Enterprise-grade Reliability

Enterprise-level Features


WebLogic JMS features enterprise-class performance features, such as automatic message paging, message compression, and DOM support for XML messages:

Tight Integration with WebLogic Server

Interoperability With Other Messaging Services

  Back to Top       Previous  Next