This section of our blog is about showcasing current and upcoming cloud connectors. Cloud Connectors are modules that allow easy connectivity to cloud APIs such as Twiiter, Facebook, and the thousands of Software as a Service platform out there on the net.

This week will talk about Mongo. Mongo is very popular database nowadays, and for several reasons. It is being use in production by several well known companies such a Disney, The New York Times, Foursquare, Chicago Tribune among several others.

Community on Thursday, August 4, 2011

SaaS Identity Provisioning use case


On one of the previous blog posts by Ross, “To ESB or Not to ESB“, he did a great job in outlining the two basic integration architectures: “Enterprise Service Bus” and “Hub and Spoke”. Included in the Blog is a good overview of the benefits and considerations that are relevant for each architectural choice.

A key implementation consideration for SOA enabled architecture such as An ESB is the capability to maintain pace with the integration needs of the organization.
The reason this is important is that we live in very dynamic IT world where business needs and system can change with the next bright idea. If your organization responds too slowly, then you are putting your organization at risk by not being able to compete effectively in the market place.

To truly be competitive, your organization must adapt to the ever changing, and complex world of technology integration. The reality is that  you no longer have months to design and additional months to deliver integration to the organization.

In the real world there is a good chance that you have an existing Identity Management System already deployed. It is also quite likely it’s either a implementation or a system that has not been updated in quite some time.

So how do you maintain and extend an existing identity management system?  What are the basic choices you have for managing your current environment and, extending it into an SOA enabled architecture?

If you have come to this “fork” in the road then there are two obvious choices available.

  1. Rip and Replace the existing solution
  2. Continue to add on to your proprietary hub and spoke solution

Both of these choices will work but they are not ideal for any number of reasons (Expense, Time to Delivery, Continuing investment in Legacy environment).  So what are the alternatives and how can I use SOA concepts to maintain services and support the organizations growth:

“How can I maintain and extend my current environment in an SOA enabled environment”?

There is a readily available answer for this question and in this blog we will present a real life demonstration of how this can be accomplished.

In the next part of the blog we are going to walk through a real life example of using a SOA enabled (hybrid approach) to provisioning and de-provisioning cloud SAAS accounts.

exception handling code is not always an easy task. You either need to setup the external conditions that cause the exception to be raised or generate mocks to get the same results.

A third option is using a bytecode injection tool like Byteman. Using scripting language you can insert custom behavior into the application code under test. The main use cases for are:

This is my final post in a series of ESB or not to articles where I have attempted to shed some light on what an really is and show some alternative architectures for performing integration.  I’ve given an overview of four main architectures that I see most often and provided some context about the benefits and the considerations of each. You can read the original post and follow-up parts 1, 2, and 3. Here is a quick recap.

In this penultimate part of my ESB or not to ESB series I’m going to cover two more architectures; API Layer and  providing the benefits and considerations for each.

Previous Posts:

API Layer

An API layer (or Service Layer) provides a set of to access data and/or functionality. Typically implemented using or SOAP services over HTTP, it provides decoupling of backend systems and applications from the clients that access them.

It is pretty common that messages contain as a payload and that those messages need to be validated/transformed. XML documents can be automatically validated using XSD, though those validations are structural and sometimes we need to manually code some in plain Java (especially in complex scenarios like validating references, existence conditions and value dependencies).

Do you want share properties between mule instances? or just between different flows within ?. Then mule session properties are what you are looking for.

Dan Diephouse on Thursday, July 21, 2011

Introducing Mule Query Language


Working with web APIs, local APIs and different data formats and structures is too damn hard. You have to write painful verbose code to:

  • Query Web and work with the data
  • Enrich and join data from external with local
  • Compose RESTful services from existing services
  • Version services and data formats
  • Merge data from different sources into a common data format
  • Sort through sets of data
michael.khalili on Thursday, July 21, 2011

Get a sneak peek at Mule 3.2


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 computing like in life, not every attempt is successful the first time. A message delivery to a remote application may be impossible for a while. A particular business action may be impossible due to the temporary unavailability of an enterprise resource. The good news is that these adverse conditions may not last: all what is needed is to retry the failed operation until the issue gets resolved.

This approach is well-known in the industry. Just take a look at how emails operate: delivery between SMTP servers is attempted repetitively until it succeeds. Failure is assumed and dealt with. Following the same principles, we’re happy to introduce the Until Successful routing .