JMS-Java Message Service
Download as PPTX, PDF1 like1,917 views
This document provides an overview of Java Message Service (JMS) including its goals, benefits, components, messaging models, and how it compares to Java Mail. JMS is a messaging standard that allows applications to communicate asynchronously via messages. It supports two messaging models: point-to-point messaging using queues and publish-subscribe using topics. The document also discusses Spring JMS, which provides a simplified API for JMS, and demonstrates sending and receiving messages using both pure JMS and Spring JMS.
JMS-Java Message Service
- 1. hSenid Lanka: Java Message Service By Kasun Dinesh Madusanke JMS (Java Message Service)
- 2. hSenid Lanka: JMS 2 Topics o Message and Messaging o What is JMS? o Goals of JMS o Benefits of JMS o When to use JMS? o JMS Message
- 3. 3 Topics Cont. o Java Mail vs JMS o JMS Components o JMS Application o MOM Service Providers o Messaging Models o JMS API Programming Model hSenid Lanka: JMS
- 4. 4 Topics Cont. o Demo-JMS Pure Java o Spring JMS o JMSTemplate o Demo-Spring JMS o Summary hSenid Lanka: JMS
- 5. 5 Message & Messaging ▸Bytes of data that is meaningful between the applications which use it. ▸Used to transfer information form one application to others. hSenid Lanka: JMS Message ▸Communication between system components or different applications. Messaging
- 6. 6 What is JMS? ▸JMS is a Message Oriented Middleware (MOM) ▸Published and maintained by Sun Microsystems ▸First published in August 1998 ▸Loosely coupled communication ▸Asynchronous messaging ▸Reliable delivery hSenid Lanka: JMS
- 7. 7 What is JMS? Cont. hSenid Lanka: JMS
- 8. 8 Goals of JMS ▸Minimizes the set of concepts a programmer must learn to use messaging products (programmer friendly). ▸Provides enough features to support sophisticated messaging applications. ▸Maximize the portability of JMS applications across JMS providers in the same messaging domain. hSenid Lanka: JMS
- 9. 9 When to use JMS? ▸The provider wants the components not to depend on information about other components' interfaces, so that components can be easily replaced. ▸The provider wants the application to run whether or not all components are up and running simultaneously. ▸The application business model allows a component to send information to another and to continue to operate without receiving an immediate response. hSenid Lanka: JMS
- 10. 10 JMS Message hSenid Lanka: JMS Header Properties Body This image shows the Structure of a JMS Message
- 11. 11 hSenid Lanka: JMS Header Properties Body Identify message Added by the application developer Message body Destination Application specific properties Can contain arbitrary data types Eg: Text messages Map (key-value pairs) XML Serialized objects (Java) Binary data Empty Routing Information Key-value pairs Priority Extensions for messaging systems Timestamp Message type Header, Properties and Body
- 12. 12 Java Mail vs JMS hSenid Lanka: JMS Java Mail JMS API for sending emails (eg: with attachments). Capable of exchanging messages between applications. Mainly for human information exchange Application/Human to Application/Human Messaging. Delivery can be duplicated. More like a database. Messages removed once it reads by the recipient system. Delivery not guaranteed. Delivery is guaranteed (Above reason). Designed for connectivity on the web. Bunch of different qualities of service (durable vs non-durable, queue vs topic).
- 13. 13 JMS Components ▸JMS Provider: ▹ The messaging system (MOM) that implements JMS. ▸JMS Clients ▹ Java applications that produce/receive messages. ▸JMS Producer/Publisher ▹ A JMS client that creates and sends messages. ▸JMS Consumer/Subscriber ▹ A JMS client that receives messages. ▸JMS Application ▹ The system composed of JMS clients and a JMS provider. hSenid Lanka: JMS
- 14. 14 JMS Application hSenid Lanka: JMS
- 15. 15 MOM Service Providers hSenid Lanka: JMS Service provider Product Company Weblogic Oracle MQSeries IBM JBOSSMQ JBOSS SoniqMQ Progress TIBCO EMS TIBCO ActiveMQ Apache
- 17. 17 Messaging Models Cont. ▸Point to Point ▹ Message queues, senders and receivers. ▹ Message is sent to a queue. ▹ Each message has only one consumer. ▹ Queue may be configured to persist messages. ▸Publish-Subscribe ▹ Publishers, subscribers, topics. ▹ Message may have multiple consumers, or no consumer at all. ▹ Each message is delivered to every client subscribed to a topic. hSenid Lanka: JMS
- 18. 18 Messaging Models Cont. hSenid Lanka: JMS ▸Point to Point
- 19. 19 Messaging Models Cont. hSenid Lanka: JMS ▸Publish-Subscribe
- 20. 20 Messaging Models Cont. hSenid Lanka: JMS PTP vs PUB/SUB Point to Point Publish-Subscribe Each message has only one consumer. Each message can have multiple consumers. Messages first sent to a destination called Queue. Messages first sent to a destination called Topic. A sender and receiver of a message have no timing dependencies (receiver can fetch the message later). Publishers and subscribers have a timing dependency (client need to be subscribed and active). The receiver acknowledges the successful processing of a message. Does not provide acknowledgement.
- 21. 21 JMS API Programming Model hSenid Lanka: JMS
- 22. 22 JMS API Programming Model Cont. hSenid Lanka: JMS ▸Connection Factory ▹ The client uses an object which is a connection factory used to create a connection to a provider. ▹ It creates connection between JMS Provider and JMS Client. ▸Connection ▹ A JMS connection encapsulates a virtual connection with a JMS provider. ▹ it is an open TCP/IP socket between a client and a provider service daemon.
- 23. 23 JMS API Programming Model Cont. hSenid Lanka: JMS ▸Session ▹ The session is a single threaded context which is used for producing and consuming messages. ▹ The sessions are used to create the following: ▹ Message Producers ▹ Message Consumers
- 24. 24 JMS API Programming Model Cont. hSenid Lanka: JMS ▸Message Producer ▹ A JMS message producer object is created by a session. ▹ It is used for sending messages to a destination. ▸Message Consumer ▹ A JMS message consumer object is created by session. ▹ It helps for receiving messages sent to a destination.
- 25. 25 DEMO (JMS Pure Java) hSenid Lanka: JMS Download project files
- 26. 26 Spring JMS hSenid Lanka: JMS ▸Advantages ▹ No EJB container required (no JEE container) ▹ Simplified resource management ▹ Connection Factory, Connections, Destinations ▹ Simplified concurrency management ▹ Simplified transaction management
- 27. 27 Spring JMS Cont. hSenid Lanka: JMS ▸JMS Template ▹ Send and receive messages synchronously ▸Message Listener Container ▹ Receive messages asynchronously ▹ Message-Driven POJOs (MDPs)
- 28. 28 JMSTemplate hSenid Lanka: JMS Method Description browse() Browse messages in a queue convertAndSend() Send messages synchronously Convert a Java object to a JMS message execute() Provides access to callbacks for more complex scenarios receive() receiveAndConvert() Receive messages synchronously receiveSelected() receiveSelectedAndConvert() Receive filtered messages synchronously send() Send a message synchronously using a MessageCreator
- 29. 29 hSenid Lanka: JMS DEMO (Spring JMS) Download project files
- 30. 30hSenid Lanka: Java Message Service By Kasun Dinesh Madusanke THANK YOU!