of Unomi’s 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 createElement('script'), s=d.getElementsByTagName('script')[0]; g.type='text/javascript'; g.defer=true; g.async=true; g.src=u+'context.js'; s.parentNode.insertBefore(g,s); })(); 2.2. GETTING STARTED information as is the case when the requested URI is context.json. However, if the client requests context.js then useful functions to interact with Unomi are added to the cxs

that developers might include the credentials to access it in non- secure parts of code such as client-side code. Since there is no difference between this endpoint and any other administration-focused unomiTracker}}(i)}unomiTracker.load=function(){var n=document.createElement("script");n.type="text/javascript",n.async=!0,n.src=unomiOption.url+"/tr acker/unomi- tracker.min.js",n.addEventListener?n.addEventListener("load" http://localhost:8181/eventcollector 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

is that developers might include the credentials to access it in non-secure parts of code such as client-side code. Since there is no difference between this endpoint and any other administration-focused s/eventcollector) 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 to the 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