• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
Bartenders:
  • Mikalai Zaikin

is WebSphere MQ have a differ functionality as compare to simple JMS Queue?

 
Greenhorn
Posts: 2
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
is WebSphere MQ have a differ functionality than simple JMS Queue???
 
Greenhorn
Posts: 12
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Yes and no.

JMS is just a specification underneath which you need a transport provider. WMQ is one of many implementations of a JMS transport and in that sense it offers exactly the same functionality as s simple JMS queue (or topic).

But at the same time, WebSphere MQ offers considerable functionality that is not specific to JMS. For example, WebSphere MQ has the concept of a "retained publication." This functionality retained the last message to be published on a given topic so that newly subscribed applications do not need to wait for subsequent publications. There are many other examples of how WMQ provides a superset of JMS functionality but I don't want to stray too far off topic for this forum.

But the short answer is that yes, WMQ does offer different functionality than a simple JMS queue should you choose to use it. If you need some of the WMQ-native functionality and this does not violate a business requirement regarding JMS compatibility then by all means use it. If your requirement is for a JMS-compliant transport make sure to stick with the JMS API and functionality in which case you can treat WMQ as if it were a simple JMS queue.
 
reply
    Bookmark Topic Watch Topic
  • New Topic