background image

JMS API Architecture

<< Basic JMS API Concepts | Messaging Domains >>
<< Basic JMS API Concepts | Messaging Domains >>

JMS API Architecture

The next section introduces the JMS API programming model. Later sections cover more
advanced concepts, including the ones you need to write Java EE applications that use
message-driven beans.
JMS API Architecture
A JMS application is composed of the following parts.
A JMS provider is a messaging system that implements the JMS interfaces and provides
administrative and control features. An implementation of the Java EE platform includes a
JMS provider.
JMS clients are the programs or components, written in the Java programming language,
that produce and consume messages. Any Java EE application component can act as a JMS
client.
Messages are the objects that communicate information between JMS clients.
Administered objects are preconfigured JMS objects created by an administrator for the use
of clients. The two kinds of JMS administered objects are destinations and connection
factories, which are described in
"JMS Administered Objects" on page 901
.
Figure 31­2
illustrates the way these parts interact. Administrative tools allow you to bind
destinations and connection factories into a JNDI namespace. A JMS client can then use
resource injection to access the administered objects in the namespace and then establish a
logical connection to the same objects through the JMS provider.
Basic JMS API Concepts
Chapter 31 · The Java Message Service API
897