Perhaps the most powerful core component in Mule, the Batch component has been there in Mule since a long time. The rationale behind having this processor is to process large amount of data in segregated batches so that failure is minimized and accounted for, and can be re-tried later if required. We will see in this article how all this happens (based on Batch component for Mule Runtime 4.x), but let’s first try to understand the underlying to principle of batch processing.
P.S: I will mainly highlight the the core concepts and structural building blocks of Batch, for configuration related information you can refer the MuleSoft documentations in Reference section. …
Most of us may feel that this is a cliched question, as we all know that Mule runs of Java (JAVA 8 only). But it is not the programming language base that Mule is all about. The core operating model has lots of intricacies and over the years there has been lots of optimizations that mule runtime has gone through which enables to provide solid performance.
In this article I am going focus on the core runtime model that Mule 4.x implements at a high level and what new options have become available when it comes to runtime tuning.
While I write this article, MuleSoft has just released version 4.3 a few weeks bug with plenty of fixes and new features added to it. …
Over the years MuleSoft has become one of the go to integration tools capable of connecting numerous complex systems via use of some the premium and select connectors that are available.
It all started way back in 2003 when the current VP Product Strategy,Ross Mason founded the open source Mule Project. He created a new platform that emphasized ease of development with quick and efficient assembly of components, instead of custom-coding by hand.
The integrations are reusable and doing that over and over is just “donkey work” :)
Although most of the API’s that we interact with nowadays are REST based microservices endpoints, but there are plethora of legacy SOA applications who are still exposing SOAP webservices for them to be consumed to interact with backend data which resides on systems like mainframe, oracle databases etc.
In order to consume such webservices Mule 4 provides the all new WSC Connector. In this article we will discuss the ways via which we can use the connector to upload files to the webservices.
Older versions of Apache CXF connectors used in Mule 3 are no longer supported in Mule 4.
There are two ways you can upload file via WSC connector in Mule…
Last week I came across a very interesting problem while trying to implement a SAML integration with one of the Mule applications. I would just touch upon the main points which I had to be implemented as a part of the workaround and got it fixed instead of going into cumbersome details of the integration.
The requirement was to build a flow which would accept an XML data coming from a source system. …
Scatter Gather is very well known routing event processor that we use to parallel process multiple business logic on the same given payload and then finally aggregate all the individually processed mule events into new mule event which is then passed on to the next component in the flow. It is an extremely useful component when you want to process a mule event simultaneously across multiple processors and there is no inter-dependency within data response coming from them.
While building several different workflows using the Scatter Gather component I came across some unique issues which I am going to discuss in this article. …