same (in etc/org.apache.karaf.shell.cfg or using shell:completion command). However, some minor changes have been introduced and new commands available: Apache Karaf 4.x feature:requirement-list fe bin/start bin\start.bat Clean start Apache Karaf stores all previously applications installed and changes that you did in the data folder. If you want to start from a clean state, you can remove the data when you change the SSHd server configuration, you have to restart the SSHd server to load the changes. You can do it with: karaf@root()> bundle:restart -f org.apache.karaf.shell.ssh The Apache Karaf

section in this page). Clean start Apache Karaf stores all previously applications installed and changes that you did in the data folder. If you want to start from a clean state, you can remove the data when you change the SSHd server configuration, you have to restart the SSHd server to load the changes. You can do it with: karaf@root()> bundle:restart -f org.apache.karaf.shell.ssh The Apache Karaf log.level = 3 ... • felix.fileinstall.enableConfigSave flush back in the configuration file the changes performed directly on the 60 CONFIGURATION configuration service (ConfigAdmin). If true, any change

It’s also possible to enable local resources listeners: these listeners broadcast local resource changes as cluster events. Please note that this behavior is disabled by default as it can have side effects working together. This permits some nodes (those outside the group) not to need to sync’ed with changes of a node within a group. By default, the Cellar nodes go into the default group: The x indicates karaf.cellar.node.cfg configuration file: The listener listens for the following local feature changes: • add features repository • remove features repository • install feature • uninstall feature

It’s also possible to enable local resources listeners: these listeners broadcast local resource changes as cluster events. Please note that this behavior is disabled by default as it can have side effects working together. This permits some nodes (those outside the group) not to need to sync’ed with changes of a node within a group. By default, the Cellar nodes go into the default group: The x indicates karaf.cellar.node.cfg configuration file: The listener listens for the following local feature changes: * add features repository * remove features repository * install feature * uninstall feature 7

restart (with the bundle:restart command) the Decanter elasticsearch bundle in order to load the changes. The Decanter elasticsearch node also supports loading and override of the settings using a etc/ Driven Collector, we can create a BundleCollector. This collector will react when a bundle state changes (installed, started, stopped, uninstalled). The purpose is to send a monitoring event in a collect

Driven Collector, we can create a BundleCollector. This collector will react when a bundle state changes (installed, started, stopped, uninstalled). The purpose is to send a monitoring event in a collect