Main.Documentation E2EMngmt-ALEServer-JMX en 0 Main.Documentation.E2EMngmt xwiki:XWiki.donsez xwiki:XWiki.donsez xwiki:XWiki.donsez 1275921062000 1277715615000 1277715615000 1.30 jvisualplugin-aleserver-1.jpg 107064 xwiki:XWiki.kievgama 1276780662000 1.2 1 Aspire :: ALE Server management with JMX ---- #toc("" "" "true") ---- 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)>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 ALEServer elements and its extensions (sensors, ...). * consoles 1.1 ALEServer MBeans The ALEServer can be managed with the following MBeans: * <code>org.ow2.aspirerfid:type=aleserver,name=server</code> (class <code>org.ow2.aspirerfid.ale.server.mbean.AleServer</code>) provides general information about the ALEServer * <code>org.ow2.aspirerfid:type=aleserver,name=lrspec</code> (class <code>org.ow2.aspirerfid.ale.server.mbean.LRSpec</code>) manages LRSpec (add, remove) * <code>org.ow2.aspirerfid:type=aleserver,name=ecspec</code> (class <code>org.ow2.aspirerfid.ale.server.mbean.ECSpec</code>) manages ECSpec (add, remove) * <code>org.ow2.aspirerfid:type=aleserver,name=sensor</code> (class <code>org.ow2.aspirerfid.ale.server.mbean.Sensor</code>) provides informations on sensors activated on the OSGi part of the ALEServer. Remark: This MBean is activated only with the OSGi profile. 1.1 Consoles 1.1.1 VisualVM plugin for Aspire ALE Server The console uses to manage the ALEServer is the standard [VisualVM>https://visualvm.dev.java.net] with the Aspire ALEServer plugin The Aspire ALEServer plugin gathers in one panel the main operations available on the 4 MBeans previously described. {image:jvisualplugin-aleserver-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] <h2 class="heading-1"><span id="HAspire3A3AALEServermanagementwithJMX">Aspire :: ALE Server management with JMX</span></h2> <hr class="line"/> <ul> <li><a href="#HALEServerMBeans">1 ALEServer MBeans</a> <li><a href="#HConsoles">2 Consoles</a> <ul> <li><a href="#HVisualVMpluginforAspireALEServer">2.1 VisualVM plugin for Aspire ALE Server</a> </ul> <li><a href="#HMisc">3 Misc</a> </ul> <hr class="line"/><p class="paragraph"/>The ALE Server had 2 profiles <ul class="star"> <li>Tomcat profile : the ALEServer war is deployed in the Tomcat web container</li> <li>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.</li> </ul>This section describes the management of the ALE server profiles (with and without OSGi) with JMX.<p class="paragraph"/><span class="wikiexternallink"><a href="http://en.wikipedia.org/wiki/Java_Management_Extensions">&#74;MX (Java Management eXtension)</a></span> is the de-facto standard for managing and for monitoring Java applications and middlewares.<p class="paragraph"/>The management is composed of 2 parts <ul class="star"> <li>MBean which are probes to manage/monitor the ALEServer elements and its extensions (sensors, ...).</li> <li>consoles</li> </ul><h3 class="heading-1-1"><span id="HALEServerMBeans">1 ALEServer MBeans</span></h3><p class="paragraph"/>The ALEServer can be managed with the following MBeans: <ul class="star"> <li><code>org.ow2.aspirerfid:type=aleserver,name=server</code> (class <code>org.ow2.aspirerfid.ale.server.mbean.AleServer</code>) provides general information about the ALEServer</li> <li><code>org.ow2.aspirerfid:type=aleserver,name=lrspec</code> (class <code>org.ow2.aspirerfid.ale.server.mbean.LRSpec</code>) manages LRSpec (add, remove)</li> <li><code>org.ow2.aspirerfid:type=aleserver,name=ecspec</code> (class <code>org.ow2.aspirerfid.ale.server.mbean.ECSpec</code>) manages ECSpec (add, remove)</li> <li><code>org.ow2.aspirerfid:type=aleserver,name=sensor</code> (class <code>org.ow2.aspirerfid.ale.server.mbean.Sensor</code>) provides informations on sensors activated on the OSGi part of the ALEServer. Remark: This MBean is activated only with the OSGi profile.</li> </ul><h3 class="heading-1-1"><span id="HConsoles">2 Consoles</span></h3> <h4 class="heading-1-1-1"><span id="HVisualVMpluginforAspireALEServer">2.1 VisualVM plugin for Aspire ALE Server</span></h4> The console uses to manage the ALEServer is the standard <span class="wikiexternallink"><a href="https://visualvm.dev.java.net">&#86;isualVM</a></span> with the Aspire ALEServer plugin<p class="paragraph"/>The Aspire ALEServer plugin gathers in one panel the main operations available on the 4 MBeans previously described.<p class="paragraph"/> <img src="/xwiki/bin/download/Main.Documentation/E2EMngmt-ALEServer-JMX/jvisualplugin-aleserver-1.jpg" height="600" alt="jvisualplugin-aleserver-1.jpg" /><p class="paragraph"/><span class="wikiexternallink"><a href="https://visualvm.dev.java.net/plugins.html">&#65;dditionnal plugins</a></span> can completed the management of the host : <ul class="star"> <li>OSGi plugin (bundles and shell)</li> <li>Tomcat</li> <li>Glassfish (which is also based on Felix since the version 3)</li> </ul><h3 class="heading-1-1"><span id="HMisc">3 Misc</span></h3> *<span class="wikilink"><a href="/xwiki/bin/view/Main.Documentation/E2EMngmt-VisualVM">More documentation on the VisualVM ...</a></span><p class="paragraph"/><p class="paragraph"/>