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
Last revision Both sides next revision
devel:documentation:application_configuration:dev:scheduled_tasks:task-scheduler [2020/03/03 15:57]
kopro add tags 		devel:documentation:application_configuration:dev:scheduled_tasks:task-scheduler [2020/06/17 20:27]
tomiskar
Line 68: Line 68:
  
 Task can be executed repetitively without reschedule is needed. When task is canceled (e.g. by server is restarted), then task can be executed again (~recovered) directly from long running task agenda. New task will be created and executed with the same configuration as original task. **When task** is stateful and **supports queue**, then **already processed items will not be processed again**. Task can be executed repetitively without reschedule is needed. When task is canceled (e.g. by server is restarted), then task can be executed again (~recovered) directly from long running task agenda. New task will be created and executed with the same configuration as original task. **When task** is stateful and **supports queue**, then **already processed items will not be processed again**.
-To enable this feature, task method ''isRecoverable'' has to be overiden and return ''true''. 
  
-{{ :devel:documentation:application_configuration:dev:scheduled_tasks:recoverable-task.png |}}+ 
 +<note>To enable this feature, task method ''isRecoverable'' has to be overiden and return ''true''.</note> 
 + 
 +<note important>Only tasks created and **running** in the version **10.2.0** and higher can be run again!</note> 
 + 
 +{{ :devel:documentation:application_configuration:dev:scheduled_tasks:lrt-sync-recreation.png |}}
  
  
Line 115: Line 119:
   * ``Synchronization uuid`` - synchronization configuration to schedule.   * ``Synchronization uuid`` - synchronization configuration to schedule.
  
-==== AddNewAutomaticRoleTaskExecutor ====+==== <del>AddNewAutomaticRoleTaskExecutor</del> ==== 
 + 
 +@deprecated since 10.4.0 - ''ProcessAutomaticRoleByTreeTaskExecutor'' is used from version 10.4.0.
  
 Long running task for add newly added automatic role to users. Can be executed repetitively to assign role to unprocessed identities, after process was stopped or interrupted (e.g. by server restart). Long running task for add newly added automatic role to users. Can be executed repetitively to assign role to unprocessed identities, after process was stopped or interrupted (e.g. by server restart).
Line 128: Line 134:
 === Parameters === === Parameters ===
   * ``roleTreeNode`` - automatic role identifier.   * ``roleTreeNode`` - automatic role identifier.
 +
 +==== ProcessAutomaticRoleByTreeTaskExecutor ====
 +
 +@since 10.4.0
 +
 +Recalculate automatic role by tree structure for contracts and positions. Recalculate roles for identities with contract or other position match selected automatic role by tree structure. Can be executed repetitively to assign role to unprocessed identities, after process was stopped or interrupted (e.g. by server restart).
 +
 +=== Parameters ===
 +  * ``roletreenode`` - automatic roles by tree structure to recount.
 +
 +==== ProcessAllAutomaticRoleByTreeTaskExecutor ====
 +
 +@since 10.4.0
 +
 +Recalculate all automatic roles by tree structure for contracts and positions. Recalculate all roles for identities with contract or other position assigned by automatic role by tree structure. Can be executed repetitively to assign role to unprocessed identities, after process was stopped or interrupted (e.g. by server restart).
 +
 +==== ProcessSkippedAutomaticRoleByTreeTaskExecutor ====
 +
 +@since 10.4.0
 +
 +Recalculate skipped automatic role by tree structure. Recalculate automatic roles by tree structure, which were not processed (skipped) after tree structure was changed (e.g. from synchronization).
 +
 +==== ProcessSkippedAutomaticRoleByTreeForContractTaskExecutor ====
 +
 +@since 10.4.0
 +
 +Recalculate skipped automatic role by tree structure for contracts and other positions. Recalculate automatic roles by tree structure for contracts and other positions, which were not processed (skipped) after work position was changed (e.g. from synchronization).
  
 ==== AddNewRoleCompositionTaskExecutor ==== ==== AddNewRoleCompositionTaskExecutor ====
Line 226: Line 259:
 === Parameters === === Parameters ===
   * ``Number of days`` - Delete events older than given number of days.   * ``Number of days`` - Delete events older than given number of days.
 +
 +<code sql>
 +-- PostgreSql
 +-- Delete events older then 3 days
 +delete from idm_entity_event where result_state='EXECUTED' AND created <= NOW() - INTERVAL '72 HOURS';
 +vacuum full idm_entity_event;
 +</code>
  
 ==== DeleteLongRunningTaskExecutor==== ==== DeleteLongRunningTaskExecutor====
Line 303: Line 343:
   * ``Workflow definition`` - Delete historic workflow processes with this definition only.   * ``Workflow definition`` - Delete historic workflow processes with this definition only.
  
 +==== VsSystemGeneratorTaskExecutor ====
 +
 +@since 10.4.0
 +
 +Task generates given number of virtual systems, roles and identities. All generated entities are evenly distributed among themselves. I.e. Roles assigned to users and connected to generated systems. Task serves for generating required scenario and following performance test.
 +
 +=== Parameters ===
 +  * ``Item prefix`` - A name prefix of all generated entities. Serves for easier searching of entities in IdM.
 +  * ``System count`` - Number of generated virtual systems.
 +  * ``Role count`` - Number of generated roles.
 +  * ``User count`` - Number of generated identities.
  
 ===== Testing tips ===== ===== Testing tips =====
  • by apeterova