Unomi 1.x - Documentation - 7 curl -X POST http://localhost:8181/context.json?sessionId=1234 \ -H "Content-Type: application/json" \ -d @- <<'EOF' { "source": { "itemId":"homepage", "itemType":"page" 1.x - Documentation - 9 curl -X POST http://localhost:8181/cxs/rules \ --user karaf:karaf \ -H "Content-Type: application/json" \ -d @- <<'EOF' { "metadata": { "id": "setContactInfo", "name": event using a request similar to this one: curl -X POST http://localhost:8181/eventcollector \ -H "Content-Type: application/json" \ -d @- <<'EOF' { "sessionId" : "1234", "events":[ {

curl --location --request POST 'http://localhost:8181/cxs/scopes' \ -u 'karaf:karaf' \ --header 'Content-Type: application/json' \ --data-raw '{ "itemId": "apache", "itemType": "scope" }' Is replaced by UNOMI 2.1. QUICK START WITH DOCKER Begin by creating a docker-compose.yml file with the following content: From the same folder, start the environment using docker-compose up and wait for the startup to 'http://localhost:8181/cxs/scopes' \ --header 'Authorization: Basic a2FyYWY6a2FyYWY=' \ --header 'Content-Type: application/json' \ --data-raw '{ "itemId": "unomi-tracker-test", "metadata": {

processed and stored by Unomi services. The collected information can then be used to personalize content, derive insights on user behavior, categorize the user profiles into segments along user-definable clients and context server integrators. Context server clients are usually web applications or content management systems. They interact with Unomi by providing raw, uninterpreted contextual data in (errorCallback) { errorCallback(xhr); } } }; xhr.setRequestHeader("Content-Type", "text/plain;charset=UTF-8"); // Use text/plain to avoid CORS preflight if (isGet) {