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. In the context internal processes for example when a rule is triggered. Events are sent to Unomi from client applications using the JSON format and a typical page view event from a web site could look something like profiles are not part of a scope since we want to be able to track the associated user across applications. For this reason, data collected for a given profile in a specific scope is still available to

lector) All other ports should not be accessible to the world. For your Apache Unomi client applications (such as the Jahia CMS), you will need to make the following ports accessible : The Apache Unomi Context Server administration REST API, so it is highly recommended that you design your client applications to use the HTTPS port for accessing the REST API. The user accounts to access the REST API are Updating applications consuming Unomi - Migrating your existing data 7.3. UPDATING APPLICATIONS CONSUMING UNOMI Since Apache Unomi is an engine, you’ve probably built multiple applications consuming

llector All other ports should not be accessible to the world. For your Apache Unomi client applications (such as the Jahia CMS), you will need to make the following ports accessible : 8181 (Context Context Server administration REST API, so it is highly recommended that you design your client applications to use the HTTPS port for accessing the REST API. The user accounts to access the REST API are 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. In the context