1
votes

I have a stand alone Mule Community Edition instance running an app, which I'd like to view in the Mule Management Console.

I've downloaded the MMC Trial and successfully connected to the trial's Enterprise Mule instance. When trying to add a new server on MMC, connecting to my Community Edition instance, it displays an error with Connection Refused.

Some Googling shows that it I should start the MMC Agent on that server.

How can I do that?

2

2 Answers

0
votes

To be able to connect to MMC, you need a agent running along your esb server, which is the one that sends data to MMC and receives commands such as stop/restart/etc. ESB EE runtime comes in 2 flavors: with or without the MMC agent included. In the case is not included, you can add it later as an addon. But you can't add it to a Community Edition (CE). You need the EE version, that is why the mmc trial version comes with the ee runtime trial version. So, in the case you want to test your application running along with the MMC, you have to deploy it in the Mule EE instance (you can deploy the application from MMC).

0
votes

In the first place I am not sure if Mule MMC agent working with Community Edition. As per MuleSoft MMC is an enterprise only feature.

For running an MMC Agent.

First download an MMC agent from MuleSoft (Mule Enterprise Trail will provide you with MMC and MMC Agent)

Then copy the MMC agnet zip file to Mule standalone server apps folder.

Then start Mule standalon server.

Mule starts and shows that MMC agent is deployed and running.

Then your MMC should be able to detect the server instance.

Refer to the following link for more details on MMC

http://www.mulesoft.org/documentation/display/current/Installing+the+Trial+Version+of+MMC

Hope this helps.