This page describes an older version of the product. The latest stable version is 16.3.
Mule ESB Integration
XAP comes with comprehensive support for Mule version 3.3 and 3.5. 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 the Mule VM transport with highly available inter VM transport over the Space.
It also enhances the Mule SEDA model, allowing you to store a Mule internal SEDA queue over the Space.
A Mule application can be packaged and run as a Processing Unit within one of the SLA-driven Processing Unit containers.
XAP’s event container transport uses event components that allow you to send and receive POJO messages over the Space using Mule.
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.
The XAP queue provider is used for internal space-based communication between services managed by Mule.
XAP’s 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.
Distributed Multi Mule service example