Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision 		Previous revision
devel:documentation:architecture:dev:events:init-data [2021/03/10 10:36]
tomiskar 		devel:documentation:architecture:dev:events:init-data [2021/10/06 12:20] (current)
tomiskar
Line 39: Line 39:
 | core | core-init-scheduled-task-processor | Schedule core long running tasks. | 10000 | no | | core | core-init-scheduled-task-processor | Schedule core long running tasks. | 10000 | no |
 | acc | acc-init-scheduled-task-processor | Schedule acc long running tasks. | 10100 | no | | acc | acc-init-scheduled-task-processor | Schedule acc long running tasks. | 10100 | no |
 +| core | core-init-monitoring-processor | Init monitoring manager and product provided monitoring evaluators. | 11000 | yes |
 +| acc | acc-init-monitoring-processor | Init product provided monitoring evaluators. | 11010 | yes |
 +| vs | vs-init-monitoring-processor | Init product provided monitoring evaluators. | 11020 | yes |
  
 **Column disableable** - processor can be disabled by additional property ''idm.sec.core.init.data.enabled=false''. Each processor can be disabled by standard [[..:..:..:application_configuration:dev:backend#entity_event_processors|processor configuration]] with processor identifier usage. **Column disableable** - processor can be disabled by additional property ''idm.sec.core.init.data.enabled=false''. Each processor can be disabled by standard [[..:..:..:application_configuration:dev:backend#entity_event_processors|processor configuration]] with processor identifier usage.
  • by tomiskar