At 12:37 10.9.2000 -0700, you wrote:
>- Authentication and Authorization (thankx Juha)
JAAS seems like the most flexible approach here. Though I'm really not at
all familiar with it, a quick glance through Sun's JAAS FCS docs promises
an authentication modules for JNDI, NT & Solaris. The JNDI approach backed
by a persistent naming service seems like the safest bet here (no linux
modules available). Although the OS specific mods would certainly add to
the ease of use aspect.
>- Security (secure data transfer, access control, logging etc.)
JSSE? Also, I'm wondering if it would be valuable to have a simple ssh
service available, so you'd be able to log to a remote jBoss server and
write 'init 0' (as Oleg suggested), 'stop <jmx:service>' or whatever..
('man jboss'? ;)
>- Search and connection to local/remote jBoss instances to be
> managed
Yes this is definitely necessary. And should be as transparent to the user
as possible.
>- Pluggable structure for service management components (MBeans)
>- Configuration service (get and set of configuration properties to be
> available to all parts of the AGF)
>- Support for advanced GUI features like Icons with Drag and Drop
> etc.
>- GUI Framework with Menu, Working Pane, Help system (JavaHelp)
> etc.
Yes, in other words, a desktop for the WebOS. You can manage the OS and the
apps from under the same framework.
>By the way IMO Diagnostic (as Juha mentioned) shoud be MBean
>service(s) offered by jBoss and the AGF should only provide a GUI
>representation of this MBean(s) because I would like to reduce the
>communication interface to JMX.
Yes, exactly. Whenever it's possible. Not sure that everything can be done
this way, or will have to live with the lowest common denominator. Some
useful diagnostics may just be too 'low level' so they really need an
access to the underlying OS (CPU load comes to mind). In which case we'll
have to give it up, or hope that something like the JSR000077 addresses
these sort of issues.
-- Juha
