array is created with two objects that associated personalization IDs with content IDs. Then we build the personalization object that contains the two IDs and their associated conditions (only a condition s/mvel.json with an array of regular expressions that will contain the allowed expressions. 3. Build the project and deploy it to Apache Unomi Warning: Do not make regular expressions too general. They result will look something like this: 8.3. AGGREGATIONS Aggregations are a very powerful way to build queries in Apache Unomi that will collect and aggregate data by filtering on certain conditions.

analytics.js- integration-apache-unomi.js apply your modification in this file then use the command yarn build to compile a new JS file. Then you can use the test page to try your changes http://localhost:8181/tracker/ this: { "_avg":1.0, "_sum":9.0 } 3.3. AGGREGATIONS Aggregations are a very powerful way to build queries in Apache Unomi that will collect and aggregate data by filtering on certain conditions. minutes and 10 seconds. See http://camel.apache.org/ftp.html and http://camel.apache.org/file2.html to build more complex source path. Also be careful with FTP configuration as most servers no longer support

BUILDING Simply type at the root of the project: mvn clean install -P generate-package The Maven build process will generate both a standalone package you can use directly to start the context server already installed Apache Karaf server (see "Deploying into an existing Karaf server") If you want to build and run the integration tests, you should instead use : mvn -P integration-tests clean install 2 Environment (build 1.7.0_51-b13) Java HotSpot(TM) 64-Bit Server VM (build 24.51-b03, mixed mode) 2.1.4. RUNNING THE INTEGRATION TESTS The integration tests are not executed by default to make build time minimal