Console on managed servers disabled

Question

Console on a managed server is almost disabled. But in some circumstances
it is
good to have limited access. For example, viewing JNDI tree. If some
bindings
are not serializable, or admin server does not have the class files of those
bindings,
JNDI tree of managed server cannot be displayed on admin console.
Is there any solution for this?
-Chenzhong

Answer 1

Another option, although not near as good as a stand-alone tool, I think you could put in the WSDL address for a particular managed server in the Admin Consoles test client. For example, on my machine with the example's server, that is bound to http://localhost:7001/wls_utc/
The one issue might be if you front-end address that gets put in your WSDL doesn't match the managed server that you want to test, then you might need to edit it first, which is probably a pain.
The test client used to be a stand alone deployment (at least I think it was in the 9.2 days), but it appears to be part of an internal application now from the docs:
http://edocs.bea.com/wls/docs103/deployment/managing.html#wp1021614