This indicates that all the Unomi services are started and ready to react to requests. You can then open a browser and go to http://localhost:8181/cxs to see the list of available RESTful services or retrieve to update profiles using events. This is also the safest way to update a profile because if you design your events to be as specific as possible to your needs, only the data that you specified will be nodes. If you have an application-level firewall you should only allow the following connections open to the whole world : • http://localhost:8181/context.js • http://localhost:8181/eventcollector

This indicates that all the Unomi services are started and ready to react to requests. You can then open a browser and go to http://localhost:8181/cxs to see the list of available RESTful services or retrieve the sample code. The page is very simple, you will see a Twitter button, which, once clicked, will open a new window to tweet about the current page. The original page should be updated with the new values xhr.withCredentials = true; xhr.open("GET", url + "&payload=" + encodeURIComponent(data), true); } else if ("withCredentials" in xhr) { xhr.open("POST", url, true); xhr.withCredentials

schema required us to modify Apache Unomi data model, One of the key differences is the removal of open maps. The properties field in the events objects provided by unomi are now restricted by JSON schema This indicates that all the Unomi services are started and ready to react to requests. You can then open a browser and go to http://localhost:8181/cxs to see the list of available RESTful services or retrieve nodes. If you have an application-level firewall you should only allow the following connections open to the whole world : http://localhost:8181/cxs/context.js (http://localhost:8181/cxs/context.js)