In MuleSoft you have the possibility to configure autodiscovery. The autodiscovery feature allows a mule runtime to be paired during deployment with the API Management portal. After you have paired the application you have the ability to enforce policies and have access to tracking information.
This feature is pretty well documented on how to configure autodiscovery but sometimes you can get in trouble configuring this feature. This can especially be true when you need to connect to the EU control plane instead of the default US management plane.
Continue reading “Troublehooting mule autodiscovery issues”
With the Mule Maven plugin you have the possibility to configure Key/Value pairs. There’s no real documentation about how you can use this feature.
But these settings can be very handy for setting up CI/CD (Continous Integration / Continous Development).
Continue reading “MuleSoft Maven plugin settings”
This is a simple usecase where you want to expose an SOAP endpoint in Mule and make sure it is under management of the MuleSoft AnyPoint Platform.
The normal workflow is to create a RAML specification in the design center and fine-tuned the specification through the mocking service. After you are satisfied with the specification you can go to the management center and in the API Manage section you can add your newly created application.
With a SOAP/WSDL application the workflow is slightly different.
Continue reading “Bringing an SOAP API under Management in Mule”