![]() ![]() ![]() ![]() ![]() ![]() ![]() |
Besides programmatic JMX access to your custom MBeans, you can use any JMX-compliant management system to access your MBeans. For information, see What Management Services Have BEA Partners Developed? and the Sun Developer Network Web site, which provides links to books, white papers, and other information on JMX: http://java.sun.com/products/JavaManagement/.
The following sections describe additional ways to access your custom MBeans:
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 JVM 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:
See Enable and Configure IIOP in Administration Console Online Help.
jconsole
service:jmx:rmi:///jndi/iiop://
host:port
/weblogic.management.mbeanservers.runtime
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
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.
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 JVM platform MBean server or the WebLogic Server Runtime MBean Server and looks up your MBeans.
For more information, see Extending the Administration Console.
![]() ![]() ![]() |