4.7. Log 4.7.1. Configuration files 4.7.2. Log4j v2 support 4.7.3. karaf.log.console property 4.7.4. Commands 4.7.5. JMX LogMBean 4.7.6. Advanced configuration 4.8. Configuration 4.8.1. Environment JMX ConfigMBean 4.9. Artifacts repositories and URLs 4.9.1. Maven URL Handler 4.9.2. Maven configuration commands 4.10. Provisioning 4.10.1. Application 4.10.2. OSGi 4.10.3. Feature and resolver Feature bundles 4.10.9. Dependent features 4.10.10. Feature configurations 4.10.11. Feature configuration files 4.10.12. Commands 4.10.13. Deployer 4.10.14. JMX FeatureMBean 4.11. Deployers 4.11

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 in the etc folder folder. Any change in a configuration file is taken on the fly. • Advanced Logging System: Apache Karaf supports a large set of Logging framework (slf4j, log4j, etc). Whatever the logging framework you you use, Apache Karaf centralizes the configuration in one file. • Provisioning: Apache Karaf supports a large set of URL where you can install your application (Maven repository, HTTP, file, etc). It also

collector: karaf@root()> feature:install decanter-collector-log The log collector doesn’t need any configuration, the installation of the decanter-collector-log feature is enough.  The Decanter log collector order to work, your Apache Karaf Pax Logging configuration should contain this appender. The default Apache Karaf etc/org.ops4j.pax.logging.cfg configuration file is already fine: log4j.rootLogger = default etc/org.apache.karaf.decanter.collector.log.socket.cfg configuration file containing: # # Decanter Log/Log4j Socket collector configuration # #port=4560 #workers=10 • the port property defines the

1.0 karaf@root()> feature:install decanter-collector-log The log collector doesn’t need any configuration, the installation of the decanter-collector-log feature is enough. NOTE The Decanter log collector order to work, your Apache Karaf Pax Logging configuration should contain this appender. The default Apache Karaf etc/org.ops4j.pax.logging.cfg configuration file is already fine: If you want, you can installs the collector and a default etc/ org.apache.karaf.decanter.collector.log.socket.cfg configuration file containing: • the port property defines the port number where the collector is bound and

automatically installed, providing the etc/hazelcast.xml configuration file. The etc/hazelcast.xml configuration file contains all the core configuration, especially: * the Hazelcast cluster identifiers (group (group name and password) * network discovery and security configuration karaf@root()> cluster: karaf@root()> feature:install cellar-event karaf@root()> feature:install cellar-obr karaf@root()> cluster). 4.2. Network The element in the etc/hazelcast.xml contains all the network configuration. First, it defines the port numbers used by Hazelcast: Second, it defines the mechanism used

automatically installed, providing the etc/hazelcast.xml configuration file. The etc/hazelcast.xml configuration file contains all the core configuration, especially: * the Hazelcast cluster identifiers (group (group name and password) * network discovery and security configuration karaf@root()> cluster: karaf@root()> feature:install cellar-event karaf@root()> feature:install cellar-obr karaf@root()> cluster). 4.2. Network The element in the etc/hazelcast.xml contains all the network configuration. First, it defines the port numbers used by Hazelcast: Second, it defines the mechanism used

KARAF_BASE/cave. You can change the storage location in the etc/org.apache.karaf.cave.server.storage.cfg configuration file: karaf@root()> cave: cave:repositories cave:repository-create cav

ad You can change the storage location in the etc/org.apache.karaf.cave.server.storage.cfg configuration file: For instance, you can define /var/cave/store for the storage.location property. 2.1. Create