Elements of a JMS application
This topic contains the different elements of a JMS messaging system.
A JMS application is composed of the following parts:
- JMS client
- An application or process that produces messages, consumes messages or both.
- Administered objects
- Preconfigured JMS objects created by an administrator for the
use of clients. The two kinds of JMS administered objects are destinations
and connection factories.
- Destination
- The object a client uses to specify the target of messages it
produces and the source of messages it consumes. The Destination implementation
in the Eclipse Amlen JMS
client implements two destination interfaces:
- Topic
- Queue
- Connection factory
- An object that a JMS client uses to create a connection with a
JMS provider. The ConnectionFactory implementation in the Eclipse Amlen JMS client implements
the three connection factory interfaces:
- ConnectionFactory
- TopicConnectionFactory
- QueueConnectionFactory
- Message
- An object that contains the data being transferred between JMS clients.
- Message producer
- A JMS client that creates and sends messages.
- Message consumer
- A JMS client that receives messages.
Important: The function
of queues is not implemented within the JMS client for the Beta release.