Migrate MBeans specific to other application servers

This rule detects all invocations of the javax.management.ObjectName constructor that might be application server specific and would need to be migrated for the application to run on WebSphere Application Server.

For example, the following invocations will be flagged:

new ObjectName("jboss.admin:service=DeploymentFileRepository")
new ObjectName("com.bea:Name=RuntimeService")
new ObjectName("com.acme:name=toon,type=com.acme.toon.management.ToonBeanCounter")
...
String name = "foo:bar";
...
new ObjectName(name)

Note that only MBeans specifically provided by application servers other than WebSphere Application Server need to be migrated. This rule will still flag those that are not specific to WebSphere, including ones that might be compatible, such as custom MBeans. Also, all invocations using non-final variables as arguments will be flagged because the tool does not have enough information to determine their values at runtime. Check all flagged MBeans for compatibility before use on WebSphere Application Server.

For example, the following invocations will not be flagged since they contain WebSphere-specific names.

static final String NAME = "com.ibm.websphere.testgrid:type=TestService";
...
new ObjectName("WebSphere:type=Server")
new ObjectName(NAME)

For a list of WebSphere provided MBeans, refer to WebSphere Application Server Public MBean Interfaces.

For a list of MBeans provided by Liberty, refer to Liberty:List of provided MBeans.

For more information on how to set up custom MBeans, refer to Extending the WebSphere Application Server administrative system with custom MBeans.