MuleSoft and CloverETL - ESB with Data Integration

CloverETL supports Mule Studio, Mulesoft’s Eclipse-based designer that drives the ESB. Embedded deeply into the Mule platform, CloverETL provides users the ability to map data payloads and create quick data transformations – which include parsing, validation, manipulation, and formatting. This visually intuitive data mapper allows for easy manipulation of and interaction with data.


Who is MuleSoft?

MuleSoft is a vendor of an enterprise integration platform Mule ESB and more recently, an on-demand PaaS integration platform called CloudHub. While the ESB product is aimed for application integration in enterprise environments, CloudHub focuses more on out-of-box integration of cloud-based applications.

MuleSoft and Clover share a very similar product philosophy: Building upon proven Java and XML technologies to deliver software solving customer’s application and data integration problems in a straightforward way – without introducing bloated application stacks.

What do they use?

MuleSoft introduced Mule Studio to allow developers to design and test Mule integration flows in a graphical environment as an alternative to the original Java and Spring-based configuration. Mule Studio’s visually intuitive data mapper based on CloverETL Designer technology allows for easy transformation of and interaction with data.

Now MuleSoft takes the next step toward developer productivity – by solving another headache of application integration: validation and mapping (transformation) of actual messages passing between integrated systems.

Originally utilizing XSLT, Xquery, Java code or scripting languages (Groovy, OGNL, JavaScript and more) Mule ESB now offers a dedicated data-mapping module called Data Mapper. The module provides a visual designer integrated into MuleStudio as well as execution module available in Mule ESB and CloudHub. Both the visual and execution module rely heavily on CloverETL technology, in particular CloverETL Designer and CloverETL Engine.

Data Mapper Introduction Video

How does it work?

The visual part of Data Mapper integrated into Mule Studio builds upon variety of CloverETL Designer APIs to provide the Studio user with dedicated screens for development and design-time validation of payload mapping.

The payload mapping is then translated into CloverETL data transformation format utilized by the execution module. As Clover data transformations are also stored in XML format it is easy to incorporate Clover configuration into existing XML configuration used by standard Mule projects and applications.

The Data Mapper execution module is essentially a wrapper around CloverETL Engine, which performs the actual payload transformation based on user-defined mapping. The Engine is initialized with generated data transformation on flow startup and transformed messages are passed in memory via Engine Java API.

Utilizing Engine plugin architecture Mule also developed additional Clover components useful mainly for ESB developers: JavaBean and JSON parsers and writers.

With the help of Clover, need for direct programming knowledge and coding effort are both significantly reduced.


Quick Facts

  • Vendor of Mule ESB and CloudHub; open source integration platforms
  • Technologies: Java, XML
  • Licensing/Availability: PaaS, on premise
Clover usage
  • Clover Engine: embedded use as execution core for DataMapper module in Mule ESB and CloudHub products
  • Clover Designer: embedded use of Clover Designer API to build DataMapper visual frontend in Mule Studio
  • As part of future releases: Direct access to Designer screens for advanced users
  • Custom extensions allowing in-memory exchange of data with ESB product
  • Joint development of components
Challenges solved
  • Transformation of messages payloads (parsing, validation, manipulation, formatting) within ESB