|
Hi
I am working on the JMX Connector which was created
to allow remote Administration tools to work on
several jBoss instances.
From my point of view there are two ways to make an
administration console:
1) A generic GUI which shows the attributes of the
services and let the user invoke the desired methods
2) A tailored GUI for each know
service
The first is just showing the attributes of the
different MBeans and invoking the methods offered in the
MBean interface. This approach is very flexible but
do not guide the user nor give him enough support.
The second shows the services in a way that it is
easy for the user to see what's going on and what
he can do to change the system. This approach is
easy to use for the user but you have to change
the console every time the services (MBeans)
changes or new services are created.
Either way IMO the administration console should
support the following:
- use of JMX technology to access the services, its
attributes and methods
- the console should be able to run locally (jBoss
instance) or remotely which also means that it
should be packaged that it can
run outside of the jBoss instance
- when the console runs remotely use the JMX
Connector and allow the user to connector to more
than one jBoss instance (maybe
also locally).
At the moment there is a lot of movements around
JMX (final release came out and jBoss or at least
the JMX Connector must be changed appropriately)
and I try to design the JMX Relation Service for jBoss.
By the way what did you already
accomplished?
Have fun
Mad Andy
|
- [jBoss-Dev] Carlos Pita
- [jBoss-Dev] Niranjani
- Re: [jBoss-Dev] Andreas Schaefer
- Re: [jBoss-Dev] Niranjani
- [jBoss-Dev] gsun
- Re: [jBoss-Dev] Juha-P Lindfors
- RE: [jBoss-Dev] Sandeep Dath
- RE: [jBoss-Dev] Jerson Chua
- RE: [jBoss-Dev] Sandeep Dath
- RE: [jBoss-Dev] Jerson Chua
- [jBoss-Dev] Schaefer, Andreas
- RE: [jBoss-Dev] marc fleury
- [jBoss-Dev] Re: [jBoss-Dev] Rickard �berg
