The JDK includes JConsole, a Swing-based JMX client that you can use to browse MBeans. You can browse the MBeans in any WebLogic Server MBean server and in the platform MBean server. Sun recommends that you use JConsole only in a development environment; it consumes significant amounts of resources. See Using JConsole to Monitor Applications at http://java.sun.com/developer/technicalArticles/J2SE/jconsole.html.
To access custom MBeans from JConsole:
Enable the IIOP protocol for the WebLogic Server instance that hosts your MBeans. Configure the default IIOP user to be a WebLogic Server user with Administrator privileges.
where host:port is the host name and port of the WebLogic Server instance that hosts your MBeans.
For example: service:jmx:rmi:///jndi/iiop://localhost:7001/weblogic.management.mbeanservers.runtime
In the User Name and Password boxes, enter the default IIOP user name and password.
Accessing Custom MBeans from WebLogic Scripting Tool
If you register your MBeans in the Runtime MBean Sever, you can use WebLogic Scripting Tool to access your custom MBeans. See Accessing Custom MBeans in WebLogic Scripting Tool.
Accessing Custom MBeans from an Administration Console Extension
You can extend the WebLogic Server Administration Console by creating Java Server Pages (JSPs) that conform to a specific template. Your JSP can include JMX code that connects to the platform MBean server or the WebLogic Server Runtime MBean Server and looks up your MBeans.