Category: CloudHub

One aspect of Mule DataMapper that makes it a grate integration tool is its ability to do mappings involving complex and different data structures (XML, Json, POJOs, CSV, Excel files and more). One feature that is really attractive is the possibility to test your mappings without the need to launch your Mule application, so that you can provide sample input data and what the result of the will be.

After reading this post you should be able to:

  • Understand how to add and use Input Arguments
  • Test your mappings with the Preview Functionality

We’ve just rolled out a new platform service in our CloudHub R20 release for storing application data. With Mule’s Object Store capabilities, each integration application is given it’s own storage, with zero configuration required. This makes it a extremely easy to implement two very important integration scenarios:

  1. Persisting OAuth tokens – all our OAuth enabled connectors can store tokens and restore them using ObjectStores
  2. Storing synchronization state – your application may need to keep track of the last record synchronized, so the next time it synchronizes it can resume where it left off

In addition, you can store any other data you want in it as well! Let’s take a more in depth look at these scenarios.

Following the recent release of Mule 3.3.0, I’m happy to announce the related releases of five community transports: AMQP, , Redis, and JCR.

With these new versions available, you’ll be able to benefit immediately from the new features of Mule 3.3.0.

This tutorial is the second in a series of blog posts that explain how to integrate Mule and .

Today’s post will focus on connecting to and updating your status on .
Other posts to expect will integratie Mule and:

  • LinkedIn
  • Yammer

Myself and Dave recently spoke a different events about APIs and use cases.  Folks ahve been asking for the slides and video, so here they are!

Real-time APIs: Don’t call us, we’ll call you

The number of real-time APIs on the Web are rising. What the heck are real-time APIs, how are they used? How are they built? This deck and demo was presented at in San Francisco.

are a very simple way to tie application together on the Internet. Suppose application A wants to be informed when changes in application B: the traditional approach consists in having application A poll B for changes. The webhooks approach turns the problem around: B gets configured so it hooks to A via HTTP calls. Whenever changes in B (or for that matter, whenever anything of interest happens in B), B will call A to let it know. No more polling, just simple HTTP server-to-server callbacks. Webhooks is so simple that there is no spec for it: the HTTP spec is all what is needed really.

SOAP, JMS, Restful, SFTP… Sometimes your integration just comes to the point in which you need to be able to download a file from your browser. From Ubuntu One all the way to Dropbox and Google Drive, the number of file storage on the cloud just keeps climbing. One that is particularly gaining a lot of momentum and putting a lot of effort on cloud to cloud integration is Box, so we decided to build a Cloud Connector for it and we’ll show it to you in this post.

We’re big fans of real-time here at MuleSoft, always asking “why wait for anything?”.  This week we have Ross our CTO and Dave our Architect and Integration Strategy Lead talking at local events, the CloudMafia meet up and the Salesforce.com Integration and Analytics meet up. We’d love to see you at either of these events this Wednesday evening.

Ramiro Rinaudo on Tuesday, July 10, 2012

Mule 3.3 Hackathon Results

3

A new Mule release has to come with another internal hackathon. Our development teams focused on using the new features we added in .3 and we came to the conclusion “A hackathon is like a of chocolate, you never know what your are gonna get”. In our case, we got some really cool applications, so cool that some of those can become real products in the future.

In response to the growing demand we’ve seen for application and data connectivity across the ecosystem, this week we are renaming our integration platform as a service Mule iON to CloudHubTM. I’d like to give you a quick insight into why we’ve changed the name.