1-2 Programming JMS for Oracle WebLogic Server
■
Chapter 4, Enhanced Support for Using WebLogic JMS with EJBs and Servlets, describes best practice methods that make it easier to use WebLogic JMS in
conjunction with Java EE components, like Enterprise Java Beans and Servlets.
■
Chapter 5, Developing a Basic JMS Application, describes how to develop a
WebLogic JMS application.
■
Chapter 6, Managing Your Applications, describes how to programmatically
manage your JMS applications using value-added WebLogic JMS features.
■
Chapter 7, Using JMS Module Helper to Manage Applications, describes how to
programatically create and manage JMS servers, Store-and-Forward Agents, and JMS system resources.
■
Chapter 8, Using Multicasting with WebLogic JMS, describes how to use
Multicasting to enable the delivery of messages to a select group of hosts that subsequently forward the messages to subscribers.
■
Chapter 9, Using Distributed Destinations, describes how to use distributed
destinations with WebLogic JMS.
■
Chapter 10, Using Message Unit-of-Order, describes how to use Message
Unit-of-Order to provide strict message ordering when using WebLogic JMS queues.
■
Chapter 11, Using Unit-of-Work Message Groups, describes how to use
Unit-of-Work Message Groups to provide groups of messages when using WebLogic JMS.
■
Chapter 12, Using Transactions with WebLogic JMS, describes how to use
transactions with WebLogic JMS.
■
Chapter 13, Developing Advanced PubSub Applications, describes the
advanced concepts and functionality of Uniform Distributed Topics UDTs necessary to design high availability applications.
■
Chapter 14, Recovering from a Server Failure, describes how to terminate a JMS
application gracefully if a server fails and how to migrate JMS data after server failure.
■
Chapter 15, WebLogic JMS C API, provides information on how to develop C
programs that interoperate with WebLogic JMS.
■
Appendix A, Deprecated WebLogic JMS Features, describes features that have
been deprecated for this release of WebLogic Server.
■
Appendix B, FAQs: Integrating Remote JMS Providers, provides answers to
frequently asked questions about how to integrate WebLogic Server with remote JMS providers.
■
Appendix C, How to Lookup a Destination, provides a summary of methods
you can use to lookup a destination.
■
Appendix D, Advanced Programming with Distributed Destinations Using the JMS Destination Availability Helper API,
provides a means for getting notifications when destinations become available or unavailable.
1.3 Related Documentation
This document contains JMS-specific design and development information. For comprehensive guidelines for developing, deploying, and monitoring WebLogic
Server applications, see the following documents:
Introduction and Roadmap 1-3
■
Configuring and Managing JMS for Oracle WebLogic Server for information about configuring and managing JMS resources.
■
Configuring and Managing Store-and-Forward for Oracle WebLogic Server for information about the benefits and usage of the Store-and-Forward service with
WebLogic JMS.
■
Using the WebLogic Persistent Store for information about the benefits and usage of the system-wide WebLogic Persistent Store.
■
Deploying Applications to Oracle WebLogic Server is the primary source of information about deploying WebLogic Server applications.
1.4 Samples and Tutorials for the JMS Developer
In addition to this document, Oracle provides a variety of code samples and tutorials for JMS developers. The examples and tutorials illustrate WebLogic Server JMS in
action, and provide practical instructions on how to perform key JMS development tasks.
Oracle recommends that you run some or all of the JMS examples before developing your own JMS applications.
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 provides a framework for 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.
MedRec includes a service tier comprised primarily of Enterprise Java Beans EJBs that work together to process requests from web applications, web services, and
workflow applications, and future client applications. The application includes message-driven, stateless session, stateful session, and entity EJBs.
1.5 New and Changed JMS Features In This Release
This release includes the following new and changed features:
■
Weighted Distributed Destinations are deprecated in WebLogic Server 10.3.4.0. Oracle recommends using Uniform Distributed Destinations.
■
Advanced WebLogic JMS publish and subscribe pubsub concepts and functionality of Uniform Distributed Topics UDTs necessary to design high
availability applications. See Section 13, Developing Advanced PubSub
Applications.
■
The JMSDestinationAvailabilityHelper API provides a means for getting notifications when destinations become available or unavailable. These APIs are
for advanced use cases only. Use this helper only when standard approaches for solving WebLogic distributed consumer problems have been exhausted. See
1-4 Programming JMS for Oracle WebLogic Server
Using the JMS Destination Availability Helper APIs with Distributed Queues in Programming JMS for Oracle WebLogic Server.
For a comprehensive listing of the new WebLogic Server features introduced in this release, see What’s New in Oracle WebLogic Server.
2
Understanding WebLogic JMS 2-1
2
Understanding WebLogic JMS
These sections briefly review the different Java Message Service JMS concepts and features, and describe how they work with other application objects and WebLogic
Server.
It is assumed the reader is familiar with Java programming and JMS 1.1 concepts and features.
■
Section 2.1, Overview of the Java Message Service and WebLogic JMS
