details). In addition to the remote console, Apache Karaf also provides a remote filesystem. This remote filesystem can be accessed using a SCP/SFTP client. Configuration The configuration of the SSHd or not. When enabled, Karaf SSHd supports SFTP, meaning that you can remotely access the Karaf filesystem with any sftp client. • keySize is the key size used by the SSHd server. The possible values command (or simply logout ) Filesystem clients Apache Karaf SSHd server also provides complete fileystem access via SSH. For security reasons, the available filesystem is limited to KARAF_BASE directory

the following features: • Storage: Cave includes a storage backend. The default one is a simple filesystem backend. As the Cave backend is designed in a plugin way, you can implement your own backend (for cave-server feature is a meta-feature which actually installs: • cave-storage feature providing the Cave filesystem default storage. karaf@root()> feature:repo-add cave 4.0.0 Adding feature url mvn:org.apache.karaf is a container for: • Artifacts (files) • Repository metadata By default, a repository uses a filesystem backend for the storage, the directory used is KARAF_BASE/cave. You can change the storage location

details). In addition of the remote console, Apache Karaf also provides a remote filesystem. This remote filesystem can be accessed using a SCP/SFTP client. Configuration The configuration of the SSHd fileystem access via SSH. For security reason, the available filesystem is limited to KARAF_BASE directory. You can use this remote filesystem with any SCP/SFTP compliant clients. Native SCP/SFTP clients clients On Unix, you can directly use scp command to download/upload files to the Apache Karaf filesystem. For instance, to retrieve the karaf.log file remotely: ~$ scp -P 8101 karaf@localhost:/data/log/karaf

df -k / | awk -F " |%" '/dev/{print $8}' # # This script will get the available space on the / filesystem for instance. # and call the script: # # command.df=/bin/script # # Another example of script to the appenders. For instance, if you want to periodically send the free space available on the / filesystem, you can add: 1.2.11. Network socket The Decanter network socket collector listens for incoming the data harvested by the system collector. The default dashboard expects data containing the filesystem usage, and temperature data. It’s just a sample, you have to tune the system collector and adapt

following features: • Storage: Karaf Cave includes a storage backend. The default one is a simple filesystem backend. As the Cave backend is designed in a plugin way, you can implement your own backend (OSGi Bundle Repository) metadata (aka a repository.xml file) By default, a repository uses a filesystem backend for the storage, the directory used is KARAF_BASE/cave. karaf@root()> feature:repo-add

df -k / | awk -F " |%" '/dev/{print $8}' # # This script will get the available space on the / filesystem for instance. # and call the script: # # command.df=/bin/script # # Another example of script to the appenders. For instance, if you want to periodically send the free space available on the / filesystem, you can add: command.df=df -k / | awk -F " |%" '/dev/{print $8}' 1.2.12. NETWORK SOCKET The

retrieves changes. The architecture as described so far could be implemented using a database/shared filesystem as a shared resource and polling instead of multicasting events. So why use Hazelcast ? Hazelcast

retrieves changes. The architecture as described so far could be implemented using a database/shared filesystem as a shared resource and polling instead of multicasting events. So why use Hazelcast ? Hazelcast