PROFILE PROPERTIES IN A CONTEXT By default, in order to optimize the amount of data sent over the network, Apache Unomi will not send the content of the profile or session properties. If you need this data call and get an updating context, or if you don’t need the context and want to send events in a network optimal way you can use the eventcollector servlet (see below). 3.2.5. SENDING EVENTS USING THE context, you should use the eventcollector servlet that is optimized respond quickly and minimize network traffic. Here is an example of using this servlet: curl -X POST http://localhost:8181/cxs/context

PROFILE PROPERTIES IN A CONTEXT By default, in order to optimize the amount of data sent over the network, Apache Unomi will not send the content of the profile or session properties. If you need this data call and get an updating context, or if you don’t need the context and want to send events in a network optimal way you can use the eventcollector servlet (see below). 2.3.5. SENDING EVENTS USING THE context, you should use the eventcollector servlet that is optimized respond quickly and minimize network traffic. Here is an example of using this servlet: Apache Unomi 1.x - Documentation - 16 curl -X

and configure its cluster. You just need to install multiple context servers on the same network, and enable the discovery protocol in $MY_KARAF_HOME/etc/org.apache.unomi.persistence.elasticsearch elasticsearch.cfg file : discovery.zen.ping.multicast.enabled=true All nodes on the same network, sharing the same cluster name will be part of the same cluster. Apache Unomi 1.1.x - Documentation - 28 Unomi 1.1.x - Documentation - 29 3.1.2. SPECIFIC CONFIGURATION If multicast is not allowed on your network, you’ll need to switch to unicast protocol and manually configure the server IPs. This can be done