Java Management Extensions (JMX) is a Java technology that supplies tools for managing and monitoring applications, system objects, devices (e. g. printers) and service oriented networks. Those resources are represented by objects called MBeans (for Managed Bean). In the API, classes can be dynamically loaded and instantiated. Managing and monitoring applications can be designed and developed by Java Dynamic Management Kit.

JMX 1.0, 1.1 and 1.2 were defined by JSR 003^[1] of the Java Community Process. As of 2006, JMX 2.0 is being developed under JSR 255.^[2] The JMX Remote API 1.0 for remote management and monitoring is specified by JSR 160.^[3] An extension of the JMX Remote API for Web Services is being developed under JSR 262.^[4]

Adopted early on by the J2EE community, JMX has been a part of J2SE since version 5.0. It is a trademark of Sun Microsystems, Inc.

Contents 1 Architecture 2 Managed Bean 2.1 Types 3 Support 4 See also 5 References 6 Books 7 External links

Architecture

JMX is based on a 3-level architecture:

• The Probe level contains the probes (called MBeans) instrumenting the resources. Also called the Instrumentation level.
• The Agent level, or MBeanServer, is the core of JMX. It is an intermediary between the MBean and the applications.
• The Remote Management level enables remote applications to access the MBeanServer through Connectors and Adaptors. A connector provides full remote access to the MBeanServer API using various communication frameworks (RMI, IIOP, JMS, WS-* …), while an adaptor adapts the API to another protocol (SNMP, …) or to Web-based GUI (HTML/HTTP, WML/HTTP, …).

Applications can be generic consoles (such as JConsole^[5] and MC4J^[6]), or domain-specific (monitoring) applications. External applications can interact with the MBeans through the use of JMX connectors and protocol adapters. Connectors are used to connect an agent with a remote JMX-enabled management application. This form of communication involves a connector in the JMX agent and a connector client in the management application.

Protocol adapters provide a management view of the JMX agent through a given protocol. Management applications that connect to a protocol adapter are usually specific to the given protocol.

Managed Bean

A managed bean - sometimes simply referred to as an MBean - is a type of JavaBean, created with dependency injection. Managed Beans are particularly used in the Java Management Extensions technology. But, with the Java EE 6 specification provides for a more detailed meaning of a managed bean.

The MBean represents a resource running in the Java virtual machine, such as an application or a Java EE technical service (transactional monitor, JDBC driver, etc.). They can be used for getting and setting applications configuration (pull), for collecting statistics (pull) (e.g. performance, resources usage, problems) and notifying events (push) (e.g. faults, state changes).

Java EE 6 provides that a managed bean is a bean that is implemented by a Java class, which is called its bean class. A top-level Java class is a managed bean if it is defined to be a managed bean by any other Java EE technology specification (for example, the JavaServer Faces technology specification), or if it meets all of the following conditions:

1. It is not a non-static inner class.
2. It is a concrete class, or is annotated @Decorator.
3. It is not annotated with an EJB component-defining annotation or declared as an EJB bean class in ejb-jar.xml.
4. It has an appropriate constructor. That is, one of the following is the case:
   • The class has a constructor with no parameters.
   • The class declares a constructor annotated @Inject.

No special declaration, such as an annotation, is required to define a managed bean.

An MBean can notify the MBeanServer of its internal changes (for the attributes) by implementing the javax.management.NotificationEmitter. The application interested in the MBean's changes registers a listener (javax.management.NotificationListener) to the MBeanServer.

Types

There are two basic types of MBean:

• Standard MBeans implement a business interface containing setters and getters for the attributes and the operations (i.e., methods).
• Dynamic MBeans implement the javax.management.DynamicMBean interface which provides a way to list the attributes and operations, and to get and set the attribute values.

Additional types are Open MBeans, Model MBeans and Monitor MBeans. Open MBeans are dynamic MBeans that rely on the basic data types. They are self-explanatory and more user friendly. Model MBeans are dynamic MBeans that can be configured during runtime. A generic MBean class is also provided for dynamically configuring the resources during program runtime.

An MXBean (Platform MBean) is a special type of MBean that reifies Java Virtual Machine subsystems such as memory pools, garbage collection, multi-threading, JIT compilation, etc.

An MLet (Management applet) is a utility MBean to load, instantiate and register MBeans in the MBeanServer from a XML description. The format of the XML descriptor is: ^[7]

 <MLET CODE = ''class'' | OBJECT = ''serfile''
   ARCHIVE = ''archiveList''
   [CODEBASE = ''codebaseURL'']
   [NAME = ''objectName'']
   [VERSION = ''version'']
 >
   [arglist]
 </MLET>

Support

JMX is supported at various levels by different vendors:

• JMX is supported by Java application servers such as OpenCloud Rhino Application Server [1], JBoss, JOnAS, WebSphere Application Server, WebLogic, SAP Netweaver Application Server, Oracle Application Server 10g and Sun Java System Application Server.
• Systems management tools that support the protocol include IBM Director,HP OpenView, Zyrion, Zenoss, Zabbix, Hyperic,Empirix OneSight and GroundWork Monitor.
• JMX is also supported by servlet containers such as Apache Tomcat.^[8]
• MX4J [2] is Open Source JMX for Enterprise Computing.
• jManage [3] is an open source enterprise-grade JMX Console with web and command-line interfaces.
• MC4J [4] is an open source visual console for connecting to servers supporting JMX

See also

• Simple network management protocol
• Network Management
• JINI

References

1. ^ JSR 003: JavaTM Management Extensions (JMXTM) Specification
2. ^ JSR 255: JavaTM Management Extensions (JMXTM) Specification, version 2.0
3. ^ JSR 160: JavaTM Management Extensions (JMX) Remote API
4. ^ JSR 262: Web Services Connector for Java Management Extensions (JMX) Agents
5. ^ Using JConsole to Monitor Applications
6. ^ MC4J is a project to create management software for J2EE application servers and other Java applications.
7. ^ "MLet (Java 2 Platform SE 5.0)". Sun Microsystems. http://java.sun.com/j2se/1.5.0/docs/api/javax/management/loading/MLet.html. Retrieved 2008-06-22. 
8. ^ Apache Tomcat 6.0: Monitoring and Managing Tomcat (Tomcat manual)

Books

• J. Steven Perry: Java Management Extensions, O'Reilly, ISBN 0-596-00245-9
• Marc Fleury, Juha Lindfors: JMX: Managing J2EE with Java Management Extensions, Sams Publishing, ISBN 0-672-32288-9
• Jeff Hanson: Connecting JMX Clients and Servers: Understanding the Java Management Extensions, APress L. P., ISBN 1-59059-101-1
• Benjamin G Sullins, Mark B Whipple : JMX in Action: You will also get your first JMX application up and running, Manning Publications Co. 2002, ISBN 1-930110-56-1

External links

• JMX on java.sun.com
• JMX at JBoss.com
• JSR 255 (JMX 2.0)
• JSR 3 (JMX 1.0, 1.1, and 1.2)

Articles

• "Enabling Component Architectures with JMX" by Marc Fleury and Juha Lindfors
• "Introducing A New Vendor-Neutral J2EE Management API" by Andreas Schaefer
• "Java in the management sphere" by Max Goff
• "Managing J2EE Systems with JMX and JUnit" by Lucas McGregor
• JMX/JBoss - The microkernel design
• JMX and jManage
• Sun Java Overview of Monitoring and Management
• [5]