7. Cluster setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63 7.1. Cluster setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136 11.1.1. Initial Setup. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Documentation - 7 curl -X POST http://localhost:8181/context.json?sessionId=1234 \ -H "Content-Type: application/json" \ -d @- <<'EOF' { "source": { "itemId":"homepage", "itemType":"page"

--request POST 'http://localhost:8181/cxs/scopes' \ -u 'karaf:karaf' \ --header 'Content-Type: application/json' \ --data-raw '{ "itemId": "apache", "itemType": "scope" }' Is replaced by the following /cxs/scopes' \ --header 'Authorization: Basic a2FyYWY6a2FyYWY=' \ --header 'Content-Type: application/json' \ --data-raw '{ "itemId": "unomi-tracker-test", "metadata": { "id": "unomi-tracker-test" ents/search' \ --header 'Authorization: Basic a2FyYWY6a2FyYWY=' \ --header 'Content-Type: application/json' \ --data-raw '{ "sortby" : "timeStamp:desc", "condition" : { "type" : "matchAllCondition"

3. Cluster setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28 3.1. Cluster setup . . . . . A given scope is represented in Unomi by a simple string identifier and usually represents an application or set of applications from which Unomi gathers data, depending on the desired analysis granularity a time-bounded interaction between a user (via their associated profile) and a Unomi-enabled application. A session represents the sequence of actions the user performed during its duration. For this