Externalize Karaf directories
When using Roboconf in production environments, we strongly recommend you to externalize Karaf’s directories. If for any reason you had to install a new version of Roboconf, your data would be preserved on the next restart.
More precisely, we suggest you define the following environment variables:
KARAF_ETC: the location of your configuration files.
Move the content of Karaf’s etc directory there.
KARAF_DATA: the location of Karaf and Roboconf’s data.
All the information managed by Roboconf about deployed applications is stored there.
Also, make sure JAVA_HOME is defined and points to a valid Java binary.
Eventually, you may want to configure the location of log files.
Notice that when you use Debian and/or RPM packages, these practices are already set up.
You can refer to Karaf’s user guide for more details.
Upgrade Karaf distributions
Major and minor releases of Roboconf may be delivered with new versions of Karaf.
However, maintenance releases generally use the same. For such situations, users may want to only update the Roboconf bundles instead of reinstalling everything.
For those who want to try such a procedure, here is how to proceed.
We here consider roboconf-dm It works the same way with roboconf-agent.
First, login to Karaf’s command line.
# Start Karaf in interactive mode... ./karaf # ... or connect to a running instance. ./client -u karaf
Uninstall the old version.
Then, register the newly released Karaf feature for Roboconf.
We here use a maintenance release (0.9.1)
Eventually, install it.
Verify the used version is the right one (0.9.1).