As an IT professional, have you ever been in a situation where you know something is broken, but you can’t manage to spot where it is coming from?
It is frustrating and quite time-consuming. You can try to use “divide and conquer” to determine the root cause. Step by step, you reduce the problem space until you isolate the origin of the issue. Yet, in most cases, you still don’t fully know what complex chain of events led to the pain.
I am excited to announce a new guide format for content that helps make understanding Anypoint Platform and implementing typical integrations patterns much easier. With Anypoint Platform, an organization can not only integrate any two systems together, but can also deploy, and manage those applications all from within a single platform.
The goal of these guides is to teach you — the developer — how to wield the platform and gain a meaningful understanding on how to achieve success with your own projects.
In the previous blog post of this series on C4E, I discussed using an API-led approach to build software applications. The C4E practice encourages reuse of resources, collaboration with third-party developers, and frequent direct interaction with business owners. During the initial discovery phase, the team recognizes the opportunity to develop a System API that provides an endpoint for retrieving data from a lookup list. The System API also allows for the list to be replaced and updated.
I have created a Mule application that pings URLs to ensure that the URLs are up. And if the URL is down for one reason or another, then the Mule application is capable of sending out an email notification. At the time of this writing, the Mule application could send out an email notification,
This is a guest blog from a member of our developer community. Dr. Roger Butenuth is a Senior Java Consultant at codecentric, he has been using Anypoint Platform for five years, with projects ranging from building simple SOAP routing/transformation to introducing the API-led approach to a Fortune 500 company.
Building Mule applications differs from coding in Java. Instead of typing all your code (with a lot of CTRL+space completion),
In an earlier blog post, we talked about how Anypoint Exchange has evolved in the November 2017 release, to make it easier for consumers to discover, learn, test and consume API assets. In this blog, we will talk about latest features added to API Manager and how they tie with Anypoint Exchange to help users better manage and govern their API assets.
We’re happy to announce the release of MuleSoft’s Ideas Portal – where any user with a support login for Anypoint Platform can post new product enhancement ideas or upvote any existing ideas submitted by others in the community. We are excited to hear from you!
As part of the official release, we’ve reviewed over 300 enhancement requests and are moving them into the Ideas Portal. Customers who created these enhancement requests will receive emails from our support team so that you can start to follow your post!
Zuora has been offering three different types of API: REST API, SOAP API and AQuA API. It is believed that majority of Zuora customers use the SOAP API to integrate with Zuora because of the breadth of its API. (MuleSoft is using the SOAP API internally!) While MuleSoft offered the Zuora Connector based on SOAP API, we started to hear from customers that some tasks could be done easily with AQuA API and Zuora is starting to recommend that customers use the AQuA API instead.
We all know how powerful Dataweave Transform Message component is. This is such a powerful template engine that allows us to transform data to and from any format (XML, CSV, JSON, Pojos, Maps, etc. basically ).
So if we need to transform we need a Dataweave component in our flow. But wait! Dataweave also provides us a function called Dataweave function that helps us to execute Dataweave language outside a Dataweave transform component.
With MongoDB as one of the most popular NoSQL databases, we are excited to announce the release of our MongoDB Connector v4.2.0. This version includes improvements in connector configuration and support for batch/bulk operations. Let’s walk through an example of using the bulk operation (Bulk.insert()) using the MongoDB Connector v4.2.0.
Since v2.6, MongoDB has supported bulk operations.
MuleSoft provides the most widely used integration platform for connecting any application, data source or API, whether in the cloud or on-premises. With Anypoint Platform®, MuleSoft delivers a complete integration experience built on proven open source technology, eliminating the pain and cost of point-to-point integration. Anypoint Platform includes CloudHub™ iPaaS, Mule ESB™, and a unified solution for API management™, design and publishing.