Make JManage more deployment friendly by allowing the parts of config and data directory to be separated from the code portion, similar to the way multiple instances of tomcat and apache's can run from the same installation.
Expecially important to keep the database 'data' directory outside the JManage installation directory. Easy way to do this would be to support properties such as the following on the command line:
-Djmanage.data.dir (to separate the data dir from jmanage.root)
-Djmanage.config.dir (to separate the entire config directory from jmanage root)
-Djmanage.config.xml.path (to separate only the config.xml with bean definitions from jmanage.root).
This would help very much in deploying within enterprise environments.