Details
Description
1. re-structure the navigation tree to make it collapsible, the tree level should be less than 3;
2. re-organize the available tree items into new groups, here is a sample list for implementation:
- Application Server
- Geronimo Kernel (put Information, Java System Info, Thread Pool and Shutdown portlets in the same page here)
- Web Server
- JMS Server
- EJB Server
- Derby server
- New server assembly
- 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, maybe bundles in the 3.0?)
- Plugins
- Resources
- DB pools
- JMS Resources
- J2EE Connectors
- Jar aliases
- Repository
- Security
- Users and Groups
- Keystores
- Certificate Authority
- Security Realms
- Monitoring and Troubleshooting
- Monitoring
- Logs(Include server logs and Derby log)
- Debug Views
- JMX Viewer
- Classloader Viewer
- JNDI Viewer
- Dependency Viewer
3. re-construct the available portlets to improve embedded assistance information, for example, show breadcrum when user is working on a task; reduce in-line text on the current UI, and use hover-help or pop-up help page only when necessary etc...
4. for the long list on the current UI such as system modules, only show the most frequently used ones, use locate/find to display more....
Risks to be noticed for UI changes:
1. Doc
2. Testsuite especially for Selenium test script, if any.
For more details, see hhttp://apache-geronimo.328035.n3.nabble.com/DISCUSS-Reorg-of-Admin-Console-for-2-2-td400707.html#a400707
Further discussion on navigation items, see http://apache-geronimo.328035.n3.nabble.com/Re-categorize-the-items-in-navigation-pane-for-G2-2-td370812.html#a370812
Attachments
Attachments
Issue Links
- relates to
-
GERONIMO-5089 Reorganize the Geronimo console and rebase on Pluto 2.
- Closed