7.17.5 with Apache Unomi 2.0, this ensure you are on a recent version that is not impacted by the log4j vulnerabilities (fixed in Elasticsearch 7.16.3). This version increase is releated to Apache Unomi available in prior versions of Elasticsearch, we do not recommend using those due to the above-mentioned log4j vulnerabilities. 2. DISCOVER UNOMI 2.1. QUICK START WITH DOCKER Begin by creating a docker-compose 5 (please make sure you use the proper version : 7.17.5) 3) Uncompress it and change the config/elasticsearch.yml to include the following config : cluster.name: contextElasticSearch

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85 8.15. List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . -2 (please make sure you use the proper version : 7.4.2) 3) Uncompress it and change the config/elasticsearch.yml to include the following config : cluster.name: contextElasticSearch /context.js?sessionId=1234 11) If something goes wrong, you should check the logs in ./data/log/karaf.log. If you get errors on ElasticSearch, make sure you are using the proper version. Next steps:

condition can test the event itself, but also the profile or the session. Once a rule triggers, a list of actions can be performed as consequences. Also, when rules trigger, a specific event is raised that can be assigned to properties ("primitive" types). 1.2.4. OTHER UNOMI ENTITIES USERLIST User list are simple static lists of users. The associated profile stores the lists it belongs to in a specific might need to select the JDK to run the tests in the itests subproject. In order to do so you can list the installed JDKs with the following command : /usr/libexec/java_home -V which will output something