in mind that for Apache Unomi 2.0 we do not support “hot” migration, the migration process will require a shutdown of your cluster to guarantee that no new events will be collected while data migration (https://git-scm.com/) to be able to retrieve the code for Unomi and the example. Additionally, you will require a working Java 11 or above install. Refer to http://www.oracle.com/technetwork/java/javase/ (http://www purposes only. Again, prefer the custom events solution because as this is a protected event it will require sending the Unomi key as a request header, and as Unomi only supports a single key for the moment

knowledge of git to be able to retrieve the code for Unomi and the example. Additionally, you will require a working Java 8 or above install. Refer to http://www.oracle.com/technetwork/java/javase/ purposes only. Again, prefer the custom events solution because as this is a protected event it will require sending the Unomi key as a request header, and as Unomi only supports a single key for the moment scenarios it will be 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

server such as Jenkins, Apache Gump, Atlassian Bamboo or others. Note : the integration tests require a JDK 7 or more recent ! Apache Unomi 1.1.x - Documentation - 9 To run the tests simply activate knowledge of git to be able to retrieve the code for Unomi and the example. Additionnally, you will require a working Java 7 or above install. Refer to http://www.oracle.com/technetwork/java/javase/ consequences of the rule matching. We only need one action of type incrementTweetNumberAction that doesn’t require any parameters. ACTION DEFINITION Let’s now look at our custom incrementTweetNumberAction action