1. Application 4.10.2. OSGi 4.10.3. Feature and resolver 4.10.4. Features repositories 4.10.5. Boot features 4.10.6. Features upgrade 4.10.7. Overrides 4.10.8. Feature bundles 4.10.9. Dependent directory • /instances : directory containing [instances|instances] • /lib : contains libraries ◦ /lib/boot : contains the system libraries used at Karaf bootstrap ◦ /lib/endorsed : directory for endorsed service, so you can use systemctl instead of a SystemV based service: This will enable Karaf at system boot. Uninstall The wrapper:install provides the system commands to perform to uninstall the service/

service: systemctl enable /opt/apache-karaf-3.0.5/bin/karaf.service This will enable Karaf at system boot. UNINSTALL The wrapper:install provides the system commands to perform to uninstall the service/daemon) wrapper.java.classpath.2=%KARAF_HOME%/lib/karaf.jar wrapper.java.classpath.3=%KARAF_HOME%/lib/karaf-jaas-boot.jar wrapper.java.classpath.4=%KARAF_HOME%/lib/karaf-wrapper-main.jar wrapper.java.classpath.5=%KA again. To prevent this behaviour, you can specify features as boot features. BOOT FEATURES You can describe some features as boot features. A boot feature will be automatically install by Apache Karaf, even

remotely use Decanter. For instance, you can have an application running on a different platform (spring-boot, application servers, …). This application can use a log4j socket appender that send the logging 0-b01-ea.jar] The opendmk_jmxremote_optional_jar-1.0-b01-ea.jar file has to be copied in the lib/boot folder of your Apache Karaf instance. Then, you have to add the new JMX remote packages by editing

KAR files in deployment folder, etc. so that your Kubernetes container may bootstrap everything on boot. The Cellar Kubernetes discovery service is a great complement to the Karaf docker.io feature (allowing

KAR files in deployment folder, etc. so that your Kubernetes container may bootstrap everything on boot. The Cellar Kubernetes discovery service is a great complement to the Karaf docker.io feature (allowing

remotely use Decanter. For instance, you can have an application running on a different platform (spring-boot, application servers, …). This application can use a log4j socket appender that send the logging