Mailing-List: contact geronimo-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: geronimo-dev@incubator.apache.org
Date: Mon, 1 Sep 2003 18:09:00 -0500
Subject: Re: [newbie] JMX Console - where to start?
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v552)
From: Dain Sundstrom <dain@coredevelopers.net>
To: geronimo-dev@incubator.apache.org
Content-Transfer-Encoding: 7bit
In-Reply-To: <7BB5E7895129484FB9705F711466DEFD0161B2A6@snnexc03.in.ce.com.au>
Message-Id: <45CB5592-DCD1-11D7-A2AE-000393DB559A@coredevelopers.net>

N. Alex Rupp is working on a web based jmx console for Geronimo (and 
mx4j).  The code is on sf right now 
http://sourceforge.net/projects/service-cache

-dain

On Monday, September 1, 2003, at 05:49 PM, Nick Faiz wrote:

> Putting it on a wiki page would be very useful.
>
> Also, how are server instances represented in Geronimo?
>
> Just to throw some obvious needs at the screen for the JMX console. We 
> could
> also consider sections for
>
> - datasources, jdbc connection pools and the usual list of things 
> you'll see
> in a J2EE console.
> - users / groups. Are we using the typical ACL model?
> - the adjustment of logging levels (it would be terrific if we could 
> view a
> stat.s graph of server usage).
> - possibly, a list of active sessions.
>
> Let me know if I can help out in this area. It's hard to know where to 
> jump
> in.
>
> Nick
>
> -----Original Message-----
> From: Matt Kurjanowicz [mailto:mkurjano@cc.gatech.edu]
> Sent: Tuesday, 2 September 2003 7:55 AM
> To: geronimo-dev@incubator.apache.org
> Subject: RE: [newbie] JMX Console - where to start?
>
> Stepping back makes sense...
> At the most basic level, I think we would need:
> * start/stop/restart/kill server
> * start/stop individual components (?)
> * add/remove components (?)
> * check status of server/individual components
> * list/start/stop services
>
> From there, I think we would need to build some more advanced
> functionality:
> * Change configuration of server on the fly
> * List configuration (? - basic?)
> * Manage (in more depth than start/stop/list)/Configure Services
> (necessary?)
>
> I think this is a really restricted list, and just takes into account
> the most basic items.  As far as how to implement this functionality, a
> command line interface would be nice and simple for the simpler tasks,
> but it would be a little more difficult to say, configure the server
> using a command line versus using a web/swing type framework.
>
> -Matt
> mkurjano at cc.gatech.edu
>
> P.S> Where in the Wiki would a page about this go?
>
> -----Original Message-----
> From: Aaron Mulder [mailto:ammulder@alumni.princeton.edu]
> Sent: Monday, September 01, 2003 4:54 PM
> To: geronimo-dev@incubator.apache.org
> Subject: RE: [newbie] JMX Console - where to start?
>
> 	Twiddle is the command line framework I'm referring to.  If you
> look at o.a.g.command.StartCommand (in the core module), you'll see how
> to
> construct a command to tke advantage of it.
>
> 	But perhaps it would be best to step back a sec and start at the
>
> top.  Shall we start a Wiki page on the topic, and assemble a list of
> what
> functions we think the JMX console should have?  It might help to talk
> through the functionality we're going for, and then see what that
> suggests
> when it comes to the implementation.
>
> Aaron
>
> On Mon, 1 Sep 2003, Matt Kurjanowicz wrote:
>> As far as which angle (command line, web, etc.), I'm interested in any
>> of those.  Is Twiddle what you are talking about on the command line?
>>
>> Expanding the Tomcat code sounds like a really interesting idea, but
> I'm
>> not familiar with the code behind it.
>>
>> I am not completely familiar with JMX and JSR -77 and -88, but I am
>> definitely willing to learn.  To be completely honest, I'm really new
> at
>> J2EE stuff, but have lots of time and willingness to learn, so I've
> been
>> playing around with different J2EE components, but nothing spectacular
>> so far.
>>

/*************************
  * Dain Sundstrom
  * Partner
  * Core Developers Network
  *************************/