Page History

...

This section discusses the Geronimo kernel. Before getting into the higher level overview of the Geronimo architecture as a whole, it's important to understand the Geronimo kernel, since it is critical to it's architecture. Through the kernel, modules in Geronimo can communicate with the management utilities while being loosely coupled and not tied to JMX. This loose coupling that the kernel provides also makes testing much easier, and allows dependency management. The kernel keeps track of the various GBeans in the system along with the various dependencies, references to other GBeans, attributes and methods that the GBeans provide. Image Removed
. Below is a high level overview of the Geronimo kernel:

Image Added

The above diagram is a basic a layout of how the Kernel component works. The Geronimo Console is a web based way to start/stop applications, change JMS information etc. In addition to the Geronimo console, this could be some custom written tool, or some other J2EE management software. If a user wanted to stop an application , for example, using the Geronimo Console, the user would log into the web console and select the application to stop. When the action to stop the application occured, the web console wouldn't access Tomcat directly. Instead the web console would communicate with query the kernel for the Tomcat GBean and then the kernel would reflectively execute the appropriate stop function in Tomcat. Note that this allows testing of the web console, the kernel and Tomcat separately from each other. Also note that the Kernel module is accessed via the Kernel interface. All of the operations on the GBean occur via calls to an implementation of the Kernel interface allowing the implementation details of the kernel to change with minimal impact to the system. Behind the scenes, the BasicKernel class that implements the Kernel interface employs the assitance of many other classes, but these are hiddent behind the Kernel interface.

...

...