james-server-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Juan Carlos Murillo <muri...@inet.co.cr>
Subject Re: Proposal for Web Admin Console
Date Fri, 17 Jun 2005 17:25:54 GMT
Meant to include this link but hit Ctrl+Enter by mistake:

http://wiki.apache.org/james/WebAdminConsole#preview

What is the preference for exposing JMX to management interfaces, RMI or
SOAP?


On Fri, 2005-06-17 at 11:10 -0600, Juan Carlos Murillo wrote:
> How does this sound:
> 
> 1- We build the web management console.
> 2- We offer it as a war download
> 3- We offer it as a war/servlet container bundle
> 4- We offer it as a James/war/servlet container bundle
> 
> This targets three different user types:
> 
> (2) Would target savvy user with multiple James that have centralized
> J2EE appserver for general app management
> (3) Would target users that decide to run James and web app on separate
> servers
> (4) Would target SOHO users that don't want to deal with the pain of
> installation/configuration.
> 
> I agree with Noel's breakdown below.  We can do parallel development on
> all these tiers and be finished faster.  I have updated the proposal to
> reflect it as to what pertains to the web admin console itself:
> > > 
> > > What we're look at probably lays out as:
> > > 
> > >   - JMX support w/MBeans embedded in each managed process
> > >   - Admin service (model)
> > >   - Admin webapp in a web container of the user's choice
> > >   - Admin script interface (uses BSF)


---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org


Mime
View raw message