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 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. The above rule will be executed if the incoming event actions;version 8181 (Context Server HTTP port) 9443 (Context Server HTTPS port) karaf/karaf karaf.local.user = karaf For your context servers, and for any standalone Elasticsearch nodes you will need to

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 change the following property in the $MY_KARAF_HOME/etc/unomi.custom.system.properties : karaf.local.user = karaf For your context servers, and for any standalone Elasticsearch nodes you will need to for the server. Apache Unomi 1.x - Documentation - 113 BUILDING THE TWEET BUTTON SAMPLES In your local copy of the Unomi repository and run: cd samples/tweet-button-plugin mvn clean install This will

way to install a development environment if you intend to re-deploy the context server KAR iteratively. Additional requirements: - Apache Karaf 3.0.2+, http://karaf.apache.org - Local copy of the Elasticsearch context.json (which isn’t very useful at this point). BUILDING THE TWEET BUTTON SAMPLE In your local copy of the Unomi repository and run: cd samples/tweet-button-plugin mvn clean install This will