Designed With SaaS Providers in Mind: Mule iON SaaS Edition Now Available
Hello friends! How’s it going?
Has the following ever happened to you? You show up to work one morning and your boss tells you, “I need you to take this data and turn it into XML.” Well, this has happened to me, and in this blog post I’m going to show you how to do this quickly.
The architecture of Mule is driven by the principles of Industrial Best Practice as outlined in the well-known Enterprise Integration Patterns which have identified the most common building blocks for every integration problem. These building blocks are what make up Mule Flows, the executable units inside Mule Applications. No matter what the problem, wiring them together into an integration solution is extremely easy and by exploiting the power of Mule’s native support for the Drools Rules Engine, the Integration Developer has a very powerful set of tools to tackle even the most complex of integration problems with the greatest of ease. With this post I hope to be able to demonstrate this to you! Read More »
Today we’re interviewing Geoff Clitheroe, GeoNet Systems Development Manager at GNS Science in New Zealand. What does this beautiful but quake-prone island country have to do with Mule? This is where Geoff’s work comes into play: he’s leading a team of developers with whom he’s been building GeoNet, an advanced geological hazards monitoring system. And Mule is at the core of it.
MM. Jeff you’ve shared some very interesting blog posts about your usage of Mule in GeoNet (1 2 3). Before going into the juicy details can you summarize what GeoNet does?
Whether it is to reduce costs or growth through innovation all companies need to constantly be thinking about how to gain competitive advantage. Over the last 20 years companies have looked towards enterprise software applications to drive this differentiation. Typically the cost of doing this runs into the millions or tens of millions, meaning it was a rich mans sport with smaller companies either getting squeezed out or forced into small market niches.
However, with the rise of SaaS the economics are changing. Now companies of all sizes are turning to applications delivered as a service due to the frictionless setup and maintenance and the much lower up front costs. The cloud is creating a level playing field for all companies where everyone has access to the same applications. In this landscape, its the integration of these applications to deliver better customer experience, innovative business models and low cost services that will drive competitive advantage.
During my years on the Mule Community forum I’ve noticed that there are some problem areas that are more common than others. One recurring question, that I thought I should address here, is how to preserve message order in JMS.
The first solution coming to mind is to use exclusive consumer, but I’ve come to realise that there are some disadvantages with exclusive consumer such as having active consumers doing nothing (I don’t like the idea of having workers ready to dig in but they are not allowed to). Another thing is that, with exclusive consumer, a message might block another message even though they really don’t have anything to do with each other. For example, let’s say we’re dealing with car orders, then you probably don’t want a order for a Volvo, that doesn’t go through, to block a order for a Saab (I’m Swedish). Read More »
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 article, I will focus on the Reflection Entry Point Resolver, which is used to determine the entry point on a component after a message has been received. The entry point is discovered using the message payload type(s) as the argument using reflection. For multiple parameters the payload should be an Array of objects. If the message payload is of type NullPayload the resolver will look for a no-argument method. Read More »
This Wednesday, April 25th we are excited to join the folks at THINKstrategies for The Cloud Analytics Summit. This is shaping up to be a great event, jam-packed with best practice sessions and opportunities for discussion.
One of the reasons why we are partnering with THINKstrategies is to help companies see how an integration-platform-as-a-service (iPaaS) can accelerate their Big Data and cloud analytics projects.
The integration challenges around Big Data and cloud analytics tend to be twofold. First, it’s important to have your data in a central place, and second, it’s extremely important to collect and analyze that data in real time.
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.
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, from relational databases to spreadsheets and flat files and, using the proper SQL syntax, you can perform queries, updates, deletes, or even execute store procedures.