As I said before we were asked to check out the new Management Console of Mule. In this post I will show the steps I took to get the console up and running and the first results of the evaluation.
- The first thing I had to fix was the fact that the Management Console only works with the Enterprise Edition. Luckily there is a 30 days trial available of the Enterprise Edition here, so I started by downloading that one.
- Next issue was that I wanted to deploy my Mule application as a WAR on a Tomcat instance. To build this WAR I use Maven (of course) so I had to made the Enterprise Edition jars available as dependencies in my repository. Luckily this issue is foreseen by MuleSoft as the Enterprise Edition comes with a script called ‘populate_m2_repo’ that adds all jars to the local repository. After running this script I was able to build my WAR file packed with the Mule EE jars.
- Next I had to add the Mule Agent to my war. To make this possible I added the agent.jar also to my local Maven repository by running the command:
mvn install:install-file -DgroupId=org.mule.console -DartifactId=mmc-agent -Dversion=2.2.5 -Dpackaging=jar -Dfile=mmc-agent-2.2.5-ea.jar
- With the agent in my repository I just had to add the following dependencies to the pom of my WAR:
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21
<dependency> <groupId>org.mule.console</groupId> <artifactId>mmc-agent</artifactId> <version>${mule.version}</version> </dependency> <dependency> <groupId>com.mulesource.muleesb</groupId> <artifactId>mule-core-ee</artifactId> <version>${mule.version}</version> </dependency> <!-- 3rd party libs --> <dependency> <groupId>quartz</groupId> <artifactId>quartz</artifactId> <version>1.5.2</version> </dependency> <dependency> <groupId>org.springframework</groupId> <artifactId>spring-webmvc</artifactId> <version>${spring.version}</version> </dependency>
By adding these dependencies my WAR will also contain the Mule Agent that is necessary for the console to monitor my Mule application.
- The next step was deploying the Management Console to the Tomcat server. This is as simple as uploading the WAR to the ‘webapps’ directory. And after Tomcat has unpacked it and started it you can access it with the following address in your browser ‘http://localhost:8080/mmc-server-2.2.5-ea/’ (of course only if you didn’t change any defaults) and you get the login screen:
After login in with ‘admin/admin’ you can add your Mule application as a server:
This gives you a lot of information about the machine/processes running that application:
and
Although all this (technical) information is nice to have I think one of the main benefits is found on the ‘Services’ tab where you can audit, pause, start, etc. your individual service:
For each service you can enable the ‘audit’ option so each incoming and outgoing message is logged:
Although it is an Early Access release, I haven’t found any issue with it, but maybe that’s because I only have done some basic routines :-) We will certainly look further into this and I expect the next build of the EA (with more functionality like ‘alerts’) to become available next week. I’ll keep you informed!
