Aspire :: ALE Server management with JMX

The ALE Server had 2 profiles

  • Tomcat profile : the ALEServer war is deployed in the Tomcat web container
  • OSGi profile: the ALEServer bundle is deployed in the Felix OGSi container with PaxWeb. Extra libraries and DLL/SO can be deployed dynamically without rebooting the server. This profile includes also sensors drivers deployed as bundles.
This section describes the management of the ALE server profiles (with and without OSGi) 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 ALEServer elements and its extensions (sensors, ...).
  • consoles

1 ALEServer MBeans

The ALEServer can be managed with the following MBeans:

  • org.ow2.aspirerfid:type=aleserver,name=server (class org.ow2.aspirerfid.ale.server.mbean.AleServer) provides general information about the ALEServer
  • org.ow2.aspirerfid:type=aleserver,name=lrspec (class org.ow2.aspirerfid.ale.server.mbean.LRSpec) manages LRSpec (add, remove)
  • org.ow2.aspirerfid:type=aleserver,name=ecspec (class org.ow2.aspirerfid.ale.server.mbean.ECSpec) manages ECSpec (add, remove)
  • org.ow2.aspirerfid:type=aleserver,name=sensor (class org.ow2.aspirerfid.ale.server.mbean.Sensor) provides informations on sensors activated on the OSGi part of the ALEServer. Remark: This MBean is activated only with the OSGi profile.

2 Consoles

2.1 VisualVM plugin for Aspire ALE Server

The console uses to manage the ALEServer is the standard VisualVM with the Aspire ALEServer plugin

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

jvisualplugin-aleserver-1.jpg

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)

3 Misc

*More documentation on the VisualVM ...