Migrating to Mule 3: Service or Flow

motif

Flow has transformed Mule and provides a very powerful way to configure many types of integration scenarios.  However, I wanted to make it clear  The <service> model from Mule 2 is not being deprecated or removed.  If you already use Mule 2.x you may be wondering whether to stick with <service> or go with the <flow>.

Building Mule Apps with Ant

motif

Mule 3 defined a simple, universal structure for Mule ESB applications. It’s a simpler version of war file format, consisting of a zip file with three sorts of entries:

  • At the top level, configuration files and application properties files
  • In the lib directory, jar files
  • In the classes directory, classes and resource files

We also created a maven plugin to build Mule apps.

Take a ride in the CLI with Mule Jockey

motif

How many web sites/web services have you wished you could just interact with over the command line? Sometimes, you just want to type commands in your shell. I can name at least 3 of our products which I’ve wished I could do that with: iON, MMC, and Tcat.

There are some challenges though. Bash/BAT file scripts don’t provide facilities to interact with web services. Then, if you go with a cross platform language, 

Introducing integration PaaS (iPaaS)

motif

This isn’t an industry that needs more acronyms but there is no stopping the cloud *aaS rocket ship so its better to clearly define new categories that get created as we fly towards the clouds. Integration Platform as a Service (iPaaS) is a new type of service tailored specifically for integration applications. The term ‘PaaS’ is a layer of cloud software that deals with the platform for building applications (if you are not familiar with PaaS take a look at my previous post).

The Developer Testing Paradox

motif

Over the years, I’ve seen many different testing styles while doing software development. Each one has unique characteristics, and some developers can identify themselves with more than one probably. I would like to go over all the different styles and point the effect it has over the project.

What is PaaS (Platform as a Service)

application networks

With 2011 being touted as the year of the PaaS there are still many questions to be answered. I thought I’d offer up my $0.02.

Let’s quickly go over the basics of where PaaS sits. There are 3 defined service layers to the cloud: Infrastructure as a Service (IaaS), Platform as a Service (PaaS) and Software as a Service (SaaS).

Both IaaS and SaaS are easier concepts to understand and have been around longer.

Deployment best practices for Mule

motif

Mule 3 had a ton of new improvements.  We’ve talked a lot about flows, cloud connectors and the like and offered webinars on each. Mule 3 also offers a new deployment model to support the deployment of multiple applications and hot deployment of those applications.

Are you looking to learn about how best to deploy Mule and Mule applications?  Should you deploy Mule standalone?  Should you deploy it on an application server?

Make the move to Mule 3 followup Q&A

motif

A week ago, we hosted a webinar on making the move to Mule 3.1. The goal was to introduce the new capabilities in Mule 3 and demonstrate the benefit they offer when working with Mule. More importantly we gave valuable tips on how to migrate your applications from Mule 2 to Mule 3. If you missed the webinar, the slides and an archived recording are available on the MuleSoft website.

Pimp your Mule Flow debugging session

motif

Mule Management Console 3.1 ships with the brand new Flow Analyzer. Select your server, interesting flows, click start and enjoy seeing real-time messages passing through mule! Click on an debug event and you will see the payload before and after each message processor of your flow.

Out of the box MMC will convert the payload to a string representation using custom toString method if any or by reflectively inspecting its individual fields.

Securing REST Web Services against LDAP

motif

Many Mule users create RESTful services but they are not always clear on the way to authenticate and apply authorization to a RESTful Web Service. I have seen questions about this topic so I decided to write a tutorial that covers a common use case. We’re going to use Jersey, Spring Security and LDAP and of course Mule to pull  it all together.  I will show you how to do the following:

  1. Expose REST resource using Jersey
  2. Secure the REST resource using HTTP Basic Authentication
  3. Authenticate and authorize users against an LDAP Directory
  4. Apply authorisation based on users groups to this REST resource