O'Reilly - Java Message Service

Java Message Service
The most important new feature in Version 3.0 is SonicMQ's Dynamic Routing
Architecture (DRA), which is targeted at large-scale B2B infrastructures. DRA provides
fault-tolerant shared queues within a cluster, allowing parallel queue access, load
balancing and failover, and the ability to share queues across application domains.
An XML message type extends the TextMessage, allowing a message to be dealt with as
either straight text or as a DOM tree. Lazy parsing means the built-in XML parser is only
invoked if you ask for the message in DOM format.
SonicMQ provides support for HTTP firewall tunneling ans SSL. The HTTP tunneling
supports client-side proxy servers as well as server-side reverse-proxy servers. HTTP 1.1,
HTTP 1.0 Keep-Alive, and vanilla HTTP 1.0 connections are automatically negotiated at
connection time based on the best available protocol. Authentication is supported with
simple usernames and passwords; PKI server authentication using digital certificates is
also supported. Access control for administered objects is also provided. Using
hierarchical topic trees, ACLs may be administratively defined at any level of the topic
tree. Both positive and negative permissions may be granted for groups of users and
individual users. SonicMQ also includes a unique Message-level payload encryption.
Clustered message servers are configured through centralized management tools. Message
traffic is routed across geographically dispersed message servers using TCP, SSL, or
HTTP.
Automatic Flow Control allows for smooth delivery of messages under heavy load. There
are also client APIs for C/C++ and ActiveX/COM+ for integration with non-Java systems.
Also available is a multiclient performance and scalability test harness, which allows you
to do your own vendor-to-vendor comparisons. Currently SonicMQ is the only JMS
vendor offering a performance comparison tool that scales beyond a handful of clients.
9.2.2 Next Version
The next version will include the JMS XA interfaces and two-phase commit, and a new
deployment option based on an IP multicast architecture. In addition, the next version of
SonicMQ will include support for the EJB message-driven bean discussed in Chapter 8. As
always, each new version will include continued performance and scalability
enhancements.
9.3 Fiorano: FioranoMQ
Fiorano's product was originally the Fiorano Middleware Platform. It was completely
rewritten in Java and renamed FioranoMQ, which first shipped in 1998. Fiorano now
offers two different JMS products: FioranoMQ Multicast and FioranoMQ Enterprise.
9.3.1 FioranoMQ Multicast 4.5
FioranoMQ Multicast is compliant with JMS 1.0.2 and supports the pub/sub JMS
messaging model. The server and clients are written in Java and therefore run on any
platform with a JDK 1.1 or higher Virtual Machine.
135