dir=%KARAF_BASE% wrapper.java.command=%JAVA_HOME%/bin/java wrapper.java.mainclass=org.apache.karaf.wrapper.internal.Main wrapper.java.classpath.1=%KARAF_HOME%/lib/karaf-wrapper.jar wrapper.java.classpath.2=%KARAF_HOME%/lib/karaf just installing the http or war feature doesn’t bind the connector. By default, Karaf creates an internal Jetty connector that you can configure via etc/ org.ops4j.pax.web.cfg : Note: if you want to use karaf@root()> feature:install war org.osgi.service.http.port=8181 It’s possible to enable the HTTPs "internal" connector. The first step is to create a keystore containing a server certificate. For instance

dir=%KARAF_BASE% wrapper.java.command=%JAVA_HOME%/bin/java wrapper.java.mainclass=org.apache.karaf.wrapper.internal.Main wrapper.java.classpath.1=%KARAF_HOME%/lib/karaf-wrapper.jar wrapper.java.classpath.2=%KARAF_HOME%/lib/karaf repositories (classifier "features") or kar archives. Feature repositories are installed in the internal "system" Maven structured repository. Kar archives have their content unpacked on top of the server startup.properties at the appropriate start level and the bundles being copied into the "system" internal repository. You can use feature_name or feature_name/feature_version formats. • bar

5. EVENTADMIN The Decanter EventAdmin Collector is an event-driven collector, listening for all internal events happening in the Apache Karaf Container.  It’s the perfect way to audit all actions performed decanter-collector-eventadmin By default, the eventadmin collector is listening for all OSGi framework and Karaf internal events. You can specify additional events to trap by providing a ‘etc/org.apache.karaf protocol, \ com.sun.jmx.remote.generic, \ com.sun.jmx.remote.opt, \ com.sun.jmx.remote.opt.internal, \ com.sun.jmx.remote.opt.security, \ com.sun.jmx.remote.opt.util, \ com.sun.jmx.remote

5. EventAdmin The Decanter EventAdmin Collector is an event-driven collector, listening for all internal events happening in the Apache Karaf Container. NOTE It’s the perfect way to audit all actions eventadmin collector: By default, the eventadmin collector is listening for all OSGi framework and Karaf internal events. You can specify additional events to trap by providing a ‘etc/ org.apache.karaf.decanter You can create two kinds of collector: • event driven collector automatically reacts to some internal events. It creates an event sent to a topic. • polled collector is a Runnable OSGi service periodically

all events to the event dispatcher. When the Event Dispatcher receives an event, it looks up an internal registry (in our case the OSGi Service Registry) to find an Event Handler that can handle the received

all events to the event dispatcher. When the Event Dispatcher receives an event, it looks up an internal registry (in our case the OSGi Service Registry) to find an Event Handler that can handle the received