On Fri, 16 Nov 2001 20:54, Gerhard Froehlich wrote:
> Sal Peter,
>
> >JMX JMX JMX ;)
> >
> >Write an agent for this and you are all good to go. I will talk more of
> > this soon when I have time to fully do a brain dump.
>
> I just downloaded the JMX Api Spec. But I didn't really
> get the point of this stuff. How can you use this stuff.
JMX is an api for managing components. It includes interfaces and rules for
describing how attributes can be read/writen on components and operations
performed on them. It also has an interface to describe how components can
generate periodic events and so forth.
The idea is that you create objects using this API then register them with a
MBeanServer. The MBeanServer is responsible for managing them via some
mechanism or by exporting a management interface to an Agent. The agent gets
to list beans, change attributes, perform operations and listen for events.
Why use JMX? Mainly as it is a standard. Theres definelty some warts on the
API but overall it isn't that bad and it is a standard. Quite a few
application frameworks are working towards being managed by it. IIRC there is
already a few servlet engines that are manageable by it, ejb servers and
general application servers.
I suspect/hope that in the future there will be a nice generic management
console that you could plug arbitrary components into. Theres already a few
nice management interfaces about I here. A few people have said nice things
about Jonas's servlet interface. I plan to have a look at that as soon as I
have the cycles.
Anyways JMX is good because it will have a lot of interoperable servers
workable via it ;)
--
Cheers,
Pete
----------------------------------------
"Liberty means responsibility. That is
why most men dread it." - Locke
----------------------------------------
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
