of available commands and '[cmd] --help' for help on a specific command. 8 QUICK START Hit '' or type 'system:shutdown' or 'logout' to shutdown Karaf. karaf@root()> SOME SHELL BASICS You can *:feature *:instance *:jaas *:kar *:log *:package *:region *:service *:shell *:ssh addbundle addfilter addregion alias cancel cl clear clone config config:cancel -u Shows the update locations --help Display this help message --table Show bundles using a shell table -t Specifies the bundle threshold; bundles with a start-level less than this value will not

4.x - Documentation 1. Overview 2. Quick Start 2.1. Prerequisites 2.2. Start the server 2.3. Shell console basics 2.4. Deploy a sample application 2.5. Stopping and uninstalling the sample application 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

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 chapter assumes that you already know Apache Karaf basics, especially the notion of features and shell usage. 3.1. Registering Cellar features Karaf Cellar is provided as a Karaf features XML descriptor

Broadcasting commands User Guide 1. Introduction 1.1. Use Cases The first goal of Karaf Cellar is to synchronize the status of several Karaf instances (named nodes). Cellar provides dedicated shell commands chapter assumes that you already know Apache Karaf basics, especially the notion of features and shell usage. 3.1. Registering Cellar features Karaf Cellar is provided as a Karaf features XML descriptor 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

and linking . . . . . . . . . . . . . . . . . . . . . . . . . . . 36 2 Contents 6 The VirtualBox shell 37 7 Main API change log 39 7.1 Incompatible API changes with version 3.2 . . . . . . . . . . . This should work on all Unix-like systems such as Linux and Solaris. For Windows systems, use commands similar to what is used in the Makefile. This will compile the clienttest.java code on the first bindings/glue/python/sample direc- tory, which contains an example of a simple interactive shell able to control a VirtualBox in- stance. The shell is written using the API layer, thereby hiding different implementation

and linking . . . . . . . . . . . . . . . . . . . . . . . . . . . 36 2 Contents 6 The VirtualBox shell 37 7 Main API change log 39 7.1 Incompatible API changes with version 3.2 . . . . . . . . . . . This should work on all Unix-like systems such as Linux and Solaris. For Windows systems, use commands similar to what is used in the Makefile. This will compile the clienttest.java code on the first bindings/glue/python/sample direc- tory, which contains an example of a simple interactive shell able to control a VirtualBox in- stance. The shell is written using the API layer, thereby hiding different implementation

events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39 4 The VirtualBox shell 41 5 Classes (interfaces) 43 5.1 IAdditionsStateChangedEvent (IEvent) . . . . . . . . . . . . . This should work on all Unix-like systems such as Linux and Solaris. For Windows systems, use commands similar to what is used in the Makefile. This will compile the clienttest.java code on the first bindings/glue/python/sample direc- tory, which contains an example of a simple interactive shell able to control a VirtualBox in- stance. The shell is written using the API layer, thereby hiding different implementation

events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40 4 The VirtualBox shell 42 5 Classes (interfaces) 44 5.1 IAdditionsFacility . . . . . . . . . . . . . . . . . . . . . . This should work on all Unix-like systems such as Linux and Solaris. For Windows systems, use commands similar to what is used in the Makefile. This will compile the clienttest.java code on the first bindings/glue/python/sample direc- tory, which contains an example of a simple interactive shell able to control a VirtualBox in- stance. The shell is written using the API layer, thereby hiding different implementation

events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40 4 The VirtualBox shell 42 5 Classes (interfaces) 44 5.1 IAdditionsFacility . . . . . . . . . . . . . . . . . . . . . . . instead. This should work on all Unix-like systems such as Linux and Solaris. For Windows systems, use commands similar to what is used in the Makefile. This will compile the clienttest.java code on the first bindings/glue/python/sample direc- tory, which contains an example of a simple interactive shell able to control a VirtualBox in- stance. The shell is written using the API layer, thereby hiding different implementation