Using OpenMQ
           Linda Schneider
           Technical Lead
           Sun Microsystems,
           Inc.
What will be covered ?
An introduction to OpenMQ.
A Customer example.
Basic customer requirements.
Building part of the in...
What is OpenMQ ?



                                                        [3]
 Copyright Sun Microsystems Inc. All Right...
Overview
Allows heterogenous applications to reliability and
asynchronously pass data between each other.
Open Source Java...
Tell Me More
Developer and User discussion forums
Stable builds with product releases
Early access, promoted builds availa...
Using OpenMQ ?



                                                       [6]
Copyright Sun Microsystems Inc. All Rights Re...
An example
To mimic problems faced in designing applications, an
example:
Represents a complex system with loosely connect...
Our Example: Santa Claus, Inc
Why, you ask ?

Even if you don't believe in Santa Claus, you must still
understand that del...
Overall System Requirements
Santa Claus, Inc. software applications need do the
following:
Handle gift selection and deliv...
What are we doing:
Focusing on handling christmas gift processing
Steps to design it include:
Determining the high level o...
Defining the High Level
Operation of the System


                                                           [11]
    Copy...
What do we need to do ?




                                                              [12]
       Copyright Sun Micros...
What do we need to do ? (cont.)




                                                              [13]
       Copyright Su...
What are the destinations ?



                                                            [14]
     Copyright Sun Microsy...
The Child Queue




                                                              [15]
       Copyright Sun Microsystems I...
The Naughty/Nice Queues




                                                             [16]
      Copyright Sun Microsys...
The Wrap Queue




                                                             [17]
      Copyright Sun Microsystems Inc....
The Stuff to Pack Queue




                                                              [18]
       Copyright Sun Micros...
Select-a-gift Queues




                                                              [19]
       Copyright Sun Microsyst...
Topic LogChild




                                                              [20]
       Copyright Sun Microsystems In...
A quick overview to design
         patterns


                                                            [21]
     Copyr...
Some basic design patterns:
Pattern                    Description
                           Message is sent to another a...
More things to think about:
Use persistent messages if it can not afford to be lost
Use non-persistent messages for:
   no...
Processing Queue Child
Conduit: many producers to one queue
Persistent: would be time consuming to lose message




      ...
Processing Naughty and Nice
Step Pattern: one step of it
Naughty Queue: Non-Persistent
   its OK if a child who is bad
   ...
Processing Nice
Step Pattern: more steps of it
Multiple resources so XA




                                              ...
Processing Nice (Select a gift)
Request/Reply Pattern
Non-persistent
Action repeated on failure




                      ...
The Wrap Queue
Step operation
Persistent: end of an expensive set of steps that they
don't want to repeat




            ...
The Log Child Topic
Broadcast Pattern
Persistent because santa wants his database accurate




                           ...
In this example:
The batch pattern was not used
   Santa does use It for processing HR updates for the elves
The time sens...
Performance Requirements
22 billion kids
364 days for preparation (since christmas is taken)
   31,526,000 seconds
70 chil...
Performance Requirements (cont)
Naughty Kids use
  1 Persistent queue (child)
  1 Non-persistent queue (naughty)
  1 Persi...
The cold hard requirements
Messages:
  Child: 100 msgs/second (persistent)
  Naughty: 40 msgs/second (non-persistent)
  Lo...
Some Sample Code



                                                        [34]
 Copyright Sun Microsystems Inc. All Righ...
Sending the “Child” message
public void doPost(HttpServletRequest request,
  HttpServletResponse response)       throws Se...
