. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 1.2.2. Plugin structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . instantiated when needed with actual values. 1.2.2. 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 specific metadata to tell Unomi the kind of entities it provides. A plugin can provide the following entities to extend Unomi, each with its associated definition (as a JSON file), located in a specific

details what just happened. 2.3.1. PREREQUISITES This document assumes working knowledge of git (https://git-scm.com/) to be able to retrieve the code for Unomi and the example. Additionally, you will basically two ways to create a new rule : Using the REST API Packaging it as a predefined rule in a plugin In both cases the JSON structure for the rule will be exactly the same, and in most scenarios it you require or are already using custom expressions, you should add a plugin to Apache Unomi to allow for this. The choice of a plugin was to make sure only system administrators and solution developers

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146 11.5. Plugin structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148 11.7.1. Creating a plugin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . greater details what just happened. 2.1.1. PREREQUISITES This document assumes working knowledge of git to be able to retrieve the code for Unomi and the example. Additionally, you will require a