Mule is a lightweight enterprise service bus and integration framework provided by MuleSoft. The platform is Java-based, but can broker interactions between other platforms such as.NET using web services or sockets. The architecture is a scalable, distributable object broker that can handle interactions across legacy systems, in-house applications, and almost all modern transports and protocols.
Supporting tools
Design and Development Tools
Anypoint Studio: An Eclipse-based graphical development environment for designing, testing and running Mule flows. It consists of two types of editors for development: Visual editor and XML editor.
Anypoint Enterprise Security: A suite of security-related features for secure access and transactions to Mule applications.
Mule Healthcare Toolkit: Provided to process HL7 standard messages used in healthcare organizations.
Mule IDE, A set of Eclipse plug-ins for developing, deploying and managing Mule projects.
Management Tools
Mule Management Console: A user interface which provides run time management facility of deployment to the Mule Repository and clusters.
Mule has an integration engine, but the community edition lacks the support for Advanced Management interfaces. MuleSoft offers an Enterprise Edition of Mule that provides a management console, a Service registry and higher availability.
support is based on the RabbitMQJava Client and supports AMQP up to 0.9.1.
JMS Support
is a Message-oriented middlewareAPI provided by Oracle for communication between different components of an application. This provides reliable, loosely coupled and asynchronous message-based communication, supporting two models: point-to-point and publish-subscribe. Mule supports all functionality of JMS specification versions 1.0.2b and 1.1, and provides an endpoint for the same.
WMQ Support
WMQ or Websphere MQ is IBM Message Oriented Middleware product for communication of distributed system. Mule also provides support for WMQ called Mule WMQ Transport which works with 7.0, 7.1 and 7.5 versions and provides endpoint for the same.
Universal Message Object
The Universal Message ObjectApplication Programming Interface is part of high-level design methodologies used to describe and define aspects of a data object used in conjunction with the Mule ESB. The ideais to, by staged events, wrap the work into sensible bundles and process it in stages that can conform to models of transaction-based processing that are useful in time or mission-critical applications such as financial transactions, where subsequent successful outcomes are required to permit the desired outcome. But if the user fails to supply needed data or a run-time error occurs, then the model will allow for stateful backoff, meaning "no harm done", the user may then complete a transaction without losing too much work or canceling an entire transaction. Universal Message Object defines the parameters that the program will use for internal messaging communications and its components to set and get variables based upon the user's needs and the program's functionality.