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 CloudHub 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, SaaS 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, HootSuite, Google 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 Salesforce.com? Look no further – follow these best practices from the dataloader.io community 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 SaaS 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.
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 Salesforce.com is a SaaS 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.
On my previous 3-part blog, I showed how Mule ESB can be used to service-enable and orchestrate traditional on-premise technologies like an Oracle database and IBM Websphere MQ. Using Mule ESB, we created a service that accessed employee information from an Oracle database table and transmitted this to IBM WebSphere MQ. An observant customer I was showing this to noticed a security flaw with how sensitive employee information was being transmitted in plain text and also asked how the employee record can be sent to SalesForce.com. This blog will show how these can be easily addressed using MuleSoft’s AnyPoint Platform. We’ll make use of the PGP encryption features from AnyPoint Enterprise Security to encrypt the data before sending it to WebSphere MQ. Then, we’ll create another message flow to retrieve this message, decrypt it and send it to SalesForce.com using the AnyPoint Connector for SalesForce.com.
Mule has a very extensive support for NoSQL 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.
Have you already tried the Visual Flow Debugger? It’s one of the new shiny features that comes with Mule Studio Enterprise 3.4. Well, if you haven’t used it yet, this post is for you:
1. Message Browsing – All the information you ever wanted, now at a click’s distance.
Before Visual Debugger, if you wanted to see the contents of the payload at each point you had to clutter your mule configuration with loggers all over the place, well, those days are over. Just put in a breakpoint et voilà!
You can also edit most values dynamically at runtime by clicking them.