not allowed in most IaaS providers and the alternative of specifying all IP addresses creates maintenance difficulties, especially since in most cases the addresses are not known in advance. Cellar solves repository and 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 allows us to setup a cluster with zero configuration and no dependency to external systems such as a database or a shared file system. See the Hazelcast documentation at http://www.hazelcast.com/documentation

not allowed in most IaaS providers and the alternative of specifying all IP addresses creates maintenance difficulties, especially since in most cases the addresses are not known in advance. Cellar solves repository and 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 allows us to setup a cluster with zero configuration and no dependency to external systems such as a database or a shared file system. See the Hazelcast documentation at http://www.hazelcast.com/documentation

Decanter dispatcher. 1.2.19. JDBC The Decanter JDBC collector periodically executes a query on a database and sends the query result to the dispatcher. Apache Karaf Decanter 2.x - Documentation - 19 connect to the database. You can create this datasource using the Karaf jdbc:create command (provided by the jdbc feature). • the query property contains the SQL query to perform on the database and retrieve from the collectors) into a database. The Decanter JDBC appender transforms the data as a json string. The appender stores the json string and the timestamp into the database. The decanter-appender-jdbc

provides additional login modules (see the developer guide for details): • JDBCLoginModule uses a database as backend • LDAPLoginModule uses a LDAP server as backend • SyncopeLoginModule uses Apache Syncope │ false │ true │ 53 couchdb │ CouchDB is a database that uses JSON for documents, an HTTP API, & JavaScript/declarative indexing. │ false │ true feature provides an OSGi service to create/delete JDBC datasources in the container and perform database operations (SQL queries). This JDBC OSGi service can be manipulated programmatically (see the developer

from the collectors) into a database. The Decanter JDBC appender transforms the data as a json string. The appender stores the json string and the timestamp into the database. The decanter-appender-jdbc allows you to specify the connection to the database: • the datasource.name property contains the name of the JDBC datasource to use to connect to the database. You can create this datasource using the command (provided by the jdbc feature). • the table.name property contains the table name in the database. The Decanter JDBC appender automatically creates the table for you, but you can create the table

BackendEngineFactory org.apache.karaf.jaas.modules.jdbc.JDBCBackendEngineFactory The JDBCLoginModule uses a database to load the users, passwords and roles from a provided data source (normal or XA). The data source undesirable to use plain text passwords in configuration files. To avoid this problem it is good to store database SECURITY FRAMEWORK 183 passwords in encrypted format and use encrypted property placeholders when