Tag: Drools

Introduction

The architecture of 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!

Complex event processing engines are a natural fit for event driven platforms like . Native   support has been available in since version 3.2 by way of the Drools Module.  The Esper Module now offers an alternate way to leverage CEP in your integration applications.   Esper is a robust, performant, open source, complex event processing engine.  Let’s take a look at how to use with Mule and then see how it compares to ’ CEP support.

Eugene Berman on Wednesday, February 1, 2012

Using Mule with Drools and jBPM

3

3 has many routing processors and expression evaluators that can be used to implement routing logic. However, sometimes business rules may be too complex. For example, one of our customers is a large logistics company which uses for their warehouse routing. To handle their complex set of rules, they decided to use with and .

This example illustrates use of Drools and jBPM inside Mule, by implementing very simple order sorting and warehouse routing use case.  In this scenario all orders with weight greater than 50lbs should be routed to the warehouse A, and orders with weight equal to 50lbs or less should be routed to the warehouse B.

michael.khalili on Thursday, July 21, 2011

Get a sneak peek at Mule 3.2

0

3.2 is right around the corner and it is shaping up as the best release ever.

Some highlights include:

  • High availability for mission critical environments
  • A to gain deep visibility into business events for root cause analysis and compliance
  • integration for business rules and complex event processing

In part 1 of this post, I gave an overview of , , and and the way they compliment an integration platform such as . Now let’s take a look at what has to offer for integrating with some of these tools.

One of the more common usages of 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, and Mule allows you to integrate with as many different options as possible.