This is still the biggest barrier to broader jManage use amongst prospective users I've seen.
The issue is that these folk don't really think in terms of ObjectNames. They think in terms of the MBean tree they see in jconsole -- but they want access to this via an HTML UI and a lot of the other material in jManage is really right on target for them as well.
DHTML on the left and the exist MBean details pages on the right would seem to really do the trick. The MBean tree could be a filtered view as well, i.e. filtered by ObjectName pattern -- so the default is *:* but you could configure focused views of smaller regions of the tree by doing something like com.myco:type=onetype,* and just dynamically tracking MBeans that match this ObjectName pattern (by listening for MBean registration/deregistration after the original query). Essentially with DHTML you could have something just as useful as the MBeans tab in jconsole -- but better. [The MBeans tab in jconsole has issues in the limited details pages provided in Java 5 and the overly-programmer oriented ones in Java 6. Java 6's jconsole also dumps attributes and operations right into the MBean tree, which causes no end of confusion, especially since these are not sorted to the top or bottom of the node set.]
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Logged In: YES
user_id=1607229
At least make the managedApplications JSP for clustered
environments be expandable/collapable
Logged In: YES
user_id=883982
Originator: NO
This is still the biggest barrier to broader jManage use amongst prospective users I've seen.
The issue is that these folk don't really think in terms of ObjectNames. They think in terms of the MBean tree they see in jconsole -- but they want access to this via an HTML UI and a lot of the other material in jManage is really right on target for them as well.
DHTML on the left and the exist MBean details pages on the right would seem to really do the trick. The MBean tree could be a filtered view as well, i.e. filtered by ObjectName pattern -- so the default is *:* but you could configure focused views of smaller regions of the tree by doing something like com.myco:type=onetype,* and just dynamically tracking MBeans that match this ObjectName pattern (by listening for MBean registration/deregistration after the original query). Essentially with DHTML you could have something just as useful as the MBeans tab in jconsole -- but better. [The MBeans tab in jconsole has issues in the limited details pages provided in Java 5 and the overly-programmer oriented ones in Java 6. Java 6's jconsole also dumps attributes and operations right into the MBean tree, which causes no end of confusion, especially since these are not sorted to the top or bottom of the node set.]