shows schema validation failure at the $.source.properties path. Note that the validation will output one log line for the exact failing path and a log line for its parent, therefore to find the source ID or aliases from the same cookie ( context-profile-id ) or body parameters ( profileId ) Verb Path Description GET /cxs/profiles/PROFILE_ID_OR_ALIAS Retrieves a profile by ID or Alias ID (useful data is compatible with the specified schema. Example of a basic JSON schema that validates that the path property is a string property: Apache Unomi is using json-schema-validator to integrate JSON schema

with the following information: window.digitalData.page = window.digitalData.page || { path: location.pathname + location.hash, pageInfo: { pageName: document.title, empty URL to make it relative to this page. initialPageProperties: { path: path, pageInfo: { destinationURL: location.href, such as categories, // tags or interests. path = location.pathname + location.hash; properties = { path: path, pageInfo: { destinationURL:

MY_DIRNAME=`dirname $0` MY_KARAF_HOME=`cd "$MY_DIRNAME/.."; pwd` export KARAF_OPTS="-Djava.library.path=$MY_KARAF_HOME/lib/sigar" export JAVA_MAX_MEM=3G export JAVA_MAX_PERM_MEM=384M . You will by using the gatling.conf file in performance-tests/src/test/resources : export GATLING_CONF=<path>/performance-tests/src/test/resources gatling.sh Reports are generated in performance-tests/target/results