server KAR iteratively. Additional requirements: - Apache Karaf 3.0.2+, http://karaf.apache.org - Local copy of the Elasticsearch ZIP package, available here : http://www.elasticsearch.org Apache Unomi 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 to false. 2 NODES CONFIGURATION One node dedicated to context server, 1 node for elasticsearch storage. Node A : node.data=true numberOfReplicas=0 monthlyIndex.numberOfReplicas=0 Node B : node.data=false

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 Elasticsearch cluster must have enough capacity to handle the migration. At a minimum, the required capacity storage capacity must be greater than the size of the dataset in production + the size of the largest index Unomi plugin, a standard extension point for the server. BUILDING THE TWEET BUTTON SAMPLES In your local copy of the Unomi repository and run: This will compile and create the OSGi bundle that can be deployed

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