OW2 Consortium
Search OW2 Mail Archive: 

Advanced Search - Powered by Google


Mail Archive Home | clif List | Febuary 2008 Index

<--  Date Index  --> <--  Thread Index  -->

[clif] Re: Clif and JMX


Loris Bouzonnet wrote:
Hello,
I don't want to use JMX to define probes, but to retrieve the data of a  ProbeEvent with for example MBeanCmd.
So, your need is to use CLIF probes through JMX, right? As probes are Fractal components, Fractal JMX will expose their methods.  Consider these ones from interface DataCollectorAdmin:
  • getStat() will return a long[] with all moving statistical values
  • getLabels() will give you a String[] with human-readable names for these values.
The ProbeEvent objects can be retrieved only from the centralized Storage component, once a test run is complete and after collection, through the StorageRead component. If you want to get the ProbeEvent objects when and where they are generated, you may insert a new component as a front-end to the Data Collector sub-component of the probe component, to do whatever you need with the ProbeEvent objects. You may also change the Data Collector component. For both solutions, you may have to modify Blade.fractal ADL definition in package org.objectweb.server.lib.

Regards,
-- Bruno.

Best regards,
Loris

Bruno Dillenseger a écrit :
Loris Bouzonnet wrote:
Hello,
I'm asking how to retrieved with JMX the collected data. I don't see MBeans, perhaps should use Fractal JMX ?
Could you give some tips ?
Best regards,
Loris
Hello,

I'm not sure I accuratelly understand your need:
- if you want to monitor some resource through a CLIF probe using JMX standard, you will have to define your own probe using the sample JMX probe provided in directory src/org/objectweb/clif/probe/jmx_jvm.
- if you want to manage the CLIF infrastructure's components via JMX, then Fractal JMX is the solution.

Does this answer your question?
Do you need more details?




<--  Date Index  --> <--  Thread Index  -->

Reply via email to:

Powered by MHonArc.

Copyright © 2006-2007, OW2 Consortium | contact | webmaster.