Once you develop your own integration solution, you will need to run the app either on Anypoint Cloud or on customer-hosted runtime.
Things have changed. MuleSoft made AnyPoint Runtime Manager to be used both for Cloud and customer-hosted runtime management. MMC will only be supported up to 3.x runtime and will no longer be supported for 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 sockets and REST so that an external application can leverage them. When you register a customer-hosted runtime to Anypoint Runtime Manager, the Runtime Manager communicates with runtimes through these APIs.
Where Do I Get the Latest Version?
You can get the latest version of Runtime Manager Agent here.
Why Do I Need It?
Let me remind you that Anypoint Runtime Manager is not an 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 the runtime environment, and to do so, it may use different APIs later on. If Runtime Manager Agent isn't updated accordingly, you may not get the benefits of the latest Runtime Manager.
How to Apply the Update
You will need to install/update the agent following the guide here. The point is, you will need to replace files from
$MULE_HOME/bin. Take a look at my folder structure as an example.
RMA is a key component that we need to understand and keep up-to-date to manage customer-hosted environments through Anypoint Runtime Manager.