Anypoint Studio, as a development tool, comes with a steep learning curve - it’s essentially a rebranded version of Eclipse, with a lot of custom Java packages (there are a lot for the Mulesoft server) and a package manager pointing at the Exchange repo.
Putting together a Mulesoft application, using the ’low code’ designer and DataWeave is easy enough, though I haven’t done any advanced data transformations yet. Currently it relays data from another Mulesoft API to an external service in a different format.
Recently I was asked to look into changing the authentication method to OAuth 2.0 for an integration service. It’s something I’d done enough times in Azure to know what’s involved: The service would need an app registration, which should provide a client ID and secret, an OAuth token request stage, and modifications to include the token in the Authorization header field of whatever was originally being sent.
After a little digging, it turned out the integration was a simple batch script, running on a Windows server, and it used curl to send data to a third-party service.
It took a while to get everything set up for the Mulesoft Development course, with the following being required:
Anypoint Studio Anypoint Platform account (separate to the training account) Salesforce account Advanced REST Client (Probably wasn’t needed, because I already had Postman installed) There are a few things to be aware of:
A considerable amount of disk space is required for Anypoint Studio and the training files. I reckon it’s somewhere around 4GB.
