Hi,

I'm working on a very complex software project design. For my project, a monitoring tool will be crucial ; that's why I'm trying to understand what JMX is. But, I did not find any document explaining what JMX is in reality.

I have three crucial questions :

1) What JMX is in reality ? Do someone know concrete and real situations where JMX has been used and How ?

2) What really is the difference between MBeans and EJBs ?

3) Could I use JMX wnhen in my architecture when there is 50% J2EE and 50% .NET ?

Thanks in advance for any helpful feedback.

 

 

JMX is a technology that lets you implement management interfaces for
Java application.
The Management Interface is composed of named objects - called MBeans
(Management Beans). MBeans are registered with a name in an MBeanServer.
The content of the MBeanServer can then be exposed through various
protocols, implemented by protocol connectors, or protocol adaptors.

A protocol connector (e.g. the JMX RMI Connector) exposes the MBeans
as they are - so a remote client sees the same model than a local client.
A protocol adaptor (e.g. an SNMP adaptor) performs (or provides hooks to
let you perform) a model mediation - to adapt the model to what a client
of that protocol (e.g. SNMP Manager) would expect to see.

Today there is one standard connector defined for JMX - which is the
RMI Connector, and comes in two flavors: RMI/JRMP and RMI/IIOP.
There's also a JMX WebServices Connector in the making - which is being
defined by JSR 262.
http://www.jcp.org/en/jsr/detail?id=262
https://ws-jmx-connector.dev.java.net

There are also a number of non-standard connectors, either free or commercial
that have been implemented by the community.

More on JMX:
http://blogs.sun.com/jmxetc/entry/looking_for_jmx_overview_examples



You will find more on tools/products using JMX on the JMX Home Page:
http://java.sun.com/products/JavaManagement/index.jsp

Among other things, JMX is used today to manage the JVM itself. It is also
widely used in the management of application servers.
See:
http://java.sun.com/j2se/1.5.0/docs/tooldocs/index.html#manage
http://java.sun.com/developer/technicalArticles/J2SE/jconsole.html
http://weblogs.java.net/blog/mandychung
Understanding JMX Technology
http://java.sun.com/developer/EJTechTips/2005/tt0222.html#1
Getting Started with Java Management Extensions (JMX): Developing Management and Monitoring Solutions
http://java.sun.com/developer/technicalArticles/J2SE/jmx.html
Managing and Monitoring Web Services in Project GlassFish
http://developers.sun.com/prodtech/appserver/reference/techart/ws_mgmt.html
Using Custom MBeans to Extend the GlassFish Administration System
http://java.sun.com/developer/EJTechTips/2006/tt0327.html#2


An EJB lives in an Application Server container. It usually implement business
logic. An MBean lives in an MBeanServer, and usually implement management
logic (configuration, monitoring, etc)...


I am not a .NET user so I'm afraid I can't provide much advice here.
It may depends on the means you have to reach out for your .NET resources
from within your Java/JMX application. If you know how to get at your .NET
resources from Java, then it should be easy to expose them through JMX.

hope this helps,
-- daniel
JMX, SNMP, Java, etc...
http://blogs.sun.com/jmxetc


Message was edited by:
dfuchs: see also http://blogs.sun.com/jmxetc/entry/what_is_jmx