Mule MQ

Mule MQ is an enterprise-class Java Message Service (JMS) implementation that guarantees message delivery across public, private, and wireless infrastructures without the use of a web server or modifications to firewall policy. Mule MQ provides developers with a reliable, scalable, and high-performance infrastructure for delivering information among applications for the enterprise and the web. In addition, Mule MQ makes it easy for administrators to monitor, manage, and secure that mission-critical data.

Mule MQ includes topic (publish/subscribe) and queue functionality that is fully compliant with the JMS 1.1 specification. It can be used as a standalone JMS server or embedded in a web server or servlet engine (e.g., Tcat Server). Mule MQ also includes a powerful and intuitive management console. Administrators can use the console to capture extremely granular metrics, manage message delivery, and audit information from multiple Mule MQ realms.

For information about the latest release, see the Release Notes.

Mule MQ Architecture

The Mule MQ architecture has both server- and client-side components. On the server side, Mule MQ provides the realm server, which maintains all the data and information related to queues and topics. The realm server is a heavily optimized Java process capable of delivering high throughput of data to large numbers of clients while ensuring latencies are kept to a minimum. The realm server functionality includes scheduling and triggers, plugins, federation, clustering, and low latency IO.

On the client side, Mule MQ provides two clients: a messaging client and a management client. The messaging client supports synchronous and asynchronous messaging via queues and publish/subscribe message models. The management client can construct resources (such as channels for publish/subscribe messaging and queues). The management client can also query management data (such as throughput, cluster state, and numbers of connections) directly from the realm server. You can access the functionality of both of these clients via the public Mule MQ Java APIs.

Both client components were developed using open protocols with specific attention paid to performance and external deployment. Furthermore, each client was specifically designed to transparently pass through firewalls and other security infrastructure while providing its own inherent security features.

Getting Started

The following documentation provides information on using Mule MQ:

• Installation Guide
• Integrating with Mule ESB
• Administrators Guide
• Developers Guide
• Performance Test
• FAQ