Network Deployment (Distributed operating systems), v8.0 > Reference > Developer detailed usage information
Java Management Extensions V1.0 to Java Management Extensions V1.2 migration
You might need to migrate custom MBeans that are supplied by products other than the Application Server from v5 to v6.0 and later for full compatibility.
Each Java virtual machine (JVM) in WAS includes an embedded implementation of JMX. In Application Server, v5, the JVMs contain an implementation of the JMX 1.0 specification. In Application Server, v6.0 and later, the JVMs contain an implementation of the JMX 1.2 specification. The JMX 1.0 implementation used in v5 is the TMX4J package that IBM Tivoli products supply. The JMX 1.2 specification used in v6.0 and later is the open source mx4j package. The JMX implementation change across the releases does not affect the behavior of the JMX MBeans in the Application Server. No Application Server administrative API are altered due to the change from the JMX V1.0 specification to the JMX V1.2 specification.
The JMX V1.2 specification is compatible with the earlier JMX V1.0 specification. However, you might need to migrate custom MBeans that are supplied by products other than the application server from v5 to v6.0 and later. The primary concern for these custom MBeans is related to the values that are used in key properties of the JMX ObjectName class for the MBean. The open source mx4j implementation more stringently enforces property validation according to the JMX 1.2 specification. Test the custom MBeans that you deployed in v5 in v6.0 and later, to ensure compatibility. Full details of the JMX V1.2 specification changes from the JMX V1.0 specification are available in the JMX 1.2 specification.
Use administrative programs (JMX)