In this blog post, we will talk about “Flow Designer,” the online component which has a wide set of features for the creation of basic integrations and to “enable” backend components by making them ready for API-led connectivity.
Flow Designer runs on the control plane and is available with the basic subscription as well as with the trial account. It enables the Citizen Integrator to create Mule applications that are deployable directly to CloudHub.
SAP provides a number of elements, data structures, and modules to enable integration with its solutions. Below is a summary of the various approaches, all of which are supported by MuleSoft’s Anypoint Platform.
We’re very excited to announce the May 2014 release of Anypoint Platform. This new release, which includes the GA release of Mule 3.5.0, provides a faster, easier way to deliver data to business applications, whether they are event-driven, real-time data or batch data. The Anypoint Platform May 2014 release also includes templates to solve the most common Salesforce integration challenges and new security certifications for CloudHub,
In this post I want to close the loop on introducing you to the last of the five initial patterns that we are basing our Anypoint Templates on. I’m sure we’ll continue creating templates and we’re going to continue discovering new data integration patterns. If you are just entering at this post, I would recommend that you look through the previous four posts to understand the other patterns.
So far, in this series, we have covered Migration, Broadcast, Bi-Directional Sync, and today we are going to cover a new integration pattern: Correlation. In an effort to avoid repeating myself, for those who are reading through the whole series, I will omit a lot of relevant information which is shared between the patterns that I have previously covered. I urge you to read at least the previous post about bi-directional sync as correlation can be viewed as a variation of bi-directional sync.
In this post I will continue talking about the various integration patterns that we used as the basis for our Anypoint Templates. The next pattern to discuss is bi-directional sync. Since bi-directional sync can be also accomplished as two, 1:1 broadcast applications combined and pointed in opposite directions, I would recommend reading my last post on the broadcast pattern before digging into this one since I will omit a lot of the same content.
Hi all, in this post I wanted to introduce you to how we are thinking about integration patterns at MuleSoft. Patterns are the most logical sequences of steps to solving a generic problem. Like a hiking trail, patterns are discovered and established based on use. Patterns always come in degrees of perfection with much room to optimize or adopt based on the needs to solve business needs. An integration application is comprised of a pattern and business use case.
Companies are looking to connect to their customers while leveraging customer data across the business to make more informed decisions. As organizations drive digital transformation initiatives to cater to today’s online consumer, there is a massive need for businesses to connect to their customer’s in an holistic way.
Most companies turn to CRM solutions to get a better view of their customers, but it’s not as simple as selecting a single CRM system.
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.