At 10:48 10.9.2000 -0700, you wrote:
>That's my goal for the administration GUI:
>- easy to use
>- use of look and feel already used in other GUIs
>- help support
>- tailored GUIs for know services (MBeans)
>- all purpose GUIs for unknown services
>- save and retrieve of user settings
>- use of advanced GUI elements like sliders, radio buttons, checkboxes,
>icons etc. to make it more appealing for the user
- authentication & authorization
Who gets to admin the server, and what can they do in the server. Can the
whole world browse the contents of the naming service, for example? Can
anyone with the admin access stop any arbitrary J2EE app running in the
server?
- user management
Create new users. Remove them. Create user groups. Grant them rights. Store
user specific settings.
- diagnostics
How many threads is the server eating up? How much memory it is using?
Which bean is hogging up all the CPU cycles? How many transactions are
currently in process? How many clients are connected? What's the average tx
completion time? per bean?
I think the task of creating an admin GUI may have been a tad misleading.
It probably should have read 'create admin tools'. Or maybe that's a whole
another task altogether.
I also believe this should be 'tools' not just one tool with all sorts of
different functionality in it. If there's a need to use these separate
tools together then they should be brought together by a central admin
framework that could be visualized as a task bar, menu bar or whatever that
allows you to launch different tools based on your needs.
Since we're working in a networked environment, the security (yeah there's
that ugly word again) should be the main concern with ease of use right
behind it.
-- Juha
