JMX in Weblogic

FragranceM

　　Here I would like to list some topics I used to search or study.

MBean Servers in Weblogic
　　The JVM for an Administration Server maintains three MBean servers provided by BEA and optionally maintains the platform MBean server, which is provided by the JDK itself:

• 
  Domain Runtime MBean Server: MBeans for domain-wide services. This MBean server also acts as a single point of access for MBeans that reside on Managed Servers. Only the Administration Server hosts an instance of this MBean server. Object Name: weblogic.management.mbeanservers.domainruntime
  
• 
  Runtime MBean Server: MBeans that expose monitoring, runtime control, and the active configuration of a specific WebLogic Server instance. You can also register your own (custom) MBeans in this MBean server. Each server in the domain hosts an instance of this MBean server. Object Name: weblogic.management.mbeanservers.runtime.
  
• 
  Edit MBean Server: Pending configuration MBeans and operations that control the configuration of a WebLogic Server domain. It exposes a ConfigurationManagerMBean for locking, saving, and activating changes. Only the Administration Server hosts an instance of this MBean server. Object Name: weblogic.management.mbeanservers.edit
  
• 
  The JVM's platform MBean server: MBeans provided by the JDK that contain monitoring information for the JVM itself. You can register custom MBeans in this MBean server, but BEA recommends that you register them in its Runtime MBean Server.Local applications can access all of the MBeans through the MBeanServer interface that java.lang.management.ManagementFactory.getPlatformMBeanServer() returns.
  

The JVM for a Managed Server maintains only one BEA MBean server and the optional platform MBean server.

Accessing WebLogic Server MBeans with JMX

Remote connection to Weblogic MBean Server: Using JConsole
　　In order to load remote Weblogic MBean Server, we should add WL_HOME\server\lib\wljmxclient.jar into classpath.
　　Here is the command used to launch jconsole.exe:

set JAVA_HOME="C:\Program Files\Java\jdk1.6.0_24"
set WL_HOME=c:\bea11g\wlserver_10.3
call %JAVA_HOME%\bin\jconsole.exe -J-Djava.class.path=%JAVA_HOME%\lib\jconsole.jar;%JAVA_HOME%\lib\tools.jar;%WL_HOME%\server\lib\wljmxclient.jar -J-Djmx.remote.protocol.provider.pkgs=weblogic.management.remote -debug 
　　Then input URL as following to access Weblogic domain MBean server:
　　service:jmx:rmi://${HOST}/jndi/iiop://${HOST}:${PORT}/weblogic.management.mbeanservers.domainruntime
　　


Remote connection to Weblogic MBean Server: Java Application
　　http://docs.oracle.com/cd/E12840_01/wls/docs103/jmx/accessWLS.html#wp1112969

Local Connections to the Runtime MBean Server
　　If the classes for the JMX client are located at the top level of an enterprise application (that is, if they are deployed from the application's APP-INF directory), then the JNDI name for the Runtime MBean Server is:
　　java:comp/jmx/runtime
　　If the classes for the JMX client are located in a J2EE module, such as an EJB or Web application, then the JNDI name for the Runtime MBeanServer is:
　　java:comp/env/jmx/runtime

Using the Monitoring Dashboard
　　http://docs.oracle.com/cd/E14571_01/web.1111/e13714/dashboard.htm#CIHHJIDD
　　TO BE UPDATED.

WebLogic Server MBean Object Names
　　http://docs.oracle.com/cd/E15523_01/web.1111/e13728/understandwls.htm#i1116307
　　TO BE UPDATED.