Re: [DISCUSS] Reorg of Admin Console for 2.2

[Jack Cai]

If we are thinking of a deeper hierarchy, here is another (more destructive
^_^) proposal to entertain. I'm still kind of new here, so might have missed
lots of background. Just trying to give my 2 cents from an "outsider"'s
point of view.

+ Servers
  + Application Server
   - Geronimo Kernel (put Information, Java System Info, Thread Pool and
Shutdown portlets in the same page here)
   - Web Server
   - JMS Server
   - System modules (Since they are "system", they should be part of the
server)
   - Repository
   - New server assembly
  + Apache HTTP Server
  + Derby DB server
+ Applications
 - Deploy New (Suggest to merge in the plan creator, so that users can
either choose to use an existing plan file, or create a new one using the
wizard)
 - User applications (merge WAR, EAR and Client. I don't quite understand
the reason to divide them)
 - Server plugins
+ Resources
 - DB pools
 - JMS resources
 - JEE Connectors
+ Security
 - (AS IS)
+ Monitoring and Troubleshotting
 - Monitoring
 - Logs
 - Debug Views


-Jack


2008/11/25 Donald Woods <[EMAIL PROTECTED]>

> Thanks for your response.  My comments in-line below.
>
> -Donald
>
>
> Lin Sun wrote:
>
>> 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.
>>
>
> The current grouping makes no sense, as everything under Services is part
> of the "Server" and everything under Server is "services" the runtime is
> providing
>
>  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).
>>
>
> Plugins should be viewed as just another application archive type, whereas
> exporting plugins and creating custom server assemblies has nothing to do
> with managing what applications are deployed in the current server runtime
> being managed, but are tools for those users who don't want to build plugins
> or custom assemblies via the maven c-m-p.
>
>  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.
>>
>
> Then suggest another name/grouping.  The current "Debug Views" is
> misleading to admins, as it makes them seem as developer focused portlets,
> whereas they are really there for admins and developers.  We also have
> monitoring tools, which really should be performed by an external
> application for true production environments (and we need to include some
> pre-canned "health monitoring" templates out of the box for developers and
> simple environments.)  The Apache HTTP portlet has nothing to do with the
> provided Geronimo runtimes, as we don't include the Apache HTTP server.
>
> The thought here, is to group all the portlets that are not used for
> server, application or security management, into a separate "tools"
> category.
>
>  4. I like plan creator under Applications better, as it is today.
>>
>>
> It provides no application management function today (aka.
> deploy/redeploy/undeploy) and is really only there because we didn't want to
> tie users to Eclipse (which we now have Deployment Plan Editors in the
> Eclipse tooling, so these should be viewed as optional tools now.)
>
>  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.
>>
>
> This is a discussion to see what people think.  If the consensus is to wait
> another year or more for console improvements, then fine, but just because
> we're planning on cutting the 2.2 branch mid-Dec. shouldn't keep us from
> making improvements now.
>
>
>  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 plug

Re: [DISCUSS] Reorg of Admin Console for 2.2

[Donald Woods]

Thanks for your response.  My comments in-line below.

-Donald


Lin Sun wrote:

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.


The current grouping makes no sense, as everything under Services is 
part of the "Server" and everything under Server is "services" the 
runtime is providing



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).


Plugins should be viewed as just another application archive type, 
whereas exporting plugins and creating custom server assemblies has 
nothing to do with managing what applications are deployed in the 
current server runtime being managed, but are tools for those users who 
don't want to build plugins or custom assemblies via the maven c-m-p.



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.


Then suggest another name/grouping.  The current "Debug Views" is 
misleading to admins, as it makes them seem as developer focused 
portlets, whereas they are really there for admins and developers.  We 
also have monitoring tools, which really should be performed by an 
external application for true production environments (and we need to 
include some pre-canned "health monitoring" templates out of the box for 
developers and simple environments.)  The Apache HTTP portlet has 
nothing to do with the provided Geronimo runtimes, as we don't include 
the Apache HTTP server.


The thought here, is to group all the portlets that are not used for 
server, application or security management, into a separate "tools" 
category.



