The Java Platform, Enterprise Edition (Java EE) is a specification for a standard server platform hosting multi-tier, distributed enterprise applications. One of the requirements of Java EE is that distributed components be able to interact through reliable, asynchronous messaging. This interaction is enabled through the use of a JMS provider. In fact, Message Queue is the reference JMS implementation for Java EE.
This chapter explores the ramifications of implementing JMS support in a Java EE platform environment. The chapter covers the following topics:
For additional information about using Message Queue as a JMS provider for Java EE compliant application servers, see Chapter 19, JMS Resource Adapter Property Reference, in Sun Java System Message Queue 4.3 Administration Guide.
In addition to the general JMS client programming model introduced in Chapter 2, Client Programming Model, there is a more specialized adaptation of a JMS client used in the context of Java EE platform applications. This specialized client is called a message-driven bean and is one of a family of Enterprise JavaBeans (EJB) components described in the EJB 2.0 (and later) Specification (http://java.sun.com/products/ejb/docs.html).
Message-driven beans provide asynchronous messaging; other EJB components (session beans and entity beans) can only be called synchronously, through standard EJB interfaces. However, enterprise applications often need asynchronous messaging, to allow server-side components to communicate without tying up server resources. Any application whose server-side components must respond to application events needs an EJB component that can receive and consume messages without being tightly coupled to the message producer. In enterprise applications, this capability must also scale under increasing load.
An MDB implements the JMS MessageListener interface. The onMessage method (written by the MDB developer) is invoked when the MDB container receives a message. The onMessage() method consumes the message, just as the onMessage() method of a standard MessageListener object would. (You do not remotely invoke methods on MDBs as you do on other EJB components: therefore there are no home or remote interfaces associated with them.) Each MDB can consume messages from only a single destination. The messages can be produced by standalone JMS applications, JMS components, or EJB components, as shown in the following figure.
A specialized EJB container supports the MDB. This MDB container creates instances of the MDB and sets them up for asynchronous consumption of messages. The container sets up a connection with the broker (including authentication), creates a pool of sessions associated with a given destination, and manages the distribution of messages among the pooled sessions. Since the container controls the life cycle of MDB instances, it manages the pool of MDB instances to accommodate incoming message loads.
Associated with each MDB is a deployment descriptor that specifies the connection factory attributes and destination properties that the container uses in setting up message consumption. The deployment descriptor can also include other information needed by deployment tools to configure the container. Each such container supports all instances of a single MDB.
In Java EE architecture, EJB containers are provided by Java EE application servers. An application server supports these containers by providing resources they need, such as transaction managers, persistence managers, name services, and, in the case of messaging and MDBs, a JMS provider.
For information about Java EE architecture, see the Java EE Platform Specification located at http://java.sun.com/javaee/downloads/index.jsp.
Java EE also provides a standardized way of plugging in external resources needed by an application server. The standard, defined by the Java EE Connector Architecture (J2EECA) 1.5 specification, allows an application server to interact with external systems by way of a resource adapter. External systems can include, among others, JMS messaging systems, as implemented by a JMS provider.
Plugging a JMS resource adapter into an application server allows Java EE components deployed and running in the application server to exchange JMS messages. The JMS connection factory and destination administered objects needed by these components can be created and configured using Java EE application server administration tools.
Other administrative operations, however, such as managing a broker and physical destinations, are not included in the J2EECA specification and can be performed only through provider-specific tools.
Message Queue includes a JMS resource adapter that consists of a single file (imqjmsra.rar) located in a directory that depends on the operating system (see Chapter 19, JMS Resource Adapter Property Reference, in Sun Java System Message Queue 4.3 Administration Guide). The imqjmsra.rar file contains the JAR files needed by the application server to support JMS messaging, as well as the resource adapter deployment descriptor (ra.xml) used to deploy the resource adapter in a Java EE application server.
You can deploy the Message Queue resource adapter in Java EE-1.4-compliant application servers by following the resource adapter deployment and configuration instructions provided by each application server.
In the case of the Sun Java System Application Server, however, Message Queue is already integrated, by default, as the application server's native JMS provider. Hence, no deployment of the Message Queue resource adapter is required.