Processing the “nice” queue
public void onMessage(Message inMessage) {
    TextMessage msg = null;
    try {
        //Mes...
Processing the “nice” queue (step 2)
public String getListItem(String childid)
          throws Exception {
     QueueConn...
Processing the “nice” queue (step 3)
public String pack(String item, String child_id)
    throws JMSException
{
    QueueC...
You'll need to fill in the rest



                                                             [39]
      Copyright Sun M...
More Information



                                                       [40]
Copyright Sun Microsystems Inc. All Rights...
OpenMQ -- More Information
Visit the product webpage
http://sun.com/software/products/message_queue
Join the Open Message ...
Related Information
Java Composite Application Platform Suite
http://sun.com/software/javaenterprisesystem/javacaps/
Java ...
Thank You!


Using OpenMQ
Linda Schneider
linda.schneider@sun.com
Upcoming SlideShare
Loading in …5
×

Building With Open MQ

3,647 views

Published on

Overview of OpenMQ 4.3, including the new Universal API.

Published in: Technology
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
3,647
On SlideShare
0
From Embeds
0
Number of Embeds
22
Actions
Shares
0
Downloads
83
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Building With Open MQ

  1. 1. Using OpenMQ Linda Schneider Technical Lead Sun Microsystems, Inc.
  2. 2. What will be covered ? An introduction to OpenMQ. A Customer example. Basic customer requirements. Building part of the infrastructure. Warnings: No in depth coverage Assumes basic JMS knowledge [2] Copyright Sun Microsystems Inc. All Rights Reserved.
  3. 3. What is OpenMQ ? [3] Copyright Sun Microsystems Inc. All Rights Reserved.
  4. 4. Overview Allows heterogenous applications to reliability and asynchronously pass data between each other. Open Source Java Message Service (JMS) implementation (+ additions) Default Messaging Provider for Glassfish Useful on its own for standalone JMS applications Enterprise level quality (>8 years in development) Open Source since JavaOne 2006 Available as a supported product: Sun Java System Message Queue (SJSMQ) [4] Copyright Sun Microsystems Inc. All Rights Reserved.
  5. 5. Tell Me More Developer and User discussion forums Stable builds with product releases Early access, promoted builds available New features, and fixes Dual license support (GPL v2 and CDDL) Open source version of Java MQ is available from http://mq.dev.java.net [5] Copyright Sun Microsystems Inc. All Rights Reserved.
  6. 6. Using OpenMQ ? [6] Copyright Sun Microsystems Inc. All Rights Reserved.
  7. 7. An example To mimic problems faced in designing applications, an example: Represents a complex system with loosely connected applications Utilizes various types of messaging Is easy to understand Is at least minimally interesting [7] Copyright Sun Microsystems Inc. All Rights Reserved.
  8. 8. Our Example: Santa Claus, Inc Why, you ask ? Even if you don't believe in Santa Claus, you must still understand that delivering all those presents would be a daunting task And while its not Christmas which comes but once a year, but requires year round planning and preparation. Just because Santa Claus lives at the North Pole, doesn't imply he can't use technology [8] Copyright Sun Microsystems Inc. All Rights Reserved.
  9. 9. Overall System Requirements Santa Claus, Inc. software applications need do the following: Handle gift selection and delivery Manage resources e.g. gifts reindeer Elves Track general status information how many days before Christmas etc. [9] Copyright Sun Microsystems Inc. All Rights Reserved.
  10. 10. What are we doing: Focusing on handling christmas gift processing Steps to design it include: Determining the high level operation Coming up with the name and type of destinations Determining models used for the messaging Determining load characteristics Looking at code for some components [10] Copyright Sun Microsystems Inc. All Rights Reserved.
  11. 11. Defining the High Level Operation of the System [11] Copyright Sun Microsystems Inc. All Rights Reserved.
  12. 12. What do we need to do ? [12] Copyright Sun Microsystems Inc. All Rights Reserved.
  13. 13. What do we need to do ? (cont.) [13] Copyright Sun Microsystems Inc. All Rights Reserved.
  14. 14. What are the destinations ? [14] Copyright Sun Microsystems Inc. All Rights Reserved.
  15. 15. The Child Queue [15] Copyright Sun Microsystems Inc. All Rights Reserved.
  16. 16. The Naughty/Nice Queues [16] Copyright Sun Microsystems Inc. All Rights Reserved.
  17. 17. The Wrap Queue [17] Copyright Sun Microsystems Inc. All Rights Reserved.
  18. 18. The Stuff to Pack Queue [18] Copyright Sun Microsystems Inc. All Rights Reserved.
  19. 19. Select-a-gift Queues [19] Copyright Sun Microsystems Inc. All Rights Reserved.
  20. 20. Topic LogChild [20] Copyright Sun Microsystems Inc. All Rights Reserved.
  21. 21. A quick overview to design patterns [21] Copyright Sun Microsystems Inc. All Rights Reserved.
  22. 22. Some basic design patterns: Pattern Description Message is sent to another application who  Request/Reply sends back a response Messages go through several iterations, the  message is persisted at key points where  Step Operations processing it again would be expensive Broadcast One message goes to many consumers Multiple consumers send messages to a single  Conduit destination Batch Messages are processed in a chunk Messages must be processed within a short  period of time (e.g. under an hour) and can not  Time Critical/Sensitive be lost [22] Copyright Sun Microsystems Inc. All Rights Reserved.
  23. 23. More things to think about: Use persistent messages if it can not afford to be lost Use non-persistent messages for: non-critical step messages (when it can be repeated) Request/Reply Anytime a message can be lost on a server crash Use durables for Topics when it may need to be retrieved later Use normal or XA transactions when multiple things must process together: XA if it includes other resources like databases [23] Copyright Sun Microsystems Inc. All Rights Reserved.
  24. 24. Processing Queue Child Conduit: many producers to one queue Persistent: would be time consuming to lose message [24] Copyright Sun Microsystems Inc. All Rights Reserved.
  25. 25. Processing Naughty and Nice Step Pattern: one step of it Naughty Queue: Non-Persistent its OK if a child who is bad misses their coal Nice Queue: Persistent. They must get their present. [25] Copyright Sun Microsystems Inc. All Rights Reserved.
  26. 26. Processing Nice Step Pattern: more steps of it Multiple resources so XA [26] Copyright Sun Microsystems Inc. All Rights Reserved.
  27. 27. Processing Nice (Select a gift) Request/Reply Pattern Non-persistent Action repeated on failure [27] Copyright Sun Microsystems Inc. All Rights Reserved.
  28. 28. The Wrap Queue Step operation Persistent: end of an expensive set of steps that they don't want to repeat [28] Copyright Sun Microsystems Inc. All Rights Reserved.
  29. 29. The Log Child Topic Broadcast Pattern Persistent because santa wants his database accurate [29] Copyright Sun Microsystems Inc. All Rights Reserved.
  30. 30. In this example: The batch pattern was not used Santa does use It for processing HR updates for the elves The time sensitive/critical data pattern was not used: Santa does use it during present delivery on christmas eve to track where he is Because he has no time sensitive/critical data, reliability is important however data availability isn't [30] Copyright Sun Microsystems Inc. All Rights Reserved.
  31. 31. Performance Requirements 22 billion kids 364 days for preparation (since christmas is taken) 31,526,000 seconds 70 children/second must be processed Assume 60% are “nice” Assume 40% downtime to cover outages and normal processing (so goal is approx 100 kids/second) [31] Copyright Sun Microsystems Inc. All Rights Reserved.
  32. 32. Performance Requirements (cont) Naughty Kids use 1 Persistent queue (child) 1 Non-persistent queue (naughty) 1 Persistent Topic (log child) Nice Kids Use: Persistent Queue (child) Persistent Queue (nice) 2 Non-Persistent Queues (Inventory request and reply queues) Non-persistent queue (Wrap) 1 Persistent Topic (log child) [32] Copyright Sun Microsystems Inc. All Rights Reserved.
  33. 33. The cold hard requirements Messages: Child: 100 msgs/second (persistent) Naughty: 40 msgs/second (non-persistent) Log Child: 100msgs/second (persistent) Nice: 60 msgs/second (persistent in XA transaction) Inventory request/reply: 60 msgs/second *2 (non- persistent) Wrap: 60 msgs/second (persistent) TOTALS: Persistent: 380 msgs/second Non-persistent: 160 msgs/second [33] Copyright Sun Microsystems Inc. All Rights Reserved.
  34. 34. Some Sample Code [34] Copyright Sun Microsystems Inc. All Rights Reserved.
  35. 35. Sending the “Child” message public void doPost(HttpServletRequest request, HttpServletResponse response) throws ServletException, IOException { // retrieve initial context (ic) QueueConnectionFactory qcf = (QueueConnectionFactory) ic.lookup(quot;MyConnectionFactoryquot;); Queue destQueue = (Queue)ic.lookup(quot;Childquot;); QueueConnection connection = qcf.createQueueConnection(); try { QueueSession session = connection.createQueueSession( False, Session.AUTO_ACKNOWLEDGE); QueueSender sender = session.createSender(destQueue); MapMessage msg = session.createMapMessage(); // Set each item msg.setString(“firstname”, request.getParameter(“firstname”)); // … retrieve other properties … ; sender.send(msg); } finally { connection.close(); } } [35] Copyright Sun Microsystems Inc. All Rights Reserved.
  36. 36. Processing the “nice” queue public void onMessage(Message inMessage) { TextMessage msg = null; try { //Message is of type text and has a unique child id msg = (TextMessage) inMessage; String id = msg.getText(); String[] list = db.getList(id); // makes SQL call String item = null; if (list == null) { // no list, send request String item = getListItem(); //next slide } else { item = list[0]; } //update inventory db.updateInventory(item, id);//makes SQL call // put on packing list pack(item, id); } catch (Exception e) { // things went wrong roll back mdc.setRollbackOnly(); } } [36] Copyright Sun Microsystems Inc. All Rights Reserved.
  37. 37. Processing the “nice” queue (step 2) public String getListItem(String childid) throws Exception { QueueConnectionFactory factory = jndiContext.lookup(“MyQueueFactory”); QueueConnection qc = factory.createQueueConnection(); qc.start(); QueueSession session = qc.createSession(true, Session.AUTO_ACKNOWLEDGED); Queue q = session.createQueue(“RandomPresent”); Queue reply = session.createTemporaryQueue(); // get sender and receiver QueueSender sender = session.createSender(q); QueueReceiver receiver = session.createReceiver(q); //send message and wait TextMessage m = session.createTextMessage(childid); m.setJMSReplyTo(reply); //send the message sender.send(m); TextMessage back = (TextMessage) receiver.receive(60*1000); // wait a minute if (back == null) { didn't get anything throw new Exception(“Nothing”); return back.getText(); [37] } Copyright Sun Microsystems Inc. All Rights Reserved.
  38. 38. Processing the “nice” queue (step 3) public String pack(String item, String child_id) throws JMSException { QueueConnectionFactory factory = jndiContext.lookup(“MyQueueFactory”); QueueConnection qc = factory.createQueueConnection(); QueueSession session = qc.createSession(true, Session.AUTO_ACKNOWLEDGED);); Queue q = session.createQueue(“Pack”); // get sender QueueSender sender = session.createSender(q); //send message MapMessage m = session.createMapMessage(childid); m.setString(“child_id”, child_id); m.setString(“present”, item); sender.send(m); } [38] Copyright Sun Microsystems Inc. All Rights Reserved.
  39. 39. You'll need to fill in the rest [39] Copyright Sun Microsystems Inc. All Rights Reserved.
  40. 40. More Information [40] Copyright Sun Microsystems Inc. All Rights Reserved.
  41. 41. OpenMQ -- More Information Visit the product webpage http://sun.com/software/products/message_queue Join the Open Message Queue project https://mq.dev.java.net Browse the product documentation http://docs.sun.com/app/docs/coll/1307.3 Take the free technical training http://www.sun.com/training/catalog/courses/WMT-SMQ-1491.xml [41] Copyright Sun Microsystems Inc. All Rights Reserved.
  42. 42. Related Information Java Composite Application Platform Suite http://sun.com/software/javaenterprisesystem/javacaps/ Java System Identity Manager http://sun.com/software/products/identity Project GlassFish https://glassfish.dev.java.net/ The Aquarium, A community forum http://blogs.sun.com/theaquarium/ [42] Copyright Sun Microsystems Inc. All Rights Reserved.
  43. 43. Thank You! Using OpenMQ Linda Schneider linda.schneider@sun.com

×