OpenSpaces Mule ESB support is available with Mule version 2.0 GA and onwards.

Overview

OpenSpaces comes with comprehensive support for Mule 2.0. It allows you to use the Space as a Mule external transport, enabling receiving and dispatching of POJO messages over the Space.

An additional transport called os-queue allows you to replace Mule VM transport with highly available inter VM transport over the Space.

OpenSpaces Mule integration also enhances the Mule SEDA model, allowing you to store a Mule internal SEDA queue over the Space.

Last, a Mule application can be packaged and run as a Processing Unit within one of the OpenSpaces Processing Unit containers – most importantly the SLA-driven container.

See the Distributed Multi Mule service example for a best practice approach when designing your Mule based application.

Section Contents

• Mule Event Container Transport — OpenSpaces event container transport uses event components that allow you to send and receive POJO messages over the Space using Mule.
• Mule Processing Unit — The Mule Processing Unit allows you to run Mule within a Processing Unit, thus leveraging all of the Processing Unit and SLA-driven container capabilities.
• Mule Queue Provider — The OpenSpaces queue provider is used for internal space-based communication between services managed by Mule.
• Mule SEDA Model — OpenSpaces Mule SEDA model allows you to define services that are aware of the space mode they are working with; and to store SEDA queues in a virtualized space queue instead of Mule's default VM queues.