repository 5. HTTP wrapper 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 additional features such as a complete Maven repository support, a REST API for management, support of remote repository proxy. Cave deals with the requirements and capabilities of all artifacts. Apache Karaf 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 file: or remote http:), looking for OSGi

OBR commands 6. HTTP wrapper service 6.1. OBR metadata access 6.2. OSGi bundles access 7. Administration Overview Apache Karaf Cave is an Apache Karaf sub-project. It provides an OSGi Bundle Repository able to browse a remote HTTP Maven repository for instance. • Repository population: Karaf Cave is able to get artifacts present on an "external" repository (local file: or remote http:), looking for Karaf Cave supports file: but also http: URL. It means that Apache Karaf Cave is able to browse a remote repository and copy the artifacts in your "local" repository. For instance, you can populate your

an enterprise-ready container, providing a lot of management indicators and operations via JMX. • Remote: Apache Karaf embeds an SSHd server allowing you to use the console remotely. The management layer (using server or background modes), you can connect to the console. This connection can be local or remote. It means that you can access to Karaf console remotely. To connect to the console, you can use 8101 (the default Apache Karaf SSH port). client accepts different options to let you connect on a remote Apache Karaf instance. You can use --help to get details about the options: 22 START, STOP, RESTART

commands 4.5.2. Subshell and completion mode 4.5.3. Unix like environment 4.5.4. Security 4.6. Remote 4.6.1. SSHd server 4.6.2. JMX MBeanServer 4.7. Log 4.7.1. Configuration files 4.7.2. Log4j v2 is an enterprise-ready container, providing many management indicators and operations via JMX. • Remote: Apache Karaf embeds an SSHd server allowing you to use the console remotely. The management layer container directly from Maven • karaf:client to interact with a remote Karaf instance • karaf:deploy to deploy an application to a remote Karaf instance 3.7. Update guide We encourage users to start

periodically by the Decanter Scheduler. The JMX collector connects to a JMX MBeanServer (local or remote), and retrieves all attributes of each available MBeans. The JMX metrics (attribute values) are you can specify service:jmx:rmi:///jndi/rmi://localhost:1099/karaf-root. You can also polled any remote MBean server (Karaf based or not) providing the service URL. Apache Karaf Decanter 2.x - Documentation copied in the lib/boot folder of your Apache Karaf instance. Then, you have to add the new JMX remote packages by editing etc/config.properties, appending the following to the org.osgi.framework.system

periodically by the Decanter Scheduler. The JMX collector connects to a JMX MBeanServer (local or remote), and retrieves all attributes of each available MBeans. The JMX metrics (attribute values) are you can specify service:jmx:rmi:///jndi/rmi://localhost:1099/karaf-root . You can also polled any remote MBean server (Karaf based or not) providing the service URL. • the username property contains the Network socket The Decanter network socket collector listens for incoming messages coming from a remote network socket collector. The decanter-collector-socket feature installs the network socket collector:

defined (using a couple hostname or IP and port list). Cellar is able to synchronize: • bundles (remote, local, or from an OBR) • config • features • eventadmin Optionally, Cellar also support synchronization Distributed 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 service. If the service is not available locally, Cellar will "route" the service call to the remote remote containing the service. 11. Discovery Services The Discovery Services allow you to use third

defined (using a couple hostname or IP and port list). Cellar is able to synchronize: * bundles (remote or local) * config * features Optionally, Cellar also support synchronization of OSGi EventAdmin Distributed 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 service. If the service is not available locally, Cellar will "route" the service call to the remote remote containing the service. 13. Discovery Services The Discovery Services allow you to use third