JMX uses objects called MBeans (Managed Beans) to expose data and resources from your application. In a typical application environment, there are three main layers that use JMX:

• JVMs provide built-in JMX instrumentation or platform-level MBeans that supply important metrics about the JVM.
• Application servers provide server or container-level MBeans that reveal metrics about the server.
• Applications often define custom MBeans that monitor application-level activity.

MBeans are typically grouped into domains to indicate where resources belong. Usually, in a JVM there are multiple domains. For example, for an application running on Apache Tomcat, there are Catalina and Java.lang domains. Catalina represents resources and MBeans relating to the Tomcat container, and Java.lang represents the same for the JVM Hotspot runtime. The application may have its own custom domains.

You can use MBean attributes to create persistent JMX metrics in Splunk AppDynamics as described here. In addition, you can import and export JMX metric configurations from one version or instance of Splunk AppDynamics to another.

See Writing PMI Applications Using the JMX Interface.