| By Tom Lubinski | Article Rating: |
|
| December 21, 2007 12:00 PM EST | Reads: |
17,013 |
With any new technology, best practice documents are invaluable in helping developers avoid common errors and design quality systems. There is much literature already available regarding best practices for using Java Management Extensions (JMX) in monitoring and management applications. Popular J2EE application servers, such as BEA WebLogic and JBoss, have used JMX for years to manage and monitor the health and status of their many components.
These large-scale systems were built using an early version of Java (1.4) and add-in libraries of JMX classes. The extra steps involved in using JMX limited its use to systems in which the benefits of exposing monitoring and management information outweighed the cost of developing and supporting the additional code - JMX was simply not in common use.
Published December 21, 2007 Reads 17,013
Copyright © 2007 SYS-CON Media, Inc. — All Rights Reserved.
Syndicated stories and blog feeds, all rights reserved by the author.
More Stories By Tom Lubinski
Tom Lubinski founded SL Corporation in 1984 and is currently the company's president and CEO. He has been instrumental in developing SL's Graphical Modeling System software and Enterprise RTView, a real-time monitoring, analytics and visualization platform. Since founding the company, he has been involved in thousands of successful customer deployments of real-time visibility solutions. Prior to starting SL Corporation, Tom attended the California Institute of Technology and developed a substantial consulting practice specializing in object-oriented programming and graphical visualization systems. He has over 30 years of experience in the development of computer hardware systems and software applications.

