WebContainer (JSP/Servlet) 4.17.3. Naming (JNDI) 4.17.4. Transaction (JTA) 4.17.5. DataSources (JDBC) 4.17.6. JMS 4.17.7. Persistence (JPA) 4.17.8. EJB 4.17.9. CDI 4.17.10. HA/failover and cluster 3. Profiling 5.15.4. Monitoring 5.16. Configuration 5.17. Deployer 5.18. Dump extender 5.19. JDBC & JPA 5.20. JMS 5.21. Custom log appender 5.22. Custom JMX MBean 5.23. Working with profiles directly provide a features repository name to the feature:repo-add command. For install, to install PAX JDBC, you can do: ################################################################################ # #

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19 1.2.19. JDBC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25 1.3.4. JDBC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . available, the collector will get the metrics and send to the Decanter dispatcher. 1.2.19. JDBC The Decanter JDBC collector periodically executes a query on a database and sends the query result to the

14. Kafka 1.2.15. Rest Servlet 1.3. Appenders 1.3.1. Log 1.3.2. Elasticsearch & Kibana 1.3.3. JDBC 1.3.4. JMS 1.3.5. Camel 1.3.6. Kafka 1.3.7. Redis 1.3.8. MQTT 1.3.9. Cassandra 1.3.10. MongoDB http://host:8181/ elasticsearch-head . 1.3.3. JDBC The Decanter JDBC appender allows your to store the data (coming from the collectors) into a database. The Decanter JDBC appender transforms the data as a json appender stores the json string and the timestamp into the database. The decanter-appender-jdbc feature installs the jdbc appender: karaf@root()> feature:install elasticsearch-head/1.7.3 karaf@root()> feature:install

JDBCLoginModule LoginModule org.apache.karaf.jaas.modules.jdbc.JDBCLoginModule BackendEngineFactory org.apache.karaf.jaas.modules.jdbc.JDBCBackendEngineFactory The JDBCLoginModule uses a database datasource = osgi:javax.sql.DataSource/(osgi.jndi.service.name=jdbc/karafdb) query.password = SELECT PASSWORD FROM className="org.apache.karaf.jaas.modules.jdbc.JDBCLoginModule" flags="required"> datasource = jndi:aries:services/ javax.sql.DataSource/(osgi.jndi.service.name=jdbc/karafdb) query.password = SELECT PASSWORD

| 3.0.2.SNAPSHOT Apache Karaf :: JDBC :: Core | org.apache.karaf.jdbc.core | 3.0 | 1.0.1.SNAPSHOT Apache Karaf :: JDBC :: Command | org.apache.karaf.jdbc.command | 3.0

| 3.0.2.SNAPSHOT Apache Karaf :: JDBC :: Core | org.apache.karaf.jdbc.core | 3.0 | 1.0.1.SNAPSHOT Apache Karaf :: JDBC :: Command | org.apache.karaf.jdbc.command | 3.0

the Cave backend is designed in a plugin way, you can implement your own backend (for instance, JDBC or LDAP backend). • Repository Metadata Generation: Cave creates the repository metadata for you

As the Cave backend is designed in a plugin way, you can implement your own backend (for instance, JDBC or LDAP backend). • OBR Metadata Generation: Karaf Cave automatically creates the OBR metadata for