Consortium Activities Projects Forge Events

Aspire :: BEG Server management with JMX

1 Aspire :: BEG Server management with JMX
----
#toc("" "" "true")
----

This section describes the management of the BEG server with JMX.

[JMX (Java Management eXtension)>http://en.wikipedia.org/wiki/Java_Management_Extensions] 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.1 BEG MBeans

The BEG can be managed with the following MBeans:
* <code>org.ow2.aspirerfid:type=beg,name=server</code> (class <code>org.ow2.aspirerfid.beg.server.mbean.BEGServer</code>) provides general information about the Server
* <code>org.ow2.aspirerfid:type=beg,name=begspec</code> (class <code>org.ow2.aspirerfid.beg.server.mbean.BEGSpec</code>) manages BEGSpec (add, remove)

1.1 Consoles
1.1.1 VisualVM plugin for Aspire BEG Server
The console uses to manage the ALEServer is the standard [VisualVM>https://visualvm.dev.java.net] with the Aspire BEGServer plugin

The Aspire BEGServer plugin gathers in one panel the main operations available on the 2 MBeans previously described.

{image:jvisualplugin-begserver-1.jpg|600}

[Additionnal plugins>https://visualvm.dev.java.net/plugins.html] can completed the management of the host :
* OSGi plugin (bundles and shell)
* Tomcat
* Glassfish (which is also based on Felix since the version 3)

1.1 Misc
*[More documentation on the VisualVM ...>Main.Documentation.E2EMngmt-VisualVM]