wide range of applications and technologies. It also supports the "run anywhere" concept (on any machine with Java, cloud, docker images, …) using the embedded mode. It’s a lightweight, powerful, and 0/bin/karaf-service /etc/init.d/ To start the service when the machine is rebooted: $ update-rc.d karaf-service defaults To disable starting the service when the machine is rebooted: $ update-rc.d -f karaf-service remove OpenSSH: On Windows, you can use Putty, Kitty, etc. If you don’t have a SSH client installed on your machine, you can use the Apache Karaf client. ssh:ssh command Apache Karaf itself provides a SSH client

/etc/ init.d/ To start the service when the machine is rebooted: $ update-rc.d karaf-service defaults To disable starting the service when the machine is rebooted: $ update-rc.d -f karaf-service remove karaf@root()> On Windows, you can use Putty, Kitty, etc. If you don't have SSH client installed on your machine, you can use Apache Karaf client. ssh:ssh command Apache Karaf itself provides a SSH client. When repository entry. For example http://www.example.org/repo@snapshots Repositories on the local machine are supported through file:/ URLs. ARTIFACTS REPOSITORIES AND URLS 71 Provisioning Apache Karaf

addresses) of the different Cellar nodes: By default, it will bind to all interfaces on the node machine. It’s possible to specify a interface: NB: in previous Hazelcast versions (especially the one used feature:repo-add cellar 4.0.0 karaf@node1()> feature:install cellar WARNING if you run the nodes on a single machine, you have to provision etc/ org.ops4j.pax.web.cfg configuration file containing the org.osgi.service

an index (1 by default): # #index.number_of_replicas: 1 # Note, that for development on a local machine, with small indices, it usually # makes sense to "disable" the distributed features: # #index.number_of_shards: that the ES_MIN_MEM and ES_MAX_MEM environment variables are set # to the same value, and that the machine has enough memory to allocate # for Elasticsearch, leaving enough memory for the operating system

system. Apache Karaf Decanter 2.x - Documentation - 12 This collector gets lot of details about the machine. The decanter-collector-oshi feature installs the oshi system collector: karaf@root()> feature:install Karaf Decanter 2.x - Documentation - 13 By default, the oshi collector gets all details about the machine. You can filter what you want to harvest in this configuration file. 1.2.11. SYSTEM (SCRIPT) The

addresses) of the different Cellar nodes: By default, it will bind to all interfaces on the node machine. It’s possible to specify a interface: NB: in previous Hazelcast versions (especially the one used