just accept it despite the warning it is safe. 10) Request your first context by simply accessing : http://localhost:8181/cxs/context.js?sessionId=1234 11) If something goes wrong, you should check the http://localhost:8181/cxs to see the list of available RESTful services or retrieve an initial context at http://localhost:8181/cxs/context.json (which isn’t very useful at this point). You can now find an introduction "timeoutInMilliseconds": "1500", "contextServerCookieName": "context-profile-id", "activateWem": true, "trackerSessionIdCookieName":

3.1. Retrieving your first context. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14 2.3.2. Retrieving a context as a JSON object.. . . . . Accessing profile properties in a context . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 2.3.4. Sending events using the context servlet . . . . . . . . . . . . 30 2.5.7. REST API Security. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30 2.5.8. Scripting security . . . . . . . . .

with the context server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 2.2.4. Retrieving context information from Unomi using the context servlet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23 2.6.4. REST API Security. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . collects using the concept of Item which provides the base information (an identifier and a type) the context server needs to process and store the data. Items are persisted according to their type (structure)