endpoint for consistency and security. 2.2.3. HOW TO UPDATE A PROFILE FROM THE PUBLIC INTERNET Before we get into how to update a profile directly from a request coming from the public internet, we’ll help use the form values to perform any action that is desired. Let’s look at a concrete example. Before we get started you should know that this example is already available to directly test in Apache this value you should edit the `etc/users.properties`file and it is required to modify this login before going to production. Finally the rule itself should be pretty self-explanatory but there are a

the snippet. All events sent to Unomi must be associated with a scope, that must have been created before events are accepted. So in order to make sure the events are collected with the above Javascript endpoint for consistency and security. 3.1.4. HOW TO UPDATE A PROFILE FROM THE PUBLIC INTERNET Before we get into how to update a profile directly from a request coming from the public internet, we’ll modified to use aliases starting Unomi 2 Upon merge: Properties are copied to the master profile as before An alias is created for the "master" profile with the ID of the merged profile Merged profiles

package, available here : http://www.elasticsearch.org Apache Unomi 1.1.x - Documentation - 7 . Before deploying, make sure that you have Apache Karaf properly installed. You will also have to increase default to make build time minimal, but it is recommended to run the integration tests at least once before using the server to make sure that everything is ok in the build. Another way to use these tests Performance tests are based on Gatling. You need to have a running context server or cluster of servers before executing the tests. Test parameteres are editable in the performance-tests/src/test/scala/unomi/Parameters