Don’t cha wish your openfire console was hawt like me? Don’t cha?
Introducing the openfire jmxweb plugin
I have been using java-monitor.com’s openfire probe for a while now to mange all my openfire servers for a while now and it pretty much works. The plugin and extra JMX mbeans developed by Guus der Kinderen have been very useful for checking the health on the servers. For various reasons which include the work done by Tom Evans to enable JMX for Openfire (Jetty. Mina, Hazelcast) I decided to monitor my openfire servers directly with an open JMX management console instead. I tried both jconsole and jvisualvm, but found them difficult to use with remote servers. I needed a web based console.
I have packaged hawt.io, jolokia and the openfire mbeans from the java-monitor.com probe into a new plugin called jmxweb. It uses the http-bind web service for hawt.io web console and jolokia’s REST API. To access openfire’s JMX mbeans, enable it with global property “xmp.jmx.enabled”. By default, access is secure and only to admin users. Use “xmpp.jmx.secure” to disable.
How to use
The plugin only works with latest openfire server 3.10 because of changes to mina in 3.10. I might do a backward build for openfire 3.9/3.8 if there is any interest.
I plan to release jmxweb on igniterealtime as a new openfire plugin and develop some mbeans for openfire meetings and a hawt.io plugin to manage them later on. It currently lacks the ability to accumulate jmx data on a central server like java-monitor.com over a period of time to analyse and I will look at implementing a push and store feature much later on.
I have attached the jar file for jmxweb plugin that will work with openfire server 3.9.3 and possibly below. Use at your own risk.
JmxWeb plugin now available as an Openfire plugin for version 3.10 and above
A discussion space at igniterealtime has also been created.
jmxweb.jar (6512573 Bytes)