state 2.8. Summary 3. Update Notes (from Karaf 3.x to 4.x versions) 3.1. Distributions 3.2. Commands 3.3. Features repositories 3.4. Features resolver 3.5. Namespaces 3.6. Maven plugin 3.7. Update 4.1. Service Wrapper 4.4.2. Service Script Templates 4.5. Using the console 4.5.1. Available commands 4.5.2. Subshell and completion mode 4.5.3. Unix like environment 4.5.4. Security 4.6. Remote property 4.7.4. Commands 4.7.5. JMX LogMBean 4.7.6. Advanced configuration 4.8. Configuration 4.8.1. Environment Variables & System Properties 4.8.2. Files 4.8.3. config:* commands 4.8.4. JMX ConfigMBean

/_/ / __/ /_/ |_|\__,_/_/ \__,_/_/ Apache Karaf (3.0.0) Hit '' for a list of available commands and '[cmd] --help' for help on a specific command. 8 QUICK START Hit '' or type 'system:shutdown' Karaf, let's install a sample Apache Camel application for now: In the console, run the following commands: 10 QUICK START karaf@root()> feature:repo-add camel 2.10.0 Adding feature url mvn:org.apache is using Camel to start a timer every 2 seconds and output a message on the console. The previous commands download the Camel features descriptor and install the example feature. >>>> SpringDSL set body:

Architecture Overview 2. Supported Events 3. The role of Hazelcast 4. Design 5. Broadcasting commands User Guide 1. Introduction 1.1. Karaf Cellar use cases The first purpose of Cellar is to synchronize synchronize the state of several Karaf instances (named nodes). Cellar provides dedicated shell commands and MBeans to administrate the cluster, and manipulate the resources on the cluster. It’s also Cellar feature: You can now see the Cellar components (bundles) installed: And Cellar cluster commands are now available: karaf@root()> feature:list |grep -i cellar cellar-core | 3

Architecture Overview 2. Supported Events 3. The role of Hazelcast 4. Design 5. Broadcasting commands User Guide 1. Introduction 1.1. Use Cases The first goal of Karaf Cellar is to synchronize the the status of several Karaf instances (named nodes). Cellar provides dedicated shell commands and JMX MBeans to manage the cluster, and manipulate the resources on the cluster. It’s also possible to cellar karaf@root()> feature:install cellar karaf@root()> la|grep -i cellar And Cellar cluster commands are now available: 3.3. Optional features Optionally, you can install additional features. The

Upload a single artifact 3.2. 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 feature provides the OBR and KFR server, including the storage backend, management layer and shell commands. User Guide 1. Installation This chapter describes how to install Apache Karaf Cave into an existing It could take several minutes depending of your network connection speed. New Apache Karaf Cave commands are now available: 2. Repository A Cave Repository is a container for: • OSGi bundles (jar files)

collector (periodically executed by the Decanter Scheduler). This collector executes operating system commands (or scripts) and send the execution output to the appenders. The decanter-collector-system feature containing: # # Decanter OperationSystem Collector configuration # # This collector executes system commands, retrieve the exec output/err # sent to the appenders # # You can define the number of thread to get the temperature: # # sensors|grep temp1|awk '{print $2}'|cut -b2,3,4,5 # You can add the commands that you want to execute using the format: Apache Karaf Decanter 2.x - Documentation - 14 command

collector (periodically executed by the Decanter Scheduler). This collector executes operating system commands (or scripts) and send the execution output to the appenders. The decanter-collector-system feature ystem # # Decanter OperationSystem Collector configuration # # This collector executes system commands, retrieve the exec output/err # sent to the appenders # # The format is command.key=command_to_execute get the temperature: # # sensors|grep temp1|awk '{print $2}'|cut -b2,3,4,5 # You can add the commands that you want to execute using the format: The collector will execute each command described in

Maven repository for the Cave repositories. After the installation of the cave-server feature, new commands are available: 2. Repository A Cave repository is a container for: • Artifacts (files) • Repository any JMX client (like jconsole for instance), you can do all actions as you can using the cave:* commands: • void createRepository(String name, String location, boolean generate, boolean install) throws