Have you already tried the Visual Flow Debugger? It’s one of the new shiny features that comes with Mule Studio Enterprise 3.4. Well, if you haven’t used it yet, this post is for you:

1. Message BrowsingAll the information you ever wanted, now at a click’s distance.

Before Visual Debugger, if you wanted to see the contents of the payload at each point you had to clutter your mule configuration with loggers all over the place, well, those days are over. Just put in a breakpoint et voilà!

You can also edit most values dynamically at runtime by clicking them.

Note: Be careful, what you put in there is not a string, but a Mule expression. Therefore string literals go with quotes (e.g. “a string”)

Tip: If you are looking for the complete message, it’s located in the Variables tab (on the right side). The things we show on the left are the most commonly used elements, the payload and some IDs.

 

2. Exception breakpointsStop browsing huge logs to find the error source.

This functionality is enabled by default, so that when you run in mode and there’s an exception somewhere in your flow, it will stop processing at the exception. Studio highlights the stopping point with a red, dotted line.

Before:

After:

 

3. Conditional breakpointsAre you picky? Then today’s your lucky day.

Suppose, for example, that you want to isolate one specific case in a really big set. What do you do? Put another Choice component in your flow just to separate it? No way, just apply a conditional breakpoint! Set it with whatever Mule expression you want evaluated and if it evaluates to true, flow execution stops there.

 

4. Expression evaluation
These come in two flavors:

  • Non eco-friendly (popup): Just use and dispose. Open it, evaluate, click somewhere else and they’re gone. Really simple, right? (My personal favorite)
    Tip: Use the popup shortcut and navigate with the arrow keys
  • Collector’s edition: add your expressions to the Mule Expressions pane so that Studio re-evaluates them at each step.

 

Save time and reduce frustration: give Debugger a try, by downloading Mule Studio.

Access our Mule Documentation for a more in-depth look at the Studio Visual Flow Debugger.

 

 

 

 

Related posts:

  1. 10 Little Mule Studio Gems
  2. Change the Studio Category of your DevKit Component
  3. Mule 3.4 Blog Post Line Up
Interested in 3 days of knowledge sharing, hands-on labs, industry focused sessions, and plenty of networking? Register for the premier integration event, CONNECT London »

One Response to “Mule Studio Visual Flow Debugger Walk-through”

Bent S July 9th, 2013, 11:06 pm

You should start with saying Visual flow debugging only works for EE runtimes, not CE (unfortunately)

Leave a Comment