The WebLogic JMS Server

WebLogic Server provides a fully compliant JMS messaging service that is implemented as a JMS server ”WebLogic JMS. WebLogic JMS strictly adheres to the JMS API specification 1.0.2b and provides the following feature set:

• A single, unified messaging API that can be leveraged by other WebLogic Server APIs and facilities, such as Enterprise Java Beans (EJB), JDBC connection pools, servlets, and RMI.

• Full support for the PTP and Pub/Sub messaging domains.

• Support for durable subscribers by storing messages until the durable subscriber becomes active again to receive messages.

• Support for distributed transactions and the two-phase commit protocol using Java Transaction API (JTA) transactions. JMS applications can also participate in transactions with other Java APIs that use JTA, including non-WebLogic XA-compliant message brokers .

• Support for messages containing XML.

• Support for Session acknowledgement-based delivery of messages by persistently storing messages until the consumer issues an acknowledgement reply that indicates a successful receipt of the message.

• Support for multicasting, allowing the broadcast of messages to a select group of hosts using an IP multicast address.

• Can use either a database or a file for persistent message storage.

• Allows Administration objects to be configured by setting attributes from the WebLogic Administration Console and/or using the JMS API to override values.

• Supports service continuity in the event of a WebLogic Server failure within a cluster by enabling you to configure multiple physical destinations (queues and topics) as members of a single distributed destination set. Through WebLogic distributed destinations, producers and consumers are able to send and receive messages. WebLogic JMS then distributes the messaging load across all available destination members within the distributed destination. When a member becomes unavailable due to a server failure, traffic is then redirected toward other available destination members in the set.

• Using the Flow Control feature, you can enable a JMS server or destination to slow down message producers when WebLogic JMS determines that it is becoming overloaded.

• The WebLogic Messaging Bridge enables you to configure a forwarding mechanism between any two messaging products, thereby providing interoperability between separate implementations of WebLogic JMS or between WebLogic JMS and another messaging product.

• The Message Paging feature can free up virtual memory during peak message load periods by swapping out messages from virtual memory to persistent storage when message loads reach a specified threshold.

• Provides support for the configuration of a server-side session pool that provides a pool of JMS Sessions that connection consumers can retrieve in order to process messages concurrently.

The following sections will describe the configuration and administration tasks related to the WebLogic JMS. Only after you have correctly configured a WebLogic JMS will you be able to develop a WebLogic JMS application, which is described in the section "Developing a WebLogic JMS Application" later in this chapter.