SAP is one of the most popular Enterprise Resource Planning (ERP) solutions on the market. But the big challenge for SAP customers is how to integrate SAP with other systems and application, which is key to automate and optimize business processes.
Here at MuleSoft, every few months we take a couple days off and hold a company Hackathon. Usually these are individual efforts to build something unique and interesting using the technology and products that we create at MuleSoft.
To kick off the new year, we decided to sponsor a team event and see if we could get some creative new ideas that might be more then a single person could implement in a day. The goal was to develop an iApp that demonstrated the power of the Mule iON platform. iApps are integration solutions developed on iON that solve a common problem and can be provisioned for use by different customers. The results were pretty inspiring making it difficult for those of us on the judging panel to choose a single winner.
We haven’t stopped though. Since releasing Mule 3.2.1, we’ve been busy working on Mule 3.3 M1. This is the first of a number of monthly milestones we will be making available to the community on the road towards Mule 3.3. In this blog post I’ll not only go over what’s new in M1, but also give you an idea of what we have planned for Mule 3.3.
Exception handling in event-driven systems like Mule can sometimes be a challenge because there are usually many more things happening at once, In this blog I will show you how to implement some common error handling patterns in Mule. We are going to cover the following use cases:
- Route a message before exception through an exception strategy to a dead letter queue
- Route an original message through an exception strategy to a dead letter queue
- Route a message based on exception type
You went to the gym twice last year yet you are considering renewing your membership; yep, 2012 is here. And while we’ve seen a number of exciting developments in enterprise IT in 2011, it was just the beginning. There’s a lot in store next year, here are 6 key developments to look out for in 2012.
I’m probably preaching to the choir here, but application messaging is extremely important for a wide variety of applications. It allows you to:
- Decouple application message processing from receiving
- Orchestrate data between two applications
- Handle the loss of a server without losing data
- Process data at a later date when you have more capacity
Yet, creating a reliable, highly scalable messaging infrastructure is extremely difficult – and sometimes not even an option. Amazon SQS takes that problem off your hands – it’s a hosted, highly scalable, reliable queueing service for applications. And now you can use it easily in your Mule applications with our new SQS support.
By now you have opened all your presents, you’re wearing your new socks/sweater/santa underwear, you’ve eaten like a champ and you’ve done the family bit. Now you find yourself thinking about the new year and what to do next. Here are some ideas for the technically inclined folks out there.
Less than a month ago we released the DevKit 3.0 and we are on a roll here. Just in case you are jumping onto the bandwagon a little late, the DevKit is a tool for authoring Mule extensions. The model is quite easy. First you write a POJO, then you annotate your POJO with Mule concepts and then when you run DevKit on the code you authored it will generate all the needed boiler plate code including a Mule-compatible schema. Sounds exciting, isn’t it? Unfortunately this blog post is all about whats change since the last release, but if you want to learn more you can do so at our website here.
We added several features in this release but to keep this blog post short I will cover just a few of them.