No one likes doing manual and repetitive tasks, or at least we don’t. That’s how our latest integration started. I’m on the IT team here at MuleSoft, and I noticed that our field team (i.e. anyone who makes commission based pay) was generating a large number of tickets based around distribution lists/email groups. The problem was simple: there had been no existing structure; each regional VP had set up their own groups; none of those groups had consistent names so they were also impossible to find; and most of the existing groups were inaccurate. The untidy structure meant that invariably every new field employee generated at least 2-3 tickets in order to refine the groups they were a member of.
We defined the API
specification using RAML
, implemented the API
by importing the RAML
into Anypoint Studio
and deployed the implementation to mule runtime in cloud or on-premise.
We are now ready to share the API
with the developer community. Before sharing, we need to make sure that the API
is governed. Governing an API
means applying policies like rate limiting, SLA based tiering and securing API
access with industry standard protocols.
One popular way to secure APIs
(Open Authorization). OAuth
2.0 focuses on client developer simplicity while providing specific authorization flows for Web applications, desktop applications, mobile apps and Internet of Things. Here’s more
about how OAuth
Mulesoft’s Anypoint Platform
provides a policy template to implement OAuth
out of the box. In this post, we will go through the step-by-step process of configuring the OAuth
policy to enforce OAuth
on an API
It’s no surprise that business is changing dramatically. The potential afforded by digital transformation could have dramatic effects on companies’ growth, scalability, and revenue. Here are the top 5 trends that I think will have a major effect on businesses next year:
Arsenal Football Club is one of the most famous football teams in the world. It has over 100 million fans worldwide and sees its international fans as key to its further success, and wants to create amazing experiences for the fans when they come to Arsenal’s home stadium in London.
The holiday shopping season is in full swing, but this year retailers noticed that customers aren’t spending the bulk of their holiday budget on Black Friday as they have in the past. Instead, shoppers are spreading their purchases throughout the pre-Christmas period, and are shopping online, whether on desktop or their smartphones, more than in the past. This shift has made it difficult for retailers to track and learn from shoppers’ habits during the holiday season.
This blog post is a continuation of our first How To series, “APIFy your integrations,” where we started off by creating a SOAP API around a database.
Some organizations are entirely invested in either SOAP or RESTful web services. There is plenty of material already written on SOAP vs. REST, so there’s no need for us to take that on here.
I’m pleased to announce the next release of our development tools, Anypoint Studio 5.4, as well as the next version of our runtime, Mule 3.7.3. This release includes a number of great new productivity improvements for Mule developers, including a new graphical mapping tool for DataWeave, a migration assistant for DataMapper, a new, more modern look and feel, bundles MUnit 1.1, and an improved palette.
One of the challenges that fast-growing enterprises face is building an IT infrastructure that meets the needs of both today and the future. Faced with the same challenge of rapid growth at MuleSoft, we have deployed our own tool, Anypoint Platform, to decouple core systems and enable the automation of core business processes.
Mike Hamilton, the Director of IT at MuleSoft, will be presenting a webinar on December 3, 2015 at 10 AM Pacific called “Secrets from the Inside: How MuleSoft IT Uses Anypoint Platform.”
We recently introduced our HowTo blog series, which is designed to present simple use-case tutorials to help you as you evaluate Anypoint Platform. This first blog in Series 1 will show you how to insulate your backend systems like databases by exposing a system API using SOAP over HTTP. The principle behind this approach is our API led connectivity methodology, which is an evolution of SOA.
The term “SOA governance” has taken on the connotation of a select group of people coming together periodically to talk about SOA topics, establishing a policy which is dutifully documented, and then disappearing back to their ivory towers without making much impact on the business. But the notion of governance is becoming ever more important as businesses adopt SaaS technologies and initiate mobile, big data, and IoT initiatives. Suddenly those responsible for SOA policy can’t exist in their ivory towers anymore; every aspect of the business needs access to those policies, and those policies now touch everyone in the business. SOA governance therefore is evolving from a largely internal function for IT teams to one that extends to external audiences.