Onboarding new employees in an organization has become a major headache for IT teams in every industry. With the advent of cheap cloud applications and decentralized software procurement decisions, users have access to an ever-growing number of applications to help them in their daily activities.
A somewhat “hidden feature” of the Mule Maven Plugin is the ability to use stored encrypted Anypoint user credentials in deployments. Normally, when deploying an application using a deployment strategy, the user either sets plain text credentials in the application’s POM, or injects them into the plugin configuration through the command line, or sets them through a property.
Mule applications and deployments can be fully managed using Maven. In the development phase, Anypoint Studio makes it easy to manage your application dependencies using Maven. For Deployment tasks, Mule provides a Maven plugin that helps automate the application deployment to different target runtime environments such as Standalone, CloudHub, ARM, Cluster, and more.
We recently announced the GA release of Mule 4 and Studio 7, a major evolution of the core runtime behind Anypoint Platform. Over the past few months, we’ve discussed DataWeave, streaming, and building flows quickly and easily. Recently, we demoed these capabilities in the Mule 4 webinar, and we wanted to share this demo through this blog post!
One of the more challenging aspects of integration work is dealing with various security protocols. This holds true both as a consumer of a secured service and as a producer of a service that must enforce the security protocol.
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),
This post was written by one of the stars in our developer community, Rakesh Kumar Jha.
As a MuleSoft Certified Architect, Designer and Developer, I recently worked on API implementations for one of our clients using MuleSoft’s CloudHub. One common feature that we used across our APIs implementations is reading a properties file in Mule flows.
The Mule 4 Release Candidate is here and, with it, the updated version of the batch module!
The batch module was first introduced in Mule 3.5 and it aims to simplify integration use cases where basic ETL functionality is needed. If you’re unfamiliar with it, I recommend you look at this post before continuing. If you are already old friends with batch, then keep reading for a breakdown of all the changes!
There’s a brand new Mule 4 Anypoint Connector for Database (DB) that you can use to connect to any relational Database engine. Unlike other connectors such as File or FTP, this connector has a pretty similar UX compared to the one in Mule 3.x, with some considerable improvements, including: