not match a known schema, it will be rejected by Apache Unomi 2. Apache Unomi 2 also introduces a set of administrative endpoints allowing new schemas and/or schemas extensions to be registered. More make it ready for prime time. 1.1.7. MIGRATE FROM UNOMI 1.X To facilitate migration we prepared a set of scripts that will automatically handle the migration of your data from Apache Unomi 1.5+ to Apache (https://www.oracle.com/technetwork/java/javase/downloads/jdk8-downloads-2133151.html) and make sure you set the JAVA_HOME variable https://docs.oracle.com/cd/E19182-01/820-7851/inst_cli_jdk_javahome_t/ (see

(https://www.oracle.com/technetwork/java/javase/downloads/jdk8-downloads- 2133151.html) and make sure you set the JAVA_HOME variable https://docs.oracle.com/cd/E19182-01/ 820-7851/inst_cli_jdk_javahome_t/ (see (Preferred) Use you own custom event(s) to send data you want to be inserted in a profile, and use rules to map the event data to the profile. This is simpler than it sounds, as usually all it requires is setting will deploy a rule that will copy data coming from the event into a profile. But we will need to map the form field names to profile names, and this can be done using the setPropertyAction that’s available

scope is represented in Unomi by a simple string identifier and usually represents an application or set of applications from which Unomi gathers data, depending on the desired analysis granularity. In the providing values for parameters defined in the associated `ActionType. Example actions include: “Set user property x to value y” or “Send a message to service x”. CONDITIONTYPE `ConditionType`s define for a profile or session property, specifying how possible values are constrained, if the value is multi-valued (a vector of values as opposed to a scalar value). `PropertyType`s can also be categorized