Things are changed. MuleSoft had made AnyPoint Runtime Manager can be used both for Cloud and Customer-hosted runtime management. MMC will only be supported up to 3.x runtime and no longer be supported from Mule 4.

Therefore, it is important to understand how Runtime Manager can be used for managing customer-hosted runtime.

What is it?

You can think of Runtime Manager Agent as the middle man between the customer-hosted runtime and AnyPoint Runtime Manager.

This agent exposes Mule APIs of a mule runtime through web socket and REST so that external application can leverage them. When you register customer-hosted runtime to Anypoint Runtime Manager, the Runtime Manger communicate with runtimes through these APIs.

Where do I get the latest?

Why do I need that latest?

Let me remind you that AnyPoint Runtime Manager is not a mmc-like tool that you install on-premise that is expected to stay the same unless you purposefully update. Runtime Manager is Live. It keeps being updated to give you better visibility of runtime environment and to do so, it may use different APIs later on. If Runtime Manager Agent doesn’t get updated accordingly, you may not get the benefits of latest Runtime Manager.

How to apply the update?

You will need to install/update the agent following the guide here. Point is, you will need to replace files from $MULE_HOME/bin. Take a look at my folder structure as an example.

Summary

RMA is a key component that we need to understand and keep it up-to-date for managing customer-hosted environment through Anypoint Runtime Manager.