Imagine yourself as a service agent for retail giants like Amazon or Alibaba. What is the first thing you notice? Customer queries and service demands. Handling such a huge load of queries makes the work even more difficult. And that results in lack of customer retention.
It’s easier to get customers than keep the customers. Customer retention can only be ensured through proper customer service. But how to do that?
The energy sector is all about improving the processes that aid in efficient energy production and consumption. This in turn requires constant changes in the way data is managed and accessed. And this is where technology plays a key role: IT is needed by the energy and utilities providers because they depend on constant deployment, integration and implementation. Another important factor is the access, analysis and real-time processing of data. There is a continuous need for improved processes to deliver these facilities in the most cost-effective way in order to reach business objectives. This is where APIs (Application Program Interface) come in handy.
In MULE 4 when a event is processed Messaging errors happens within the flow when there is some kind of processing issue and the flow execution stops. This post explains how messaging errors are handled and how the error objects are created when a Messaging Error occurs. These Error Objects and are handled with error handler. Each error handler contains one or more error handler scopes. Each error scope can contain many number of event processors.
This short tutorial discusses how the objects in a Mule event change when an external source is called through the flow. A Mule event consists of Mule message, attributes, payload and variables. The tutorial is explained with parent and child flow respectively.
Remember those old days, when you need to add the correlationId as a prefix in each and every log messages in Mule 3 just to keep track of an individual HTTP request in your Mule API? Those days are just gone. So does the pain of extra Muley works. Because it is automatically done for you by Mule 4.
Once upon a time, there was a Microsoft SQL Server named DB007 running in a data center in an enterprise organization in Toronto. DB007 was sad. It doesn’t get much attention due to the high demand in the SAAS based database solution. Everyone is excited talking about the cloud-based solution, NoSQL, data lakes, etc. However very few people considering storing data into DB007.
We will need appropriate tools and proper environment set up to work with MuleSoft. This writing describes the components and sets up the environment needed to build and run the program.
The prerequisites-
JDK (Java Development Kit)
JDK is a package of tools which is needed to develop java-based software programs. Oracle provides free JDK to download. We will have an additional tutorial for downloading and installing JDK. For interested readers here is the link to install JDK. We will use version 8 in our environment.
https://www.oracle.com/technetwork/java/javase/downloads/jdk8-downloads-2133151.html
In MuleSoft we will use the Anypoint Platform and write RAML (RESTful API Modeling Language) code to design and manage the RESTful APIs. It requires permission from the owner organization to use the Anypoint Platform. Or anyone can have a free 30 days trial account to access it.
As the name denotes, it is a platform to perform various activities. This is the platform which can connect any application, API, and data source to all sort of devices. Anypoint Platform is active both in the cloud hub and on-premise.
Problem:
Sometimes to work with MuleSoft Anypoint Studio, we have payload with fields contain a null value.
For example:
Input Payload:
{
"id": 001, "firstName": "John", "lastName": null, "phoneNumber": null, "email": "abc@domain.com"
}
If you have already created a global error handler plugin (if not then click here to know how to create one), then you definitely want to share that among all different mule-applications. This article gives an example of how to install a global error handler plugin in a mule-application.
As a recap, our error response builder is a mule plugin which is responsible for managing error response and handling generic errors. This plugin will be imported in each working Mule project and invoke the generic error handling flow available in it.
This article assumes that you have maven installed on your local computer.
Pre-requisite:
