Accessing MMC as service( for beginner )

Before we start, we will actually look into what MMC really is.

Mule Management Console (MMC) which can be said as centralizes management and monitoring functions for all our Mule ESB Enterprise deployments, no matters whether they are running as standalone instances, as a cluster, or embedded in application servers.

MMC is can be said as an enterprise management and monitoring tool designed specifically for Mule ESB instances.

It provides the comprehensive set of functionality for managing and monitoring running Mule instances, Mule clusters, applications within Mule instances, and the flows within those applications.

Reference :- https://docs.mulesoft.com/mule-management-console/v/3.7/

How can we access Mule MMC as a service???

Management Console (MMC) expose REST API that provides a way for us to programmatically access all the functionalities of MMC. The functionalities includes:-

• Create an applications • Register new servers and manage existing servers, including restarting

servers. • Deploy a new version of our application• Delete our application• Getting statistics/details about our application

Accessing MMC with REST Api

So, if we start out Mule standalone on premises server and run our mmc , we will find that we can access all the mmc task by accessing the REST api it expose. For example, below you can find the REST api is used to check all the details of the server. For example, if our server is configured on port 8080, we can use the following url to access the details of the server -

You can see, details like deployment, deployment id, application, server details are visible here.

Using the following api, that includes the deployment id as a parameter, we can view the details of a specific deployment:-

Now, using following api, we can create an deployble application in our Mule Standalone server, which will be ready for deployment. You can see that we are putting server name and application name in our JSON POST request.

Now, if we check our Mule mmc, we will found the application is created and ready for deployment.

Now, using the following api, we can deploy our application on the server using the deployment id as parameter.:-

If we check back in our mmc, we will find that the api has deployed the application successfully on the server.

Now, using the following api, we can undeploy our application on the server using the deployment id as parameter.:-

If we check back in our mmc, we will find that the api has been undeployed from the server.

Now, using the following api, we can redeploy our application on the server that was undeployed using the deployment id as parameter.:-

If we can see in mmc portal, the application is redeployed from the undeployed state and running .

Now, using the following api, we can delete our application on the server completely. Deployment id is required as a parameter in url :-

If we check our mmc, we will find that the api has been deleted completely from the server. There is no application present.

Conclusion…..

So we can see it is very very easy to access the functionality of our Mule mmc on Mule Standalone server using the REST api exposed by it. We can create an application, delete and application, deploy an application, undeploy the application, redeploy it, list the deployed applications, server details/statistics and many more.

So at the end I can only say that, let’s spread our knowledge and expand our Mule community.

Thank You