you can completely manage the container. • Dynamic Configuration: Apache Karaf provides a set of command dedicated for the management of the configuration files. All configuration files are centralized referenced as . START THE SERVER Open a command line console and change the directory to . To start the server, run the following command in Windows: bin\karaf.bat respectively on Unix: Unix: bin/karaf You should see the following information on the command line console: __ __ ____ / //_/____ __________ _/ __/ / ,< / __ `/ ___/ __ `/ /_ / /| |/ /_/ / / / /_/ /

Whitebox-Service paradigm (recommended) 4.20.4. Schedule a new Job using the Gogo Shell 4.20.5. Schedule a command 4.20.6. Schedule a new Job using the Scheduler Service 4.20.7. Update scheduling of an existing Statically bundling jars 5.11. Blueprint 5.12. SCR 5.13. Archetypes 5.13.1. Create a command (karaf-command-archetype) 5.13.2. Create an OSGi bundle (karaf-bundle-archetype) 5.13.3. Create an OSGi 255 characters. 2.2. Start the server Open a command line console and change the directory to . To start the server, run the following command in Windows: respectively on Unix: You should

reacts when new lines are appended into a file (especially a log file). It acts like the tail Unix command. Basically, it’s an alternative to the log collector. The log collector reacts to local Karaf log filter the lines read from the file using the regex property. For instance: regex=(.*foo.*) Only the line matching the regex will be sent to the dispatcher. For instance, instead of the log collector send any new line matching the regex in this log file as collected data. PARSER By default, the collector use the org.apache.karaf.decanter.impl.parser.IdentityParser parser to parse the line into a typed

reacts when new lines are appended into a file (especially a log file). It acts like the tail Unix command. Basically, it’s an alternative to the log collector. The log collector reacts for local Karaf log file collector configuration file: The file collector will tail on karaf.log file, and send any new line in this log file as collected data. 1.2.5. EventAdmin The Decanter EventAdmin Collector is an event-driven appenders # # The format is command.key=command_to_execute # where command is a reserved keyword used to identify a command property # for instance: # # command.df=df -h # command.free=free # # You can also

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 you are logged on (the local node) group (see link:groups for details about cluster groups) • you explicitly call the cluster:sync command We have a synchronizer per resource: feature, bundle, config, eventadmin (optional), obr (optional) cluster group) in the etc/ org.apache.karaf.cellar.groups.cfg configuration file: The cluster:sync command allows you to "force" the sync: default.bundle.sync = cluster default.config.sync = cluster default

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 you are logged on (the local node) cluster group (see [groups] for details about cluster groups) • you explicitly call the cluster:sync command We have a synchronizer per resource: feature, bundle, config, obr (optional). Cellar supports three cluster group) in the etc/ org.apache.karaf.cellar.groups.cfg configuration file: The cluster:sync command allows you to "force" the sync: default.bundle.sync = cluster default.config.sync = cluster default

define /var/cave/store for the storage.location property. 2.1. Create The cave:repository-create command creates a new repository: A repository is identified by a name, my-repository in our example. Apache 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 location. 2.3. Repository and OBR service By default, Apache installed repositories using the obr:url-list command: You can refresh a repository or install a repository in the OBR service using the cave:repository-install command: karaf@root()> cave:repository-create

define /var/cave/store for the storage.location property. 2.1. Create The cave:repository-create command creates a new repository: A repository is identified by a name, my-repository in our example. Apache the artifacts that you want to pick up to populate the repository. The cave:repository-populate command accepts a regex option for the filter. For instance, to pick up only joda-time version 2 artifact doesn’t monitor the remote repository. It means that you have to call the cave:proxy-repository command each time the remote repository change (new artifacts, etc). NB: a best practice is to create a