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

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

PLUGIN STRUCTURE Being built on top of Apache Karaf, Unomi leverages OSGi to support plugins. A Unomi plugin is, thus, an OSGi bundle specifying some specific metadata to tell Unomi the kind of entities the plugin provides and inject any required dependency. The Blueprint file is located, as usual, at OSGI-INF/blueprint/blueprint.xml in the bundle JAR file. The plugin otherwise follows a regular maven feature:repo-add cxf 2.7.11 feature:install -v cxf/2.7.11 . Create a new $MY_KARAF_HOME/etc/org.apache.cxf.osgi.cfg file and put the following property inside : org.apache.cxf.servlet.context=/cxs . Copy