Mule ESB offers an amazing out-of-the-box integration which easily integrates with ActiveMQ. There is a plethora of examples on the internet that will show how to use ActiveMQ with Mule. But here we will explore how to use a filter with ActiveMQ and Mule that will help us picking up the right JMS messages we need.
Consider an environment where there is a JMS queue and there are multiple consumers listening to that queue;
Recently I had a situation where I needed to get confirmations from an external system (webservice) at frequent intervals and add them to a database. All available confirmations were retrieved in a batch when the service was invoked. A confirmation was sent to the Service after a successful retrieval.
Of course, Quartz came to mind. Piece of cake I thought and implemented the scenario using Mule ESB. Everything seemed to work as planned until we started to notice duplicates of confirmations in the database.
Mule Properties and Flow Variables are one of the most widely used features in Mule. Nevertheless, Mule newcomers may have a hard time understanding how the different property scopes and variables compare to each other, and how to choose the right one for their use cases.
The idea behind this blog post is to clarify those differences, comparing side by side INBOUND, OUTBOUND,
I’m going to provide an overview on how to build a simple contract-first web-service and JAX-WS client that consumes the web-service with Mule Studio.
The sample below is going to build the following:
Build SOAP/ HTTP web service using Mule & CXF that is CRUD web service to create, retrieve, update and delete an order and returns the order id. This exercise implements only the create operation for this service.
In the previous lesson Invoking Java Component Over HTTP, we learned how to invoke a simple method of a Java component in Mule Flow. Let’s now go a bit further and see how Mule maps a request message to a specific method in your component using Entry Point Resolvers.
At a high level, Mule uses three types of Entry Point Resolvers.
In this blog post, I’ll give you some background information about JDBC, explain what Mule ESB and Studio do with JDBC, and demonstrate how can you use it in a simple example.
A little reference for JDBC:
JDBC, which stands for Java Database Connectivity, is basically an API that enables users to execute operations over a Data Source using the Java programming language. This API allows you to connect to almost any Data Source system,
Mule Studio offers easy-to-use components to connect to JMS Queues and Topics. In today’s example, we’re going to learn how to use ActiveMQ, a leading open source JMS implementation from Apache that supports JMS 1.1 specification.
Here’s an outline of the simple steps required to implement this example:
Since Mule is built on Java and Spring, it has native integration capabilities to invoke Java and Spring components. In this tutorial, we shall learn how to pass request received from HTTP endpoint on to Java component and receive response.
Please complete Hello World lesson from last week before proceeding further.
This is a series of blogs aimed at developers new to Mule that are just getting started. These lessons will introduce common concepts and implement frequent use case that we see in our community. If you have suggestions for a lesson, please post it in the comments.
The lessons are all based on Mule Studio, the free Eclipse IDE for Mule, you can get the latest version here.
MuleSoft provides the most widely used integration platform for connecting any application, data source or API, whether in the cloud or on-premises. With Anypoint Platform®, MuleSoft delivers a complete integration experience built on proven open source technology, eliminating the pain and cost of point-to-point integration. Anypoint Platform includes CloudHub™ iPaaS, Mule ESB™, and a unified solution for API management™, design and publishing.