Apache Unomi 2.x - Documentation
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 header adds Basic authorization scheme with base64 encoded karaf:karaf value to the request. The result will now show the list of profiles: 6.5.4. DELETING PROFILE Profile can be deleted using deleteProfile0 码力 | 117 页 | 4.78 MB | 1 年前3Apache Unomi 1.x - Documentation
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 profileID is always server-generated. Injecting a custom cookie with a non-valid profile ID will result in failure to load the profile. Profile ID are UUIDs, which make them (pretty) safe from brute- query endpoint that is quite powerful. It provides ways to perform queries that can quickly get result counts, apply metrics such as sum/min/max/avg or even use powerful aggregations. In this section0 码力 | 158 页 | 3.65 MB | 1 年前3Apache Unomi 1.1.x - Documentation
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 0_51` and then check that it was correctly referenced using: java -version which should give you a result such as this: java version "1.7.0_51" Java(TM) SE Runtime Environment (build 1.7.0_51-b13) Java if any>, "profileSegments":, "filteringResults":<result of the evaluation of personalization filters>, "trackedConditions": 0 码力 | 32 页 | 477.20 KB | 1 年前3
共 3 条
- 1