should look something like this: 1. Login to a social platform 2. Call back to a special secured system that performs an server-to-server call to send the login event to Apache Unomi using the Unomi key form-mapping-example The parameter is the itemId of the rule. If you want to see all the rules deployed in the system you can use the command : unomi:rule-list 1000 The 1000 parameter is the limit of number of objects CENTRALIZED CONFIGURATION Apache Unomi uses a centralized configuration file that contains both system properties and configuration properties. These settings are then fed to the OSGi and other configuration

incremented on each page reload. You can also use the rule-list command to display all the rules in the system and the rule-tail to watch in real-time which rules are executed. The rule-view RULE_ID command yet introduced more advanced notions such as profile segmentation or Groovy action scripting. The system is capable of much more, for example by directly using its actions to integrate with third-party '' for a list of available commands and '[cmd] --help' for help on a specific command. Hit 'system:shutdown' to shutdown Karaf. Hit '' or type 'logout' to disconnect shell from current session

values as opposed to a scalar value). `PropertyType`s can also be categorized using tags or file system structure, using sub-directories to organize definition files. Apache Unomi 1.1.x - Documentation 1.6.0_65-b14-462, x86_64: "Java SE 6" /System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home 1.6.0_65-b14-462, i386: "Java SE 6" /System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home