JMX architecture

[sysuser1]

Hello,

I was wondering if anyone of you can help me understand the architecture of JBOSS. To my understanding JBOSS runs on top of JMX -- the components that make up JBOSS all register with a JMX MBeanServer. What isnt clear to me is how do the components that register with the MBeanServer communicate wit each other. Is JMX simply there to provide a Context, and components find each other via JNDI, or does JMX play a role in how components find and talk to each other? Can anyone please shed some light?

Thanks in advance
- Reed

[raja05]

The Registry plays a key role in that you can access any component thats registered with the MBeanserver. So for example, im in a deployer mbean and i want to access the Transaction Service, all i need to know is the object name of the Tx Service and i ask the Registry to get the object.
This also allows for effective administration in that you can selectively enable/disable any component you want using the admin console, which is a reflection of the all the Mbean registered with the server.

-Raj