This is a requirement for monitoring and configuring JVMs.
The idea is that may JVMs have user defined purposes. For example, a weblogic server JVM is serving a specific purpose as defined by the applications deployed on it and by the URL that it serves. Given that the purpose is known, all enterprise monitoring systems respect the notion of a server/JVM identity and associates all data collected for that ID across restarts.
The behavior that we want is as follows:
1. User defines a JVM ID via a command line option (could be a property)
2. ID will be unique per host.
3. All server specific config MBeans for the JVM will be persisted in a folder (or file) associated with the ID.
4. EM can use this feature to better manage a JVM in term of monitoring and configuring it.
5. We won't force the users to set an ID, but we shall recommend it as the proper blueprint for a JVM.