…). This Map is sent to the appenders. The collector allows you to remotely use Decanter. For instance, you can have an application running on a different platform (spring-boot, application servers means that you can add your own custom data, and easily create queries bases on this data. For instance, instead of the log collector, you can create the following etc/ org.apache.karaf.decanter.collector property is the MBeanServer to connect. "local" is reserved keyword to specify the local MBeanServer. Instead of "local", you can use the JMX service URL. For instance, for Karaf version 3.0.0, 3.0.1

Post-Installation steps 4.1.4. Building from Sources 4.2. Directory structure 4.3. Start, stop, restart, connect 4.3.1. Start 4.3.2. Stop 4.3.3. Status 4.3.4. Restart 4.3.5. SystemMBean 4.4. Integration in Commands 4.12.3. Deployer 4.12.4. JMX KarMBean 4.13. Instances 4.13.1. Using the instance commands 4.13.2. Instance script 4.13.3. JMX InstanceMBean 4.14. Security 4.14.1. Realms 4.14.2. Users, groups Leveraging existing Java capabilities (via reflection) 5.2.8. Examples 5.3. Programmatically connect 5.3.1. To the console 5.3.2. To the management layer 5.4. Branding 5.4.1. Console 5.4.2. Adding

console and JMX. • Instances: multiple instances of Apache Karaf can be managed directly from a main instance (root). APACHE KARAF OVERVIEW 5 • OSGi frameworks: Apache Karaf is not tight to one OSGi framework in the console. karaf@root> Display all 183 possibilities? (y or n) *:config *:dev *:feature *:instance *:jaas *:kar *:log *:package *:region *:service *:shell *:ssh addbundle config:property-append config:property-delete config:property-list config:property-set config:update connect create date delete destroy dev QUICK START 9 dev:dump-create display

…). This Map is sent to the appenders. The collector allows you to remotely use Decanter. For instance, you can have an application running on a different platform (spring-boot, application servers read from the file using the regex property. For instance: regex=(.*foo.*) Only the line matching the regex will be sent to the dispatcher. For instance, instead of the log collector, you can take keys used a property name in the event. Apache Karaf Decanter 2.x - Documentation - 4 For instance, you can have the following etc/org.apache.karaf.decanter.parser.split.cfg configuration file:

OSGi runtime. It means that using Cellar, you are able to call an OSGi service located on a remote instance. See the transport and DOSGi section of the user guide. Finally, Cellar also provides "runtime descriptor. The easiest way to install is just to have an internet connection from the Karaf running instance. See link:deploy to how to install and start Cellar. 2.2. Building from Sources If you intend Deploy Cellar This chapter describes how to deploy and start Cellar into a running Apache Karaf instance. This chapter assumes that you already know Apache Karaf basics, especially the notion of features

OSGi runtime. It means that using Cellar, you are able to call an OSGi service located on a remote instance. See the [Transport and DOSGi] section of the user guide. Finally, Cellar also provides "runtime descriptor. The easiest way to install is just to have an internet connection from the Karaf running instance. See link::deploy to how to install and start Cellar. 2.2. Building from Sources If you intend Deploy Cellar This chapter describes how to deploy and start Cellar into a running Apache Karaf instance. This chapter assumes that you already know Apache Karaf basics, especially the notion of features

backend. As the Cave backend is designed in a plugin way, you can implement your own backend (for instance, JDBC or LDAP backend). • OBR Metadata Generation: Karaf Cave automatically creates the OBR metadata file: , http: , etc. • Repository proxy: Karaf Cave is able to proxy an existing repository, for instance an existing Maven repository. The artifacts are located on the "external" repository, Cave handles supports file: and http: URLs, it means that Cave is able to browse a remote HTTP Maven repository for instance. • Repository population: Karaf Cave is able to get artifacts present on an "external" repository

backend. As the Cave backend is designed in a plugin way, you can implement your own backend (for instance, JDBC or LDAP backend). • Repository Metadata Generation: Cave creates the repository metadata sion, file:, http:, etc. • Repository proxy: Cave is able to proxy an existing repository, for instance an existing Maven repository. The artifacts are located on the "external" repository, Cave handles supports file: and http: URLs, it means that Cave is able to browse a remote HTTP Maven repository for instance. • Repository population: Cave is able to get artifacts present on an "external" repository (local