Enterprise-Grade Reliability WebLogic Server Value-Added JMS Features

Introduction and Roadmap 1-3

1.4 JMS Samples and Tutorials for the JMS Administrator

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

1.4.1 Avitek Medical Records Application MedRec and Tutorials

MedRec is an end-to-end sample Java EE 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 Java EE features, and highlights Oracle-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.

1.4.2 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.

1.5 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, available at http:java.sun.comproductsjmsdocs.html . Moreover, it is tightly integrated into the WebLogic Server platform, allowing you to build secure Java EE 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.

1.5.1 Enterprise-Grade Reliability

WebLogic JMS includes the following reliability features: ■ Out-of-the-box transaction support: – Fully supports transactions, including distributed transactions, between JMS applications and other transaction-capable resources using the Java Transaction API JTA, as described in Using Transactions with WebLogic JMS in Programming JMS for Oracle WebLogic Server. – Fully-integrated Transaction Manager, as described in Introducing Transactions in Programming JTA for Oracle WebLogic Server. 1-4 Configuring and Managing JMS for Oracle WebLogic Server ■ File or database persistent message storage both fully XA transaction capable. See Using the WebLogic Persistent Store in Configuring Server Environments for Oracle WebLogic Server. ■ Message Store-and-Forward SAF is clusterable and improves reliability by locally storing messages sent to unavailable remote destinations. See Understanding the Store-and-Forward Service in Configuring and Managing Store-and-Forward for Oracle WebLogic Server. ■ If a server or network failure occurs, JMS producer and consumer objects will attempt to transparently failover to another server instance, if one is available. See Automatic JMS Client Failover in Programming JMS for Oracle WebLogic Server. ■ Supports connection clustering using connection factories targeted on multiple WebLogic Servers, as described in Section 4.1, Configuring WebLogic JMS Clustering. ■ System-assisted configuration of Uniform Distributed Queues, Replicated Distributed Topics, and Partitioned Distributed Topics that provide high availability, load balancing, and failover support in a cluster, as described in Using Distributed Destinations and Developing Advanced PugSub Applications in Programming JMS for Oracle WebLogic Server. ■ Automatic whole server migration provides improved cluster reliability and server migration WebLogic Server now supports automatic and manual migration of a clustered server instance and all the services it hosts from one machine to another, as described in Section 4.1, Configuring WebLogic JMS Clustering. ■ Redirects failed or expired messages to error destinations, as described in Managing Rolled Back, Recovered, Redelivered, or Expired Messages in Programming JMS for Oracle WebLogic Server. ■ Supports the JMS Delivery Count message property JMSXDeliveryCount, which 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 in Programming JMS for Oracle WebLogic Server. ■ Provides three levels of load balancing: network-level, JMS connections, and distributed destinations.

1.5.2 Enterprise-Level Features