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 4.10.4. Features repositories 4.10.5. Boot features 4.10.6. Features Developer Guide 5.1. Developer commands 5.1.1. Dump 5.1.2. Diagnostic 5.1.3. Dynamic import 5.1.4. OSGi framework 5.1.5. Stack traces printout 5.1.6. Bundle tree 5.1.7. Watch 5.2. Scripting 5.2.1. Bundles 5.9.1. Add extended information to bundles 5.9.2. Wiki Syntax 5.10. Creating bundles for non OSGi third party dependencies 5.10.1. Dynamically wrapping jars 5.10.2. Statically bundling jars 5.11

is a OSGi-based runtime which provides a lightweight container onto which various components and applications can be deployed. Apache Karaf uses either Apache Felix Framework or Eclipse Equinox OSGi frameworks managed directly from a main instance (root). APACHE KARAF OVERVIEW 5 • OSGi frameworks: Apache Karaf is not tight to one OSGi framework. By default, Apache Karaf runs with Apache Felix Framework, but karaf@root()> feature:install camel-spring karaf@root()> bundle:install -s mvn:org.apache.camel/ camel-example-osgi/2.10.1 The example installed is using Camel to start a timer every 2 seconds and output a message

installation of the decanter-collector-log feature is enough.  The Decanter log collector is using osgi:DecanterLogCollectorAppender appender. In order to work, your Apache Karaf Pax Logging configuration rootLogger = DEBUG, out, osgi:* If you want, you can explicitly specify the DecanterLogCollectorAppender appender: log4j.rootLogger = DEBUG, out, osgi:DecanterLogCollectorAppender, osgi:VmLogAppender 1.2 feature:install decanter-collector-eventadmin By default, the eventadmin collector is listening for all OSGi framework and Karaf internal events. You can specify additional events to trap by providing

installation of the decanter-collector-log feature is enough. NOTE The Decanter log collector is using osgi:DecanterLogCollectorAppender appender. In order to work, your Apache Karaf Pax Logging configuration actually process the message logs. log4j.rootLogger = DEBUG, out, osgi:* log4j.rootLogger = DEBUG, out, osgi:DecanterLogCollectorAppender, osgi:VmLogAppender 1.2.3. Log Socket The Decanter Log Socket Collector feature installs the eventadmin collector: By default, the eventadmin collector is listening for all OSGi framework and Karaf internal events. You can specify additional events to trap by providing a ‘etc/

8.3. Deploying bundles using the cluster OBR 9. OSGi Event Broadcasting support (eventadmin) 9.1. Enable OSGi Event Broadcasting support 9.2. OSGi Event Broadcast in action 10. HTTP Balancer 10.1 support synchronization of OSGi EventAdmin, OBR (URLs and bundles). The second goal is to provide a Distributed OSGi runtime. It means that using Cellar, you are able to call an OSGi service located on a remote feature adds support of OSGi EventAdmin on the cluster: The cellar-obr feature adds support of OBR sync on the cluster: The cellar-dosgi feature adds support of DOSGi (Distributed OSGi): The cellar-cloud

8.3. Deploying bundles using the cluster OBR 9. OSGi Event Broadcasting support (eventadmin) 9.1. Enable OSGi Event Broadcasting support 9.2. OSGi Event Broadcast in action 10. DOSGi and Transport support synchronization of OSGi EventAdmin, OBR (URLs and bundles). The second purpose is to provide a Distributed OSGi runtime. It means that using Cellar, you are able to call an OSGi service located on a 3 | OBR cluster support cellar-eventadmin | 3.0.3 | | karaf-cellar-3.0.3 | OSGi events broadcasting in clusters cellar-cloud | 3.0.3 | | karaf-cellar-3

contains both system properties and configuration properties. These settings are then fed to the OSGi and other configuration files using placeholder that look something like this: Default values are secured. For each trusted third party server, you need to add these 3 lines : org.osgi.service.http.port.secure=9443 org.osgi.service.http.port=8181 org.apache.unomi.cluster.public.address=http://localhost:8181 following command: And the corresponding rule can be deleted using the following command: INJECT AN OSGI SERVICE IN A GROOVY SCRIPT It’s possible to use the services provided by unomi directly in the groovy

service 6.1. OBR metadata access 6.2. OSGi bundles access 7. Administration Overview Apache Karaf Cave is an Apache Karaf sub-project. It provides an OSGi Bundle Repository (OBR) and Karaf Features you to directly register a Cave repository into an OBR RepositoryAdmin OSGi service. • Artifact Upload: Users can upload OSGi bundle in a Cave repository. It supports URLs like mvn:groupId/artifactId/version able to get artifacts present on an "external" repository (local file: or remote http:), looking for OSGi bundles, and copy the artifacts in the Cave repository storage. The cave-server feature provides

box in the Apache Unomi server. There are two ways to register rules : either by building a custom OSGi bundle plugin or using the REST API to directly send a JSON representation of the rule to be saved contains both system properties and configuration properties. These settings are then fed to the OSGi and other configuration files using placeholder that look something like this: contextserver.publicAddress=${org $MY_KARAF_HOME/etc/unomi.custom.system.properties (and create it if you haven’t yet) file: org.osgi.service.http.port.secure=9443 org.osgi.service.http.port=8181 If you change these ports, also make sure you adjust the

------------------------------------- * removed INDEX.LIST entries from Spring jar META-INF dirs * fixed OSGi metadata for optional "javax.inject" package import * fixed AbstractResource's InputStream-based "contentLength()" if resource type does not have a filename * Resource "contentLength()" implementations work with OSGi bundle resources and JBoss VFS resources * PathMatchingResourcePatternResolver preserves caching MediaType Changes in version 3.1 RC2 (2011-11-28) --------------------------------------- * fixed OSGi manifest for spring-web bundle to not require Apache HttpComponents anymore * fixed GenericTypeResolver