Java Management Extensions V1.0 to Java Management Extensions V1.2 migration

We might need to migrate custom MBeans that are supplied by products other than the appserver from V5 to V6.0 and later for full compatibility.

Each JVM in WAS includes an embedded implementation of Java Management Extensions (JMX). In WAS v5, the JVMs contain an implementation of the JMX 1.0 specification. In WAS 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 appserver. No Application Server admin APIs are altered due to the change from the JMX V1.0 specification to the JMX V1.2 specification.

The JMX V1.2 spec is compatible with the earlier JMX V1.0 specification. However, we might need to migrate custom MBeans that are supplied by products other than the appserver 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 spec changes from the JMX V1.0 spec are available in the JMX 1.2 specification.

---

 

Related tasks

Use admin programs (JMX)