Category: Tech Ramblings

Hello There! If you remember a couple of months back we started a series regarding the Google Cloud Connectors Suite. In the first post we introduced the suite, took a look at how to install the connectors in Studio and built a very simple yet cool iApp that takes contacts from a Google Spreadsheet and turns them into Salesforce contacts, Google Contacts, Google Calendar Events and Tasks.  Then on the second post we gave some quick code examples of common usage on the connectors.

Today MuleSoft and THINKstrategies have published the results from our 2nd annual SaaS Integration Survey. These results validate the growing interest we’ve seen from SaaS providers to build and offer integration as a part of their service. See below for the key findings and don’t forget to download the report today!

Add our Infographic to Your Site

Interested in learning more? Download the full report.

Hi and welcome to Mac, fellow

In this post, I will go over some tips I’ve been collecting which can make your life as a developer just a little bit easier if you come from other operating systems. Of course the list can grow, but here is my list. This article is based on MacOS X 10.8.2 (Mountain Lion), but should be helpful for other versions as well.

With the rapidly increasing adoption of SaaS, integration Platform as a Service (iPaaS) has become the preferred way to connect SaaS applications.  However, with the explosion of Open APIs on the Web connecting APIs together is becoming the norm for application development. However, typical application containers and even application PaaS offerings don’t help in this new era where applications compose APis together from many different sources.

In the iPaaS world composing APIs together is modus operandi. An application built on an iPaaS is focused on connecting 2 or more systems together via APIs in order to synchronizing data between them.  However, we’ve taken this new breed of applications much further with the concept of Integration Apps.

This Monday, we are very excited to be participating in Cloud Channel Summit, hosted by THINKstrategies. As more Enterprises are moving to the cloud, ISV’s have an opportunity to grow their customer base from the early adopters in small businesses through to the largest of Enterprises. At MuleSoft we understand Enterprise IT projects and what it takes to make systems and applications work together. We also understand the tremendous value partnerships can bring to SaaS companies as they look strategically across their portfolio, and make critical decisions across engineering, services and sales resources for 2013 to outpace their competition.

Today I would like to talk a little bit about releasing a new version of your extensions.  As you may know is a an extensible platform with well defined integration points for plugging in your own connectors transformations, components and even routers. Suppose you have used The Mule Devkit to create your very own extension or cloud connector, and your project is so cool that it was accepted on MuleForge.

What happens if you make changes to you project and it moves from version 1.0 to 1.1? We’ll take a very quick look at how to do that in this post.

First, modify your pom.xml to increase your version number. In this case, we’ll go from 1.0 to 1.1:

<groupId>org.mule.modules</groupId>
<artifactId>cool-connector</artifactId>
<version>1.1</version>
<packaging>mule-module</packaging>

    

Mark Zuckenberg once said: “How can you connect the world if you leave out China”. Well, I now hereby say: “How can you connect the cloud if you leave out Google”. I know I don’t have his net worth, but I have a point nevertheless. Reality is that Google has done a great job building a Gazillion of different and very cool APIs and you’d be right to feel that it’s hard to keep their pace. To help you with that is that we proudly present to you the first release of the Google Cloud Connectors Suite.

Picking up where Dirk Olmes left off in the post, Migrating a MuleForge project to Github, we now suggest a utility to facilitate the migration: svn2git.

svn2git is a tiny utility for migrating projects from Subversion to Git while keeping the trunk, branches and tags where they should be.

This involves three basic steps:

  1. Getting the svn repository
  2. Creating a Git repository
  3. Pushing the trunk, tags and branches (previously added)

Step 1 is where svn2git is very appropriate.  To use it, you just need to execute the command “svn2git” followed by the url of the svn repository and the utility does the rest. Great, isn’t it?

future of integrationThe explosion of APIs, applications, and mobile devices has created a massive integration wave. The resulting shift in the way we connect is forcing an IT mega change unlike anything we’ve seen before.  As the development model moves from writing reams of code to composing APIs together, a new generation of middle tier application architecture is being born. What does this mean for you? Ross Mason, MuleSoft’s Founder and CTO, will provide his perspective on the future of this growing movement.

Topics include:

  • The give and take of
  • A glimpse into the connected revolution

Customer stories series: SNMP alerts

Nagios

Motivation

We are evaluating using Nagios or a similar Big Brother Enterprise solution for displaying information about our many Enterprise Mule instances, applications and the status of our production and staging environments. The only sure thing is that we presented a budget for buying a couple of 55” monitors and were approved. Pure awesomeness!

First solution: Do it yourself

This is complicated. We would have to hire a Java programmer to develop an agent to gather from servers distributed in different geographical zones. Pretty heavy stuff. The project would take a while to complete. And once that is done, we would have to start worrying about upgrades, deployment of the agent, and paperwork. We are using a waterfall cycle. You know the pain.