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 /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. version: '3

/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: "interest2" : 2, "interest3" : 3 } }; console.log(properties); // this will trigger a second page view for the same page (the first page view 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

sessionId; successCallback(response); } } else { console.log("contextserver: " + xhr.status + " ERROR: " + xhr.statusText); if (errorCallback) { webmaster@apache.org DocumentRoot /var/www/vhosts/unomi.apache.org/html CustomLog /var/log/apache2/access-unomi.apache.org.log combined Options FollowSymLinks AllowOverride None