5.1.6. Bundle tree 5.1.7. Watch 5.2. Scripting 5.2.1. Assignation 5.2.2. Expressions 5.2.3. List, maps, pipes and closures 5.2.4. Startup 5.2.5. Constants and variables 5.2.6. Built-in variables service: it’s a very flexible and extensible container, covering all the major needs. Here is a short list of provided features: • Hot deployment: simply drop a file in the deploy directory, Apache Karaf / /| |/ /_/ / / / /_/ / __/ /_/ |_|\__,_/_/ \__,_/_/ Apache Karaf (4.2.0) Hit '' for a list of available commands and '[cmd] --help' for help on a specific command. Hit '' or type 'system:shutdown'

service: it's a very flexible and extensible container, covering all the major needs. Here is a short list of provided features: • Hot deployment: simply drop a file in the deploy directory, Apache Karaf / /| |/ /_/ / / / /_/ / __/ /_/ |_|\__,_/_/ \__,_/_/ 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 '' config:cancel config:delete config:edit config:list config:property-append config:property-delete config:property-list config:property-set config:update connect

listeners is at your own risk. The nodes list could be discovered (using unicast or multicast), or "static" defined (using a couple hostname or IP and port list). Cellar is able to synchronize: * bundles installed: cd [karaf_install_dir]/src mvn karaf@root()> feature:repo-add cellar karaf@root()> feature:list |grep -i cellar karaf@root()> feature:install cellar karaf@root()> la|grep -i cellar And Cellar Cellar cluster node, and hence tries to discover the others Cellar nodes. You can list the known Cellar nodes using the list-nodes command: The starting x indicates that it’s the Karaf instance on which

listeners is at your own risk. The nodes list could be discovered (using unicast or multicast), or "staticly" defined (using a couple hostname or IP and port list). Cellar is able to synchronize: • bundles components (bundles) installed: And Cellar cluster commands are now available: karaf@root()> feature:list |grep -i cellar cellar-core | 3.0.3 | | karaf-cellar-3.0.3 | Karaf clustering Cellar cluster node, and hence tries to discover the others Cellar nodes. You can list the known Cellar nodes using the list-nodes command: The starting x indicates that it’s the Karaf instance on which

Apache Karaf Cave features 1.3. 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 feature:repo-add mvn:org.apache.karaf.cave/apache-karaf-cave/3.0.0/xml/ features karaf@root()> feature:list |grep -i cave cave-server | 3.0.0 | x | karaf-cave-3.0.0 | karaf@root()> repository. If you create a new empty repository, these options don’t have really any effect. 2.2. List You can list the repositories using the cave:repositories command: You can find the repository name and

############################### # Decanter Kafka Configuration ############################### # A list of host/port pairs to use for establishing the initial connection to the Kafka cluster #bootstrap For Elasticsearch 1.x: karaf@root()> feature:install elasticsearch karaf@root()> feature:version-list elasticsearch ############################################################################### ##################### discovery (enabled by default): # #discovery.zen.ping.multicast.enabled: false # # 2. Configure an initial list of master nodes in the cluster # to perform discovery when new nodes (master or data) are started:

############################### # Decanter Kafka Configuration ############################### # A list of host/port pairs to use for establishing the initial connection to the Kafka cluster #bootstrap ################################## # Decanter JMS Kafka Configuration ################################## # A list of host/port pairs to use for establishing the initial connection to the Kafka cluster #bootstrap allows you to define how the messages are sent to the Kafka broker: • the bootstrap.servers contains a list of host:port of the Kafka brokers. Default value is localhost:9092. • the client.id is optional

Apache Karaf Cave features 1.3. Starting 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 feature url mvn:org.apache.karaf.cave/apache-karaf-cave/4.0.0/xml/features karaf@root()> feature:list|grep -i cave cave-server | 4.0.0 | | Uninstalled | repository. If you create a new empty repository, these options don’t have really any effect. 2.2. List You can list the repositories: 3. Populate repository You can add new artifacts in a repository. 3.1