following in Apache Unomi 2.x: If using the default Apache 1.x data model, our Unomi 2 migration process will handle the data model changes for you. If you are using custom events/objects, please refer worth keeping 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 to modify them to fit your use case, which might result in errors. The best approach during development is to enable Apache Unomi debug mode, which will provide you with more detailed logs about events

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 \ --user Item which provides the base information (an identifier and a type) the context server needs to process and store the data. Items are persisted according to their type (structure) and identifier (identity) system to add information to a profile you should use the identify event type and add a rule to only process the data you want to accept. If you want to add/update/delete properties in a secure manner from

Item which provides the base information (an identifier and a type) the context server needs to process and store the data. Items are persisted according to their type (structure) and identifier (identity) 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 (see "Deploying "Deploying the generated package") or a KAR file that you can then deploy using a manual deployment process into an already installed Apache Karaf server (see "Deploying into an existing Karaf server") If