"interest3" : 3 } }; console.log(properties); // this will trigger a second page view for the same page (the first page view is in the tracker snippet). window yActions' \ --user karaf:karaf \ --form 'file=@hello-world.groovy' Finally, register a rule to trigger execution of the groovy action: Apache Unomi 1.x - Documentation - 33 curl -X POST 'http://loc “world!”, which is then used in the log message triggered by the action. You can now use unomi to trigger a “view” event and see the corresponding message in the Unomi logs. Once you’re done with the Hello

ns' \ --user karaf:karaf \ --form 'file=@hello-world.groovy' BASH Finally, register a rule to trigger execution of the groovy action: Note that this rule contains a “location” parameter, with the value “world!”, which is then used in the log message triggered by the action. You can now use unomi to trigger a “view” event and see the corresponding message in the Unomi logs. Once you’re done with the Hello without a reindexing step. The script in position "10" will introduce its own painless script, then trigger the re-indexation. This way you don’t have to re-index the same indices twice. You can find existing

session. Once a rule triggers, a list of actions can be performed as consequences. Also, when rules trigger, a specific event is raised so that other parts of Unomi can react accordingly. SCORING `Scoring`s page is provided at the following URL: http://localhost:8181/index.html This test page will trigger the loading of the /context.js script, which will try to retrieving the user context or create a user profile using a ContextServlet request triggering a custom event. This event will, in turn, trigger a Unomi action on the server implemented using a Unomi plugin, a standard extension point for the