2.5. Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27 2.5.1. Centralized configuration . . . . . . . . . . . . . . . . . . . 27 2.5.2. Changing the default configuration using environment variables (i.e. Docker configuration) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27 2.5.3. Changing the default configuration using property files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28 2.5.4. Secured events configuration. . . . . . . . . . . . . . . . .

and running you can go look at the request examples to learn basic requests you can do once your server is up and running. 2.4. UNOMI WEB TRACKING TUTORIAL In this tutorial we will guide through the create and manipulate rules, as they don’t require any development or deployments on the Apache Unomi server. The above rule will be executed if the incoming event is of type myEvent and will simply copy be quite complex. Please remember that the more complex the more resources it will consume on the server and potentially this could affect performance. 3.1.8. GETTING / UPDATING CONSENTS You can find

. . . . . . . . . . . . . . . . . . . . . . . . . . . 7 2.1.2. Deploying into an existing Karaf server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 2.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 2.2.3. Interacting with the context server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22 2.6. Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .