Category: CloudHub

Introduction

After creating a basic Mule App, you might be wondering how to automate the process of deploying a Mule App to . In this post, we are introducing a Maven plugin that enables that use case. As a result a Mule App will be deployed automatically to after a Maven build. This is achieved using the goal cloudhub-deploy from the Mule AppKit Maven Plugin.

In a ideal development workflow, each time the project builds the Mule Application will be deployed to the cloud providing a cutting edge instance that can be used for QA of the latest snapshot. Both Bamboo or Jenkins can be configured in order to run Maven and deploy the Mule App to CloudHub.

It’s pretty common to hear and read about how everything in the IT business is going “as a service…”. So you start hearing about Software as a Service (SaaS), Platform as a Serivce (PaaS) and even Integration Platform as a Service (iPaaS, which is where our very own platform plays on). But what about data?

Lack of Connectivity Limits Marketing and Sales Engagement with Customers

As more companies adopt SaaS sales and marketing applications, providers are under the gun to create and offer functionality that supports the business process and automation requirements of these individual and sometimes silo teams.  In any given organization, sales and marketing use upwards of 10 – 15 applications to engage, onboard and maintain customer interactions.  Believe it or not, here at MuleSoft our marketing and sales teams use over 30 different applications. Yes 30, and we have less than 30 people in our marketing organization! Sample applications include, HootSuiteGoogle Apps, Confluence, Yammer, Salesforce, SurveyMonkey, WebEx Events, Eventbrite, Cloud9 Analytics, KISSmetrics, Google Adwords, GetSatisfaction and the list goes on. Each of these applications are used to engage the customer in a different stage of the buying process:

Calling all Salesforce.com users! Looking for a fast and easy way to move data in and out of .com? Look no further – follow these best practices from the dataloader.io to quickly become a data loading pro:

Add our Infographic to Your Site

<a href="https://appexchange.salesforce.com/listingDetail?listingId=a0N30000009w8ZBEAY"><img src="http://blogs.mulesoft.org/wp-content/uploads/2013/06/salesforce_dataloader_infographic.jpg" alt="" width="500" /></a>

 

At MuleSoft, we’re constantly looking for better ways to solve the integration needs of enterprises. Software as a service is creating new integration requirements and Gartner expects the SaaS market to continue growing at a blistering pace of 17.9% through the end of 2013. With the adoption of in Europe and Asia Pacific accelerating, we talk to customers every day looking to integrate in the cloud across geographies, and isolate certain data to comply with data protection laws.

Dataloader.io, MuleSoft’s #1 data loading app on the Salesforce AppExchange, just reached the 1 billion records processed mark!

As a special thanks to all of our dataloader.io pros, we’ve created a nifty for you to get the most out of your dataloader.io experience:

Add our Infographic to Your Site:

<a href="https://dataloader.io/"><img src="http://blogs.mulesoft.org/wp-content/uploads/2013/06/Dataloader_existinguser_final.jpg" alt="" width="500" /></a>

As an avid observer of the Salesforce.com data loading community, I thought it would be interesting to share some of the trends we see within our dataloader.io user base heading into the summer. How do these data loading trends compare to the activities within your organization?

SaaS is one size fits all (kind of)

Even though is a based application, there is quite a bit of customization that takes place inside account, opportunity and contact records. While the majority of datalaoder.io users have standard objects, roughly ⅓ are routinely updating, upserting or inserting (importing) custom objects into their salesforce.com orgs.

Mule has a very extensive support for data stores, which covers pretty much the whole spectrum of what’s available out there, from key/value stores to document-oriented databases. The only piece that was missing in the puzzle was connectivity to a graph database: with the introduction of the Neo4j connector, the gap is now closed.

Popularized by the advent of social media, the need for efficiently storing, indexing, traversing and querying graphs of objects has become prominent in less than a decade. During this time, Neo4j has risen to the number one graph database on the market, with successful deployments across all types of industries and a strong commitment to open source.

The new connector, presented in this blog, allows Mule users to leverage the incredibly rich API that Neo4j offers with convenient configuration elements. Read on to discover a simple example built with this connector.

Janet Revell on Monday, June 10, 2013

10 Little Mule Studio Gems

1

Every so often, while using , I come across clever little gems that our team thoughtfully inserted into the product to improve usability. These gems don’t get a lot of fanfare, nor do they often warrant much attention on their own, but put together, they make for a smoother, intuitive user experience. Nearly invisible, they have become nearly indispensable to me.

 

#1 Wrap in and Extract to

At MuleSoft, we’ve been saying for years that point-to-point integration is evil. With time to market measured in minutes or hours, point-to-point integration projects measured in man-years are headed the way of the Dodo. And the no-software no-hardware model of iPaaS promises to shrink time to market even more.

But how fast can you deploy an enterprise-grade integration from scratch? We’re setting out to break preconceived notions of time to market with the 15-minute integration. Like the 4-minute mile before Roger Bannister, the 15-minute integration sounds like a myth. So is it for real?