Starting Apache Karaf Cave Server 2. Repository 2.1. Create 2.2. List 2.3. Repository and OBR service 2.4. Destroy 2.5. What’s next 3. Populate repository 3.1. Upload a single artifact 3.2. Populate Populate from an external repository 4. Proxy repository 5. OBR commands 6. HTTP wrapper service 6.1. OBR metadata access 6.2. OSGi bundles access 7. Administration Overview Apache Karaf Cave is OSGi Bundle Repository (OBR) and Karaf Features Repository (KFR). OBR provides a service that can automatically install a bundle, with its deployment dependencies, from a bundle repository. Apache Karaf

Apache Karaf Cave Server 2. Repository 2.1. Create 2.2. List 3. Populate repository 3.1. Upload a single artifact 3.2. Populate from an external repository 4. Proxy repository 5. HTTP wrapper service service 5.1. Repository metadata access 6. Maven wrapper service 7. Administration 7.1. JMX 7.2. REST Overview Apache Karaf Cave is an Apache Karaf sub-project. Cave is an implementation of the OSGi OSGi Repository specification, providing additional features such as a complete Maven repository support, a REST API for management, support of remote repository proxy. Cave deals with the requirements

Provisioning: Apache Karaf supports a large set of URLs where you can install your applications (Maven repository, HTTP, file, etc). It also provides the concept of "Karaf Features" which is a way to describe verify and validate Karaf features • karaf:features-add-to-repository to recursively copy features XML and content into a folder (repository) • karaf:features-export-meta-data to extract the metadata org/ download.html. Extract the files in the directory of your choice. • by checking out the git repository: Use Apache Maven to build Apache Karaf: git clone https://github.com/apache/karaf karaf NOTE

Provisioning: Apache Karaf supports a large set of URL where you can install your application (Maven repository, HTTP, file, etc). It also provides the concept of "Karaf Feature" which is a way to describe your org/index/community/download.html. Extract the files in the directory of your choice. • by checkout of the git repository: git clone https://git-wip-us.apache.org/repos/asf/ karaf.git karaf 1. Use Apache Maven to build org/index/community/download.html. Extract the files in the directory of your choice. • by checkout of the git repository: git clone https://git-wip-us.apache.org/repos/asf/ karaf.git karaf 1. Use Apache Maven to build

EventAdmin (optional) 7.3. Blocking policy 8. OBR Support 8.1. Enable OBR support 8.2. Register repository URL in a cluster 8.3. Deploying bundles using the cluster OBR 9. OSGi Event Broadcasting support have the name of the repository, and the URL, like in the feature:repo-list command. However, the cluster:feature-repo-list command provides the location of the features repository: * cluster means that that the repository is defined only on the cluster group * local means that the repository is defined only on the local node (not on the cluster) * cluster/local means that the repository is defined both

EventAdmin (optional) 7.3. Blocking policy 8. OBR Support 8.1. Enable OBR support 8.2. Register repository URL in a cluster 8.3. Deploying bundles using the cluster OBR 9. OSGi Event Broadcasting support default | node2:5702 node1:5701(x) | test | karaf@node1()> cluster:feature-repo-list default Repository | Located | URL ------------------------------------------------------- have the name of the repository, and the URL, like in the feature:repo-list command. However, the cluster:feature-repo-list command provides the location of the features repository: * cluster means that

for each collector, appender, SLA alerter. The first thing to do is to add the Decanter features repository in Karaf: Or Now, you have to install the collectors, appenders, and eventually SLA alerters

features for each collector, appender, alerter. The first thing to do is to add the Decanter features repository in Karaf: karaf@root()> feature:repo-add mvn:org.apache.karaf.decanter/apache-karaf- decanter/2