4. I like plan creator under Applications better, as it is today.



It provides no application management function today (aka. 
deploy/redeploy/undeploy) and is really only there because we didn't 
want to tie users to Eclipse (which we now have Deployment Plan Editors 
in the Eclipse tooling, so these should be viewed as optional tools now.)



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.


This is a discussion to see what people think.  If the consensus is to 
wait another year or more for console improvements, then fine, but just 
because we're planning on cutting the 2.2 branch mid-Dec. shouldn't keep 
us from making improvements now.



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

Re: [DISCUSS] Reorg of Admin Console for 2.2

[Lin Sun]

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
>
>

Re: [DISCUSS] Reorg of Admin Console for 2.2

[Donald Woods]

OK, I'll work on creating a post to either this thread or GERONIMO-4423 
that includes the proposed moves/renames.



-Donald

David Jencks wrote:

Donald...

I'm not really convinced yet by this.  I've been  wondering what would 
help me understand better what you think is wrong and what you want to 
change.  I wonder if you would be willing to list the current navigation 
tree and next to each portlet say where you want to put it (or split it 
up, etc).  Another thing that might help me would be definitions of the 
categories you propose and some criteria for portlet inclusion.  For 
instance right now having all the plugin/module management under one 
category makes sense to me since they are all involved with 
understanding how the basic geronimo building blocks (plugins) fit 
together and are dependent on one another and what will happen if you 
start or stop one.  I'd need a really lot of convincing that any 
reorganization that moved non-ee plugins away from ee plugins was a good 
idea.


On the other hand I can certainly see putting all the plan creation 
wizards together in one category.



On Nov 23, 2008, at 9:49 PM, Jack Cai wrote:


Donald, thanks for bringing this topic up!

I agree with most of your proposal. I do have several comments though -

* I kind of like keeping the current separation of Server and Service. 
It's hard to find a right label for the merged category - "Service" 
does not sounds right to me. Hard to find a label is an indication 
that these two categories might not be appropriate to merge.


* The Logging portlets are the same kind as the Server information, 
Java System Info and the Monitoring portlet. They should go hand in hand.


Monitoring and the proposed cluster/farm management are the only 
functionality that directly refer to (lots of) other servers. 
 Everything else refers only to the server you're looking at directly. 
 Mixing them up seems like a bad idea to me.



* Should Derby and HTTP server also parts of the Server catetory? 
Although they are not JEE components.


-Jack

2008/11/22 Donald Woods <[EMAIL PROTECTED] >

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


thanks
david jencks

Re: [DISCUSS] Reorg of Admin Console for 2.2

[Donald Woods]

Thanks for the naming ideas for roles/tasks.  I'll work that into a post 
showing the proposed changes.


As far as making the tree collapsible, I think that's a major rework for 
a 3.0 release, as we would also want the collapsible nodes to contain 
their own page, describing what that category deals with and links to 
the child pages (I've seen other Admin Portals do this, but not sure if 
we can with Pluto without too much custom code.)



-Donald


Joe Bohn wrote:
It would help me to see the fully populated proposal for the Navigation 
Tree side-by-side with the existing tree.  It seems one of your primary 
concerns here is the size of the tree and it isn't clear to me if this 
proposal is actually reducing the size of the tree.


I think the real fix for the size issue is to make the tree collapsible. 
 As you mention roles are the best way to eliminate the complexity for 
an individual user and permit filtering based upon a subset of of the 
roles for any particular user (server administrator, security 
administrator, cluster management, etc...).  Both of those will take a 
little longer to implement than a simple reorganization so we still need 
to consider what to do now.


More comments in-line


Donald Woods 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)
Perhaps "Server Management" is a better title?  Services just doesn't 
seem descriptive to me.



 - 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)

"Application Management" ?


 - 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

Why is logging so special?  I think it's fine under Server Management.


 - 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.)
I'm fine with keeping this a unique category since security is such a 
hot topic and we might eventually have a security administrator role 
someday.





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.
I agree that role/task organization is best.  For starters, we should 
rename leaf (task) in the tree with a task-like name.  For example, 
rather than "Web App WARS" it could be "Manage Web Applications (WARs)". 
  Organization of the tasks could be by role but it might make more 
sense by domain (Server tasks, Application tasks, Developer tasks, etc...).






-Donald

Re: [DISCUSS] Reorg of Admin Console for 2.2

[Joe Bohn]

It would help me to see the fully populated proposal for the Navigation 
Tree side-by-side with the existing tree.  It seems one of your primary 
concerns here is the size of the tree and it isn't clear to me if this 
proposal is actually reducing the size of the tree.


I think the real fix for the size issue is to make the tree collapsible. 
 As you mention roles are the best way to eliminate the complexity for 
an individual user and permit filtering based upon a subset of of the 
roles for any particular user (server administrator, security 
administrator, cluster management, etc...).  Both of those will take a 
little longer to implement than a simple reorganization so we still need 
to consider what to do now.


More comments in-line


Donald Woods 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)
Perhaps "Server Management" is a better title?  Services just doesn't 
seem descriptive to me.



 - 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)

"Application Management" ?


 - 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

Why is logging so special?  I think it's fine under Server Management.


 - 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.)
I'm fine with keeping this a unique category since security is such a 
hot topic and we might eventually have a security administrator role 
someday.





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.
I agree that role/task organization is best.  For starters, we should 
rename leaf (task) in the tree with a task-like name.  For example, 
rather than "Web App WARS" it could be "Manage Web Applications (WARs)". 
  Organization of the tasks could be by role but it might make more 
sense by domain (Server tasks, Application tasks, Developer tasks, etc...).






-Donald

Re: [DISCUSS] Reorg of Admin Console for 2.2

[David Jencks]

Donald...

I'm not really convinced yet by this.  I've been  wondering what would  
help me understand better what you think is wrong and what you want to  
change.  I wonder if you would be willing to list the current  
navigation tree and next to each portlet say where you want to put it  
(or split it up, etc).  Another thing that might help me would be  
definitions of the categories you propose and some criteria for  
portlet inclusion.  For instance right now having all the plugin/ 
module management under one category makes sense to me since they are  
all involved with understanding how the basic geronimo building blocks  
(plugins) fit together and are dependent on one another and what will  
happen if you start or stop one.  I'd need a really lot of convincing  
that any reorganization that moved non-ee plugins away from ee plugins  
was a good idea.


On the other hand I can certainly see putting all the plan creation  
wizards together in one category.



On Nov 23, 2008, at 9:49 PM, Jack Cai wrote:


Donald, thanks for bringing this topic up!

I agree with most of your proposal. I do have several comments  
though -


* I kind of like keeping the current separation of Server and  
Service. It's hard to find a right label for the merged category -  
"Service" does not sounds right to me. Hard to find a label is an  
indication that these two categories might not be appropriate to  
merge.


* The Logging portlets are the same kind as the Server information,  
Java System Info and the Monitoring portlet. They should go hand in  
hand.


Monitoring and the proposed cluster/farm management are the only  
functionality that directly refer to (lots of) other servers.   
Everything else refers only to the server you're looking at directly.   
Mixing them up seems like a bad idea to me.



* Should Derby and HTTP server also parts of the Server catetory?  
Although they are not JEE components.


-Jack

2008/11/22 Donald Woods <[EMAIL PROTECTED]>
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


thanks
david jencks

Re: [DISCUSS] Reorg of Admin Console for 2.2

[Jack Cai]

Donald, thanks for bringing this topic up!

I agree with most of your proposal. I do have several comments though -

* I kind of like keeping the current separation of Server and Service. It's
hard to find a right label for the merged category - "Service" does not
sounds right to me. Hard to find a label is an indication that these two
categories might not be appropriate to merge.

* The Logging portlets are the same kind as the Server information, Java
System Info and the Monitoring portlet. They should go hand in hand.

* Should Derby and HTTP server also parts of the Server catetory? Although
they are not JEE components.

-Jack

2008/11/22 Donald Woods <[EMAIL PROTECTED]>

> 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
>
>