service 5.1. Repository metadata access 6. Maven wrapper service 7. Administration 7.1. JMX 7.2. REST Overview Apache Karaf Cave is an Apache Karaf sub-project. Cave is an implementation of the OSGi Repository specification, providing additional features such as a complete Maven repository support, a REST API for management, support of remote repository proxy. Cave deals with the requirements and capabilities act as a complete Maven repository, allowing you to use Cave directly with Maven. • REST API: Cave provides a REST API to manipulate the repositories. • Artifact Upload: Users can upload OSGi bundle

Notifier 1.2.10. System 1.2.11. Network socket 1.2.12. JMS 1.2.13. MQTT 1.2.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 similar to the Decanter Kafka appender. Please, see Kafka collector for details. 1.2.15. Rest Servlet The Decanter Rest Servlet collector registers a servlet on the OSGi HTTP service (by default on /decanter/collect /decanter/collect ). It listens for incoming collected messages on this servlet. The decanter-collector-rest-servlet feature installs the collector: 1.3. Appenders Decanter appenders receive the data from

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17 1.2.16. Rest Servlet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . to the Decanter Kafka appender. Please, see the Kafka collector for details. 1.2.16. REST SERVLET The Decanter Rest Servlet collector registers a servlet on the OSGi HTTP service (by default on /decanter/collect) servlet. The decanter-collector-rest-servlet feature installs the collector: Apache Karaf Decanter 2.x - Documentation - 18 karaf@root()> feature:install decanter-collector-rest-servlet 1.2.17. SOAP The

configuration, features information, other) and a topic which is used to exchange events with the rest of the group nodes. architecture Each group comes with a configuration, which defines which events event, broadcast the event to the cluster and hold the unit state to a shared resource, so that the rest of the nodes can look up and retrieve the changes. shared architecture For instance, we want all change occurs on a.b.c. "Karaf A" updated the shared repository data for a.b.c and then notifies the rest of the nodes that a.b.c has changed. Each node looks up the shared repository and retrieves changes

configuration, features information, other) and a topic which is used to exchange events with the rest of the group nodes. architecture Each group comes with a configuration, which defines which events event, broadcast the event to the cluster and hold the unit state to a shared resource, so that the rest of the nodes can look up and retrieve the changes. shared architecture For instance, we want all change occurs on a.b.c. "Karaf A" updated the shared repository data for a.b.c and then notifies the rest of the nodes that a.b.c has changed. Each node looks up the shared repository and retrieves changes

Working with profiles 5.24. Security & JAAS 5.25. Servlet 5.26. WAR 5.27. HTTP Resources 5.28. REST service 5.29. SOAP service 5.30. Websocket 5.31. Scheduler 5.32. Quick example with Apache Camel | openejb-cxf | 4.5.2 | | openejb-features | openejb-rest | 4.5.2 | | openejb-features | openejb-soap | uses the Syncope REST API to authenticate users and retrieve the roles. The Syncope login module just requires one parameter: Name Description address Location of the Syncope REST API version Syncope

behavior of the completer depending on the commands already executed, in the current shell or even the rest of the arguments that have been already passed to the command. Such example is the config:set-property uses the Syncope REST API to authenticate users and retrieve the roles. The Syncope login module just requires one parameter: Name Description address Location of the Syncope REST API admin.user Admin