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 the values from the event to the profile. Note that the setPropertyName will define the property to set on the profile and the setPropertyValue will define where the value is coming from. In this example allowedEvents=${env:UNOMI_THIRDPARTY_PROVIDER1_A LLOWEDEVENTS:-login,updateProperties} The events set in allowedEvents will be secured and will only be accepted if the call comes from the specified IP

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 specific event is raised so that other parts of Unomi can react accordingly. SCORING `Scoring`s are set of conditions associated with a value to assign to profiles when matching so that the associated users