Using Quartz to Trigger a Service

June 29 2009

2 comments 0

When you’re working with Mule, you’re usually concerned about responding to messages that come in and making sure you’re routing them correctly from service to service. But what if you just want to trigger a service component on a set interval? What if its method doesn’t require any incoming data at all?

Using Mule for ETL

June 18 2009

6 comments 0

The Mule framework provides all the extract/transform/load (ETL) tools you need for connecting to data sources, extracting and transforming data, and passing it along on any number of channels.

Having Some REST with Mule’s Power Tools

June 9 2009

1 comment. 0

This is a guest blog entry by David Dossot, co-author of the soon-to-be-released book Mule in Action.

I recently had the opportunity to integrate a bunch of REST resources and came to further appreciate what I consider to be Mule’s power tools: scripting and expressions (there is a third tool in my power box, Spring, but I won’t discuss it here).

Scripting, and more precisely Groovy, has been key to this REST integration for:

  • Generating the desired request microformats
  • Processing the HTTP responses

Streaming in Mule

May 28 2009

4 comments 0

Streaming enables efficient processing of large data objects such as files, documents, and records by streaming the data through Mule rather than reading the whole thing into memory. Streaming provides the following advantages:

  • Allows services to consume very large messages in an efficient way
  • Message payloads are not read into memory
  • Simple routing rules based on message metadata are still possible
  • You can combine streaming and non-streaming endpoints

Galaxy on EC2 via Cloud Foundry in 10 minutes!

May 24 2009

0 comments 0

A couple of months ago, I reviewed the process for deploying Mule Galaxy, our SOA governance platform, onto Amazon’s EC2. Not long after that, I was introduced to cloudtools, a set of tools for deploying, managing, and testing Java EE applications on EC2. With these tools, it becomes trivial to deploy an application like Mule Galaxy to the cloud in minutes, rather than hours.

Error Handling in Mule

May 18 2009

0 comments 0

Mule provides different approaches to handling errors. You can set exception strategies for connectors, models, and individual services. You can use the exception router to specify where the message goes when an error occurs. And you can use the exception type filter for fine-grained control. Following is an introduction to these approaches.

Getting a Response from your Mule Services

May 4 2009

0 comments 0

When wiring your Mule services together, new users sometimes get confused about when to use an outbound router and when it’s sufficient to simply get a reply. Following is a description of the three message styles you can use to get a response from your Mule services.

Dallas JavaMUG

April 13 2009

0 comments 0

Continuing my whirlwind speaking tour on Mule, I landed in Dallas this week to talk to the JavaMUG. This was my first MUG (I’ve been to JUGs, SIGs, Camps, and Meetups, but never a MUG), and I was blown away to walk into a room of 75+ people all there to hear about Mule (okay, the free pizza and soda probably helped, too). Supposedly it was their largest attended event in several years. I gave a similar talk last month in San Francisco, but in Dallas I expanded a little on my thoughts about SOA and the Cloud.

Galaxy on EC2 in one hour!

March 30 2009

0 comments 0

We have been running Galaxy successfully on our in-house servers and laptops for demo purposes for some time now and decided that having a running image of Galaxy on Amazon’s EC2 was the next logical step. Galaxy in the cloud gives us the opportunity to expose a running instance to a much wider audience than might otherwise interact directly with the product.

Technical Webinar: Integrating WebSphere MQ with Mule

March 23 2009

0 comments 0

Are you currently using Mule or evaluating Mule for use with your WebSphere MQ messaging system? Do you need to utilize WebSphere MQ specific messaging headers, message types, and character code IDs with Mule? Would you like to know how to deploy Mule for maximum reliability when coupled with WebSphere MQ?