Professional Documents
Culture Documents
Jms Final
Jms Final
Jms Final
JMS Details
JMS Clients
Java programs that send/receive messages
Messages
Administered Objects
preconfigured JMS objects created by an admin for the use of
clients
ConnectionFactory, Destination (queue or topic)
JMS Provider
messaging system that implements JMS and administrative
functionality
JMS Administration
Administrative Bind
Tool JNDI Namespace
Lookup
Publish-Subscribe (One-to-Many)
Receiver
Send (publish) message to a JMS Topic
Enables many readers (subscribers)
Sender
uses a “topic” to send and receive messages
Message
each message has multiple consumers
Topic
Subscriber Subscriber
Point-to-Point Messaging
Msg
Msg
consumes
Client1 Queue Client2
sends
acknowledges
Publish/Subscribe Messaging
subscribes
Msg Client2
delivers
Client1
publishes Topic subscribes
Client3
delivers
JMS API Programming Model
Connection
Factory
creates
Connection
Message Header
used for identifying and routing messages
contains vendor-specified values, but could also contain
application-specific data
typically name/value pairs
Message Properties (optional) Header
Message Body(optional) Properties
contains the data
five different message body types Body
in the JMS specification
Header
Identify message
Destination
Header Routing Information
Properties Priority
Timestamp
Body
Reply to
Message type
Properties
Added by the application
developer
Header Application specific
Properties properties
Key-value pairs
Body KEYWORD=VALUE
Extensions for messaging
systems
Body
Message body
Can contain arbitrary data
types
Header Text messages
Properties Map (key-value pairs)
XML
Body
Serialized objects (Java)
Binary data
Empty
JMS Message Types