This post originated from an RSS feed registered with Java Buzz by Simon Brown. Original Post: What can JMX do for you? Feed Title: Simon Brown's weblog Feed URL: http://www.simongbrown.com/blog/feed.xml?flavor=rss20&category=java Feed Description: My thoughts on Java, software development and technology. Latest Java Buzz Posts Latest Java Buzz Posts by Simon Brown Latest Posts From Simon Brown's weblog

As I've previously mentioned, I'm presenting an in-depth tutorial on JMX entitled What can JMX do for you?...

JMX (the Java Management Extensions) is one of the lesser known jewels in the Java SE crown, and few people understand what this simple but powerful API can do for them. This tutorial presents an in-depth look at JMX and how it fits into the development of enterprise Java applications. We will be covering the following topics.

• Getting started with JMX and implementing your own MBeans.
• Using a bespoke container architecture to control application components with JMX at runtime.
• Using JMX to centralise access to core services (e.g. logging, configuration) in enterprise applications.
• Taking advantage of JMX notifications for real-time status updates.
• Options for starting, customizing and remotely exposing an MBeanServer instance.
• Integrating JMX functionality into your Spring application.
• Accessing MBeans from your application code.
• Extending JConsole functionality with the Java 6 JConsole API.
• Building your own web-based JMX dashboard to aggregate management information across multiple JVMs.

If you have not yet looked at what JMX can do for you, come along and find out.

JMX has been around for years now but, based upon my own experience of consulting on and building enterprise applications, it's not a technology that readily springs to mind when new projects are started. I think JMX has a reputation for either being (a) something that's a little dull, (b) something that's only relevant to application server vendors or (c) one of those "nice to haves" that gets the chop once budgets and deadlines enter the picture.

For me, JMX is like automated unit testing with something like JUnit - it seems like a really good idea but you can't just quite get around to using it. Once you have used it though, you become infected.

JMX is cool. Once you become infected and start to think about the other ways in which your applications can be monitored and managed you'll think it's cool too.

p.s. don't forget to enter the draw to win a free pass to QCon!