Java Message Service

Chapter 9. JMS Providers

This chapter provides an overview of the top six JMS providers today (IBM’s MQSeries, Progress’s SonicMQ , Fiorano’s FioranoMQ , Softwired’s iBus, Sun’s JMQ , BEA’s Weblogic), as well as one open source JMS provider (OpenJMS). It is important to note that not all enterprise messaging systems support JMS. Some of the largest MOM products still do not support JMS, namely Microsoft Message Queue (MSMQ) and Tibco. While the authors expect that Tibco will eventually support JMS, MSMQ is not expected to do so—Microsoft has never supported Java enterprise APIs.

Each product summary addresses the following five topics:

• Product history

• JMS version and operating systems supported

• Architecture (centralized or distributed) and administration tools

• Persistence mechanism and transactional support

• Security (firewall tunneling, authentication, access control)

We have attempted to provide the version number for each product we discussed. Since new releases of these products will have additional features, we have also included a section on features expected for new versions along with all the product summaries.

Note

The term “JMS-compliant” is used throughout this chapter to indicate which version of JMS specification each provider claims to implement. It is important to note that Sun does not have any compatibility tests for JMS at this time, so there is no standard for verifying vendor’s claims of compatibility.

Most vendors do not support two-phase commit. This is understandable, ...