Integration is the biggest challenge in the cloud


When people ask  “what are your biggest concerns about cloud” you may think security, lack of standardization or reliability, but the real challenge is the same challenge that has challenged every enterprise; how do I get my applications to talk to each other and how to I respond to changes in my business?

The fact is that there are some major trends happening that are making integration an important if not the most important economic and business imperative.

Modeling your Business Logic: BPM, Rules, and CEP (Part 1)


One of the more common usages of Mule is as the integration piece of a larger SOA architecture. Mule has traditionally never attempted to offer a complete SOA suite/stack of products as some of its larger competitors do, but has rather focused on the thing it does best, which is integration. Other aspects of an SOA architecture (messaging backbone, data storage, governance, etc.) are generally provided by other best-of-breed solutions for those areas,

Unveiling the AMQP transport for Mule 3.1


Messaging systems used to be found only in big enterprises or in the financial sector. Who else needed the reliability and scalability offered by such systems? But times have changed: public web sites have grown to sizes that dwarf some of the most advanced corporate systems. And as these web sites have grown, the need for timely decoupling their subsystems in order to scale has increased to.

This lead an entirely different breed of developers to want messaging systems too.

Go with the Flow with Mule 3.1!


Mule 3 underwent some significant architectural improvements, I talked about this back when Mule 3.0 was released in my “Mule 3 Architecture: Back to Basics” blog post.  These improvements  enable a much simpler way of configuring Mule that is more powerful while at the same time much more intuitive.  As we release Mule 3.1 I really want to encourage everyone to “Go with the Flow!!”

In this post we’ll cover the basics of “Mule Flow”;

Logging just got a lot easier in Mule 3.1

December 17 2010

1 comment.

Mule 3.1 introduces a very useful new <logger> element that makes it easy to inspect the content and properties of your messages in Mule while building or debugging a flow. It’s also perfect for logging errors, info messages etc.  Mule has always supported logging with the <log-component> but while working with the new orchestration capabilities of Mule 3 flows, we found a real need for fine-grained logging. With the new message processor architecture,

Why use jBPM with Mule?


Mule integrates with jBPM, allowing you to send/receive messages to/from a running process. A message from Mule can start or advance a process, the message can be used as a process variable, and a process can send messages to any endpoint in your Mule config.

Mule 3.0-M2 and beyond


I’m pleased to announce that Mule team has just released 3.0 Milestone 2. Before we get into the features coming in Mule 3.0, I’d like to talk about the theme for this release.
The overall theme for Mule 3.0 is simplicity. We are looking at every part of Mule to see what we can do to make things even easier. Mule is a powerful platform, but we realise not everyone wants or needs all that power.

Invoking a service method in Mule


At TSSJS last week I had a conversation with a Mule user that was having a problem invoking more than one method on a service component (just a POJO object). His scenario was that he had a service with multiple inbound endpoints and a service component with multiple methods, some with matching parameter types. Existing Mule users will be aware that Mule will match methods against the parameters received in the current message. Thus is two methods have the same parameters Mule cannot match the method to invoke.

The new @Schedule annotation in Mule and iBeans

December 17 2009

1 comment.

Scheduling is great, it really is. It’s also very useful for application integration since we often have to repeat tasks of over time interval or schedule tasks for a date in the future. Mule has had scheduling support since version 1.1 with the Quartz connector, now with iBeans scheduling just got easier. iBeans offers a annotations-based API for performing common integration tasks such as sending email, subscribing to a JMS queue or polling an ATOM feed.

Mule IDE 2.0 Released

October 27 2009


MuleSoft is proud to announce that Mule IDE 2.0 has been released.

Mule IDE 2.0 is a development and testing environment based on Eclipse. It supports the following features: