to lookup profiles by main (Unomi) ID or by any other alias ID Aliases are just IDs stored in a dedicated index A profile may have an unlimited number of aliases attached to it. HOW TO USE THEM Here es/META-INF/base/BaseScript.groovy) REST API Actions can be deployed/updated/deleted via the dedicated /cxs/groovyActions rest endpoint. Deploy/update an Action: A Groovy Action can be updated by following karaf command: Doing so will output logs similar to this: 5.3.2. VALIDATEEVENT ENDPOINT A dedicated Admin endpoint (requires authentication), accessible at: cxs/jsonSchema/validateEvent , was created

CONFIGURATIONS It is recommended to have one node dedicated to the context server, where the other nodes take care of the Elasticsearch persistence. The node dedicated to the context server will have node.data data set 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 numberOfReplicas=0 monthlyIndex.numberOfReplicas=0 3 NODES CONFIGURATION One node dedicated to context server, 2 nodes for elasticsearch storage with fault-tolerance Node A : node.data=false

by default a Base script defined here REST API Actions can be deployed/updated/deleted via the dedicated /cxs/groovyActions rest endpoint. Apache Unomi 1.x - Documentation - 32 Deploy/update an Action: Since Apache Unomi version 1.5.0 every type of items (see section: Items) is now stored in a dedicated separated index. 8.19.2. API CHANGES To be able to handle the multiple indices the Persistence migration tool. 8.20. IMPORTANT CHANGES IN PUBLIC SERVLETS SINCE VERSION 1.5.5 What used to be dedicated servlets are now part of the REST endpoints. Prior to version 1.5.5 the following servlets were