this section of the documentation we provide quick recipes focused on helping you achieve a specific result with Apache Unomi. 3.1.2. ENABLING DEBUG MODE Although the examples provided in this documentation (they will work "as-is"), you might be tempted 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 properties and configuration properties. These settings are then fed to the OSGi and other configuration files using placeholder that look something like this: Default values are stored in a file called $MY_

. . . . . . . . . . . . . . . . . . 27 2.5.3. Changing the default configuration using property files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28 2.5.4. Secured events configuration section of the documentation we provide quick recipes focused on helping you achieve a specific result with Apache Unomi. 2.2.2. HOW TO READ A PROFILE The simplest way to retrieve profile data for the properties and configuration properties. These settings are then fed to the OSGi and other configuration files using placeholder that look something like this: contextserver.publicAddress=${org.apache.unomi

profiles as soon as collected data permits positive association between distinct profiles, usually as a result of the user performing some identifying action in a context where the user hadn’t already been positively be categorized using tags or file system structure, using sub-directories to organize definition files. Apache Unomi 1.1.x - Documentation - 5 RULE `Rule`s are conditional sets of actions to be executed memory size and perm gen size by adjusting the following environment values in the bin/setenv(.bat) files (at the end of the file): MY_DIRNAME=`dirname $0` MY_KARAF_HOME=`cd "$MY_DIRNAME/.."; pwd`