Chapter 12. Configuring the Hot Deployment System
Abstract
Standalone containers scan a directory for OSGi bundles and JBI artifacts to automatically load. You can change the location of this folder and the interval at which the folder is scanned.
Overview
Standalone containers will automatically load and deploy OSGi bundles and JBI artifacts from a pre-configured folder. It scans the folder once a second for new bundles or JBI artifacts. You can change the folder a container scans and the scan interval by editing properties in the
org.apache.felix.fileinstall-deploy PID.
Important
The hot deployment system is not not enabled for fabric containers.
Specifying the hot deployment folder
By default, a container scans the
deploy folder that is relative to the folder from which you launched the container. You change the folder the container monitors by setting the felix.fileinstall.dir property in the rg.apache.felix.fileinstall-deploy PID. The value is the absolute path of the folder to monitor. If you set the value to /home/joe/deploy, the container will monitor a folder in Joe's home directory.
Specifying the scan interval
By default containers scan the hot deployment folder every 1000 milliseconds. To change the interval between scans of the hot deployment folders, you change the felix.fileinstall.poll property in the
org.apache.felix.fileinstall-deploy PID. The value is specified in milliseconds.
Example
Example 12.1, “Configuring the Hot Deployment Folders” shows a configuration editing session that sets
/home/smx/jbideploy as the hot deployment folder and sets the scan interval to half a second.
Example 12.1. Configuring the Hot Deployment Folders
JBossFuse:karaf@root>config:edit org.apache.felix.fileinstall-deployJBossFuse:karaf@root>config:propset felix.fileinstall.dir /home/smx/jbideployJBossFuse:karaf@root>config:propset felix.fileinstall.poll 500JBossFuse:karaf@root>config:update
