I am excited to announce Anypoint Platform’s support for ForgeRock’s OpenAM! As with the PingFederate support that came natively with the release of the Anypoint Platform for APIs last year, our new out-of-the-box support with OpenAM is seamless and can be configured for any organization with the push of a button. Once configured with OpenAM as an external identity provider, Anypoint Platform supports two key capabilities:

Shohil Kothari on Thursday, April 23, 2015

Get Certified at CONNECT 2015


Free on-site certification exams at CONNECT!


Ensure you have the skills needed to succeed with MuleSoft

How do you know if you and your team members have what it takes to be successful with Anypoint Platform? Get your skills verified with MuleSoft’s professional accreditation testing. Whether you’re a customer, a partner, or a hands-on MuleSoft user, anyone can benefit from MuleSoft Certification Exams.

All CONNECT attendees have the option to take a Certification Exam free of charge during the event. Space is limited, so reserve your spot now! Exam descriptions are below, so take a look and be sure to submit your time preference.

Choose from four exams:

  • Associate MuleSoft Developer
  • Certified MuleSoft Developer
  • Associate API Designer with RAML
  • Associate MuleSoft Connector Developer

Upcoming webinar: So you want to set up an API strategy. Now what?

Join us for the latest installment in the MuleSoft webinar series as we sit down with Julie Craig, Research Director at Enterprise Management Associates, and Reza Shafii, Director of Product Management, MuleSoft to discuss some of the common pitfalls and questions businesses have when developing their API strategy. Craig and Shafii will talk about the essentials of an API-led approach to design, key criteria for an API management solution, and the basics of the full API lifecycle, from development to governance. Participants will hear about trends in API development and how APIs are delivering real business value to the enterprise.


In this post we’re going to continue the discussion started our last post “A sneak peek into Mule 3.7’s deepest internals” about how Mule’s registry, lifecycle and dependency injection mechanism are being overhauled in Mule 3.7. In this case, we’re going to take a deep dive into how we managed to unify the registries while keeping backwards compatibility and all the implications of such maneuvers.

IMPORTANT: If you haven’t read the first post in this series go ahead and do it now. This will be very difficult to follow otherwise. This post carries the same warning as the first one: it’s mainly intended for developers coding their own custom Mule components. If you’re the kind of person who codes their own components or finds it tasteful to leverage the low level Mule APIs and internals, then you should definitively read this series of posts. On the other hand, if you’re the kind of user which just simply uses Mule out-of-the-box and the Anypoint Studio palette gives you all you need, then you probably won’t be as excited about this long read, but it’s recommended anyway; it’s always good to know your tools.

Priya Sony on Wednesday, April 15, 2015

CONNECT 2015 is coming!


Get 20% off your ticket with special promo code: BLOG20

Whatever your role, or industry, CONNECT is the place to be.

Don’t miss the opportunity to engage in an interactive discussion with your peers around digital
transformation and learn why an API-led connectivity approach has become IT’s secret weapon at CONNECT 2015. Nearly every business priority can be enabled by IT through API-led connectivity. Whether you’re a CIO, an enterprise architect, or an IT leader, you’ll walk away with a number of innovative ways to improve and transform your business. Don’t miss the opportunity to be inspired, learn best practices, and take away practical solutions you can use today!

Mule 3.7 is approaching, and among other things we decided to put a lot of focus on the experience of the guy coding custom components (Devkit based or not). For this, the first 3.7 milestone is incorporating big changes in terms of the how Mule Lifecycle and Dependency Injection are applied.

As I said, these changes are BIG, so for clarity reasons we’ll cover them in a series of post starting with this one. Hopefully by the time 3.7 is out, you’ll already be familiar with all the new goodies at your disposal.

Twinning can be evilWhen it comes to API implementation, message “twinning” is one of those annoying pitfalls that in the worst case scenario, can lead to major problems downstream, such as duplicate orders being submitted etc. However, the client side is often not equipped to prevent duplicate messages from being sent, especially for javascript based user interface calling REST APIs, where user actions such as fat-fingering and unintentional double-clicking are virtually impossible to control.

Technology is disrupting industries, and no more so than in Healthcare where wearables, devices and the Internet of Everything (IoE) more broadly, provide the means to reframe how healthcare is delivered. These technologies are bringing hardware and software together to enable the provision of data, to both healthcare professionals and patients, and ultimately to enable better clinical decision making.

Delivering distinct solutions

healthcareIn the past, there’s been a dichotomy between hardware and software. Companies, products and engineers alike were defined by whether they fell in the hardware or software camp. IoE is blurring these lines, as Apple’s Healthkit can attest. What these technologies are achieving is a fluid flow of data between device and application; patients must seamlessly be able to enter data from their individual device into a system to be accessed by their doctors, and conversely, individualized treatment plans or fitness recommendations are sent to personal devices from a central information system. We believe that the promise of innovation can only be truly by bringing hardware and software together in this way, to deliver truly coherent and distinctive solutions.

We’re pleased to announce that for the second year in a row, Gartner has named MuleSoft a Leader in the Magic Quadrant for Enterprise Integration Platform as a Service (iPaaS). CloudHub, the cloud-based integration component of Anypoint Platform, was evaluated in the Magic Quadrant.

Ken Yagen, our vice president of products, noted, “Digital transformation requires enterprises to rapidly integrate SaaS applications and digital services from
business partners with their existing back office systems. This calls for broad API-led connectivity and deployment on a platform that seamlessly connects the cloud and traditional data centers. Gartner’s recognition is a testament to CloudHub’s leadership and significant role in an enterprise’s hybrid integration strategy.”gartner-mq-ipaas-diagram

Connect anyone, changes everything…


SAN FRANCISCO – April 1, 2015 – MuleSoft, the company that makes it easy to connect applications, data and devices for corporations, today announced a new component of its flagship Anypoint Platform™, CloudShack, a highly available, resilient, and scalable solution for connecting people, thus making the world a better place.cloudshack

Today, even lonesome hearts demand seamless and automated interactions with their mating service providers, given the ever more disruptive ambience of modern lifestyles. Constant manual finger swiping simply will not do.

By leveraging MuleSoft’s industry leading connectivity technologies, combined with our newly developed Connected Universal People Identifying Decision (CUPID™) engine, we have created an API-centric innovative dating solution that will automatically make the optimal matches for the lonely souls out there. A user can simply make a call to the CloudShack REST API, all the while remaining restful (pun intended), and CloudShack will handle the rest and return the best match. Imagine, a dating platform where all the exchange patterns are request-response, processing strategy is not just synchronous but also harmonious, and every outbound endpoint finds itself an inbound endpoint. That is CloudShack.