Aspire :: BEG Server management with JMX
This section describes the management of the BEG server with JMX.JMX (Java Management eXtension) is the de-facto standard for managing and for monitoring Java applications and middlewares.The management is composed of 2 parts
- MBean which are probes to manage/monitor the BEG elements and its extensions (sensors, ...).
- consoles
1 BEG MBeans
The BEG can be managed with the following MBeans:org.ow2.aspirerfid:type=beg,name=server
(classorg.ow2.aspirerfid.beg.server.mbean.BEGServer
) provides general information about the Serverorg.ow2.aspirerfid:type=beg,name=begspec
(classorg.ow2.aspirerfid.beg.server.mbean.BEGSpec
) manages BEGSpec (add, remove)
2 Consoles
2.1 VisualVM plugin for Aspire BEG Server
The console uses to manage the ALEServer is the standard VisualVM with the Aspire BEGServer pluginThe Aspire BEGServer plugin gathers in one panel the main operations available on the 2 MBeans previously described. Additionnal plugins can completed the management of the host :- OSGi plugin (bundles and shell)
- Tomcat
- Glassfish (which is also based on Felix since the version 3)