Details on the JMX Browser

Background

Before diving into the structure, make sure that these two major points are well-known :

  • The JavaBeans and JavaBean Context API. The JMX Browser is heavily based on a hierarchic JavaBean model, that access the external resources via BeanContext services. For more informations about JavaBean and the Glasgow specifications, click here .
  • The JMX API. The JMX API allows the development of modular server based on a central JMX spine where Managed Bean are connected to. It allows a great flexibility and reusability of the Managed Bean. For more informations about JMX API, click here .

The BeanContext Model

The JMX Browser takes a snapshot of the JMX Server structure by build a JavaBean hierarchy that mirrors the JMX Server as illustrated by the following graphic :

JMX to BeanContext

Two services are available for the children of the BeanContext Container :

  • Connection Service that hides the JMX Server calls.
  • Notification Service that register and catch the notification send by the JMX Server.
Every nested JavaBean can access these services to use them. The BeanContext Container is also responsible to locate any required MBean by its canonical name.

Swing-based Proxies

To Do.

Web-based Proxies

To Do.