Message Broker Features

WSO2 Message Broker brings messaging and eventing capabilities to your SOA framework. It is based on JMS (Java Message Service), and its features are basically implementations of the JMS specification, so any JMS client can communicate with WSO2 Message Broker. It can be used as a standalone message broker or a distributed message brokering system.

WSO2 Message Broker has the following key features. For the relevant versions of the applications used as features, see Compatibility of WSO2 Products.

Feature	Description
JMS Message Queuing	Publish and receive messages with: FIFO order Message durability Ability to handle large messages Ability to specify maximum delivery attempts Failover available with clustered setup In-memory mode available with standalone setup
JMS Message Pub/Sub	Use topics to subscribe to messages.
WS-Eventing	WSO2 Message Broker is compliant with the latest WS-Eventing specification.The underlying JMS engine handles WS-Eventing/JMS synchronization, which enables exposing and consuming your events using two different standard APIs.
Featured Graphical Console	WSO2 Message Broker includes a set of management services and a graphical user interface to configure, manage, and monitor the running message broker, allowing you to: Create and delete message queues Create and delete message topics and create subscriptions Register WS subscriptions using event sink URLs View message statistics Browse the registry View nodes that have joined the message broker cluster
Server Management via JMX	Manage queues, topics, and other server objects via JMX.