Mule is a lightweight enterprise service bus (ESB) and integration framework[1] provided by MuleSoft. It has a Java-based platform and can also act as broker for interactions between other platforms such as .NET using web services or sockets.

Mule
Original author(s)Ross Mason
Developer(s)MuleSoft
Stable release
4.4.0 / September 7, 2021 (2021-09-07)
Repository
Written inJava
Operating systemCross-platform (JVM)
TypeEnterprise Service Bus
LicenseCPAL license for Community Edition, Proprietary for Enterprise Edition
Websitewww.mulesoft.com

It has a scalable[2] and distributable object broker architecture that can manage interactions across legacy systems, in-house applications, and modern transports and protocols.[3]

Supporting tools

edit

Design and development tools

edit
  1. Anypoint Studio: An Eclipse-based graphical development environment for designing, testing, and running Mule flows. It consists of two types of editors for development: a visual editor and an XML editor.
  2. Anypoint Enterprise Security: A suite of security-related features for secure access and transactions to Mule applications.
  3. Mule Healthcare Toolkit: Provided to process HL7 standard messages used in healthcare organizations.
  4. Mule IDE (now deprecated): A set of Eclipse plug-ins for developing, deploying, and managing Mule projects.

Management tools

edit
  1. Mule Management Console: A user interface that provides a run-time management facility for deployment to the Mule Repository and clusters.

Mule has an integration engine, but the community edition lacks support for Advanced Management interfaces. MuleSoft offers an Enterprise Edition of Mule that provides a management console, a Service registry, and higher availability.

Cloudhub

edit

Cloudhub is Mulesoft's Cloud-based integration platform as a service (iPaaS) designed to connect apps, data, and devices with integration connectors (like one to Twitter, etc.).

Mule ESB and messaging

edit

AMQP support

edit

AMQP (Advanced Message Queuing Protocol) support is based on the RabbitMQ Java Client and supports AMQP up to 0.9.1.[4]

JMS support

edit

Jakarta Messaging is a Message-oriented middleware API 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 (queues) and publish-subscribe (topics). Mule supports all functionality of JMS specification versions 1.0.2b and 1.1, and provides an endpoint for the same.[citation needed]

WMQ support

edit

WMQ or Websphere MQ is an IBM Message Oriented Middleware product for communication for distributed systems. Mule also provides support for WMQ called Mule WMQ Transport which works with 7.0, 7.1, and 7.5 versions and provides an endpoint for the same.[citation needed]

Universal Message Object

edit

The Universal Message Object Application 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 idea is 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 state-full back-off, meaning "no harm done", the user may then complete a transaction without losing too much work or cancelling 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.

References

edit
  1. ^ "The Role of the Enterprise Service Bus".
  2. ^ "Mule: A Case Study".
  3. ^ "Exploring ESB Patterns with Mule Blog - Oracle Community". Archived from the original on 2009-03-08.
  4. ^ "Home".

Further reading

edit
edit