we feature in this tutorial is extracted from our tracker sample which is available here: https://github.com/apache/unomi/blob/master/extensions/web- tracker/wab/src/main/webapp/index.html . However you to modify them to fit your use case, which might result in errors. The best approach during development is to enable Apache Unomi debug mode, which will provide you with more detailed logs about events "target" properties. Apache Unomi ships with a set of predefined JSON Schemas, detailed here: https://github.com/apache/unomi/tree/master/extensions/json- schema/services/src/main/resources/META-INF/cxs/schemas

more interesting to use the REST API to create and manipulate rules, as they don’t require any development or deployments on the Apache Unomi server. curl -X POST http://localhost:8181/cxs/rules \ --user address. In our login sample we provide an example of such a rule. You can find it here: https://github.com/apache/unomi/blob/master/samples/login-integration/src/main/resources/META-INF/ cxs/rules/exampleLogin container. You can find the list of all the environment variable names in the following file: https://github.com/apache/unomi/blob/master/package/src/main/resources/etc/custom.system.properties If you are

needed if you didn’t use the generated package. Also, this is the preferred way to install a development environment if you intend to re-deploy the context server KAR iteratively. Additional requirements: HTML PAGE The code for the HTML page with our Tweet button can be found at https://github.com/apache/incubator-unomi/blob/master/wab/src/main/webapp/index.html. Apache Unomi 1.1.x - Documentation