Difference between revisions of "Knowledge:Access manager"
From OpenKM Documentation
m |
|||
Line 10: | Line 10: | ||
This will reduce OpenKM performance (at least in search) but will match customer requirements. | This will reduce OpenKM performance (at least in search) but will match customer requirements. | ||
+ | |||
+ | == Difference between "simple" and "recursive" == | ||
+ | |||
+ | Give this repository structure: | ||
+ | |||
+ | * okm:root | ||
+ | ** fld-level-1a | ||
+ | *** fld-level-2a | ||
+ | **** fld-level-3a | ||
+ | ***** doc-a | ||
+ | ***** doc-b | ||
+ | ***** doc-c | ||
+ | **** fld-level-3b | ||
+ | ** fld-level-1b | ||
+ | ** fld-level-1c |
Revision as of 10:37, 6 October 2012
By default OpenKM 6 is configured this way:
security.access.manager = simple security.search.evaluation = lucene
Which provides great performance by only evaluating a single node. But if you want to evaluate every parent you can change this behavior with these settings:
security.access.manager = recursive security.search.evaluation = [ am_more | am_window | am_limited ]
This will reduce OpenKM performance (at least in search) but will match customer requirements.
Difference between "simple" and "recursive"
Give this repository structure:
- okm:root
- fld-level-1a
- fld-level-2a
- fld-level-3a
- doc-a
- doc-b
- doc-c
- fld-level-3b
- fld-level-3a
- fld-level-2a
- fld-level-1b
- fld-level-1c
- fld-level-1a