Hi, Thanks for bringing this up to discussion. I am not seeing the obvious advantage of what you propose and I have the following specific comments - 1. I kinda like what we currently have, Server and Service. 2. I think we should have a plugin category (if we are going to have the collapsible tree structure) and put the 3 plugin related portlets there (install plugin, export plugin and customer server assembly). Otherwise, I think it is better to have all 3 in one page (I believe we discussed this before on dev list). 3. I really don't like the Tools name, as it is not concrete. I'd rather see stuff organized into specific names instead of a generic name. 4. I like plan creator under Applications better, as it is today.
Maybe we should not rush the organization of the console navigation in 2.2, given that we are planning it soon. I 'd rather to see us do it in one shot, instead of changing it in 2.2 and changing it again in 3.0. Lin On Fri, Nov 21, 2008 at 2:36 PM, Donald Woods <[EMAIL PROTECTED]> wrote: > Given our Console navigation tree has gotten so large and many "new" > portlets were added in 2.0/2.1 without doing a proper reorg of what we had, > I'm proposing the following changes as part of GERONIMO-4423, 4424, 4425 and > yet to be created JIRAs: > > 1) Reorg the Server Console contents into main categories of: > - Services (config/resources) > - combination of existing Server and Services portlets > - contains portlets for server/service configuration > info, threads, connectors, modules, jms server/resourecs, ... > - future portlet to setup clustering/farming member servers > and view their status would go here > - Applications (app deployment and life-cycle) > - portlets to deploy/redeploy/undeploy apps/wars/ears/jars > - portlets to install/uninstall and stop/start modules > - porlet to install plugins (not export or server assembly) > - future updates and/or new portlet to support deploy/undeploy > apps to clusters/farming would go here > - Security > - portlets focused on users/groups, keys/ca, realms > - Logging > - portlets to configure logging and log levels > - separate pages for Server, Web Access and Derby log viewers > - Tools > - everything in current "Debug Views" category > - Plan Creator portlet > - Monitoring portlet > - Embedded DB portlets (renamed to Derby * to reflect true usage) > - Apache HTTP portlet (for creating mod_jk configs) > - Exporting plugins > - Custom server assemblies > > I could see the Logging portlets as one page under Tools, as those are > really runtime tools (changes don't survive a restart) for debugging > server/application problems. > > I could also see the Security portlets being split between the Services and > Tools categories (but really think these deserve their own category.) > > > The point, is that we need to review how the admin console is laid out and > try to regroup into Java EE roles/tasks/concepts, like server > config/resources, app deployment/mgmt and other tools/tasks. > > > -Donald > >
