accessing : http://localhost:8181/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 ElasticSearch is developed and breaking changes are introduced quite often. If in doubt, don’t hesitate to check with the Apache Unomi community to get the latest information about ElasticSearch version compatibility little more involved, is much preferred. When sending a login event, you can setup a rule that can check a profile property to see if profiles can be merged on an universal identifier such as an email address

accessing : http://localhost:8181/cxs/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 ElasticSearch version specified in the documentation whenever possible. If in doubt, don’t hesitate to check with the Apache Unomi community to get the latest information about ElasticSearch version compatibility increments a property called pageViewCount on the user’s profile. You can then reload then page and check with the profile-view PROFILE_UUID SSH command that the profile was updated with the new property

select the one you want using : export JAVA_HOME=`/usr/libexec/java_home -v 1.7.0_51` and then check that it was correctly referenced using: java -version which should give you a result such as this: fairly straightforward: we retrieve the profile associated with the event that triggered the rule and check whether it already has the properties we are interested in. If not, we create the associated property