JMS and Available Implementations

As of this writing, the JMS specification is at 1.0.2. A reference implementation (RI) of the Java Message Service API is not available as of yet. However, JavaSoft has promised that it will be part of the reference implementation for the Java 2 Platform, Enterprise Edition 1.3. There are a number if vendors offering JMS implementations or who have pledged support for JMS and the list of these vendors can be obtained at http://java.sun.com/products/jms/vendors.html.

When considering buying a JMS compatible server, it is important to decide whether you are interested in JMS itself, or whether you would like to deploy JMS messaging in the context of other J2EE technologies. J2EE-compatible application servers can deliver a whole host of functions, in addition to the capabilities offered by JMS. If JMS is one of the several items that you're looking for, you can look at a whole host of J2EE Application Server providers like Allaire's JRun, BEA System's WebLogic Gemstone, Oracle, Orion, etc.

However, if like most developers, you are in search of JMS solution providers specializing in JMS. you have a choice of a dedicated set of vendors that specialize in providing great JMS implementations.

Fiorano Software, Inc. (http://www.fiorano.com) was one of the earliest JMS vendors to enter the market. They provide three products as of this writing — the Fiorano MQ Message Server. Fiorano MQ InfoBus, and FioranoMQ Bridge. The FioranoMQ server was released in October 1998. FioranoMQ supports both Publish/Subscribe and Point-to-Point messaging domains and can be configured to support either of the topologies. It also supports selective filtering of incoming and outgoing messages and offers XML interoperability that converts JMS messages into external XML messages. They have a very simple and intuitive GUI front-end for their administrative console.

SoftWired (http://www.Softwired-inc.com), also one of the earlier JMS vendors, provides three producers: The iBus Message Bus which relies heavily on IP Multicast, the iBus Message Server, which is based on the traditional hub-and-spoke architecture and the iBus Mobile for wireless applications. The iBus Messaging server provides support for a variety of transport media in addition to TCP/IP and IP Multicast. These include support for protocols like SMS (Short Message Service) and WAP (Wireless Application Protocal.

The Spirit WAVEJMS framework from SpiritSoft, Inc. (http://www.spirit-soft.com) relies on IP multicast and broadcast technologies to efficiently deliver information to subscribers. It may be of interest to people in the financial industry, as it strongly integrates with traditional financial world middleware products like TIBCO Rendezvous, IBM MQSeries, and Talarian SmartSockets.

Progress Software (http://www.progress.com), is another JMS vendor. As of this writing, SoniqMQ supports both Publish/Subscribe and Point-to-Point messaging domains and can be configured to support either of these topologies. It also supports selective filtering of incoming messages and offers XML interoperability.

Sun released its Java Message Queue (JMQ), in November 1999. Sun however did not write its JMS Server from scratch. Modulus Technologies developed the underlying server. It is generating a lot of interest among Sun and Sun/Netscape Alliance customers.

Note 

Appendix A contains more details about some of the most popular JMS Providers available.