Work Definition (Types of Activities)
This section defines what the activity should do (i.e. the action) and on what items (the item set). As of midPoint 4.4, the following items are supported (MT means "Supports multi-threading", MN means "Support multi-node operation"):
Item | Meaning | Activity type | MT | MN | Parameter | Meaning | Default |
---|---|---|---|---|---|---|---|
|
Recomputes specified objects. |
Simple |
Y |
Y |
|
What objects to recompute. |
All of |
|
What options to use. |
|
|||||
Imports specified resource objects. |
Simple |
Y |
Y |
|
What resource objects to import. |
This is obligatory parameter. |
|
Reconciles specified resource objects. |
Predefined composite |
Y |
Y |
|
What resource objects to reconcile. |
This is obligatory parameter. |
|
Processes asynchronous updates for given resource objects (EXPERIMENTAL). |
Simple |
Y |
N |
|
What resource objects to receive updates for. (Not all configuration items are supported - TODO.) |
This is obligatory parameter. |
|
Processes live synchronization events for give resource objects. |
Simple |
Y |
N |
|
What resource objects to synchronize. |
This is obligatory parameter. |
|
|
See Live Synchronization. |
0 |
|||||
|
See Live Synchronization. |
|
|||||
|
Cleans up obsolete objects: audit records, closed tasks, closed cases, closed certification campaigns, output reports, and dead nodes. |
Predefined composite |
N |
N |
|
Cleanup policies to be used. (Specifying typically max. age and/or max. number of records to keep.) |
Global cleanup policies defined in the system configuration. |
|
Exports any report in a "classical" way. (Does not support bucketing.) |
Simple |
Y |
N |
|
Definition of the report. |
Obligatory. |
|
Definition of the report parameters. |
No parameters. |
|||||
|
Exports a report on repository objects or audit records. |
Predefined composite |
Y |
Y |
|
Definition of the report. |
Obligatory. |
|
Definition of the report parameters. |
No parameters. |
|||||
|
Imports a report. |
Simple |
Y |
N |
|
Definition of the report. |
Obligatory. |
|
Definition of the report parameters. |
No parameters. |
|||||
|
Report data to be imported. |
Obligatory. |
|||||
|
Executes a script (a.k.a. bulk action) over a set of objects. |
Simple |
Y |
Y |
|
What objects to process. |
All objects in repo. |
|
Script to execute ( |
Obligatory. |
|||||
|
Executes a script (a.k.a. bulk action) on an empty or explicitly specified input. NOTE: not implemented yet, but hopefully will be in 4.4. |
Simple |
N |
N |
|
Script to execute ( |
Obligatory. |
Executes validity scan on focal objects. |
Predefined composite |
Y |
Y |
|
What objects to scan. |
All of |
|
|
How to find the objects: |
|
|||||
|
Custom validity constraint. |
None. |
|||||
|
Executes trigger scan on repository objects. Invokes trigger handlers for any triggers that have fire time less than or equal |
Simple |
Y |
Y |
|
What objects to scan. If a query is present, the filter computed by the activity is added to it (as a conjunction). |
All of |
Looks for pending operations in shadows and updates their status. |
Simple |
Y |
Y |
|
What shadows to process. If a query with filter is present, it replaces the default query. If a query without filter is present, the default filter is "implanted" into it (reusing e.g. the ordering). |
All shadows with pending operations. |
|
|
Executes specified changes on specified objects. |
Simple |
Y |
Y |
|
What objects to process. |
All of |
|
What delta to apply. |
Obligatory. |
|||||
|
What execution options to use. |
Default execution options. |
|||||
|
Re-indexes specified repository objects. |
Simple |
Y |
Y |
|
What objects to reindex. |
All of |
|
Deletes all shadows that have not been updated for given time. (I.e. their |
Simple |
Y |
Y |
|
What shadows to check. The task works only if given resource is not in maintenance mode. If a query is specified, it is always appended to the default time-scanning query. |
Obligatory. |
|
How "stale" must be a shadow to be deleted. |
Obligatory. |
|||||
|
The purpose of this activity is to detect and optionally fix anomalies in repository objects. However, currently its only function is to display information about objects size. |
Simple |
N |
N |
|
What objects to analyze. |
All objects in repository. |
|
Number of columns in the histograms of object sizes. |
80 |
|||||
The purpose of this activity is to detect and optionally anomalies in resource object shadows stored in the repository. |
Simple |
N |
N |
|
What shadows to analyze. |
All shadows. |
|
|
Aspects that should be diagnosed. |
All. |
|||||
|
Aspects that should be fixed. |
None. |
|||||
|
Class name of the duplicate shadows resolver to be used. |
Built-in one. |
|||||
|
Whether to check uniqueness on primary identifiers (or on secondary ones as well). |
|
|||||
Adapts running activities to the current cluster configuration by executing "reconcile workers" operation when the cluster state changes (i.e. a node goes up or down). |
Simple |
Y |
Y |
|
Tasks that should be considered for auto-scaling. (Any task must be multi-node, running, and the auto-scaling for it must not be disabled.) |
All eligible tasks. |
|
|
Minimal interval between reconciliations, i.e. it will not reconcile workers if this time has not elapsed since the last one. |
0 |
|||||
|
Maximal interval between reconciliations, i.e. it will always reconcile workers after this time has elapsed since the last one. |
infinity |
|||||
|
Whether to skip initial reconciliation of the workers on the activity start. |
|
|||||
Executes eligible pending operations on a resource. |
Simple |
Y |
Y |
|
Resource on which the operation propagation should be done. |
Obligatory. |
|
Executes eligible pending operations on set of resources. |
Simple |
Y |
Y[1] |
|
Set of resources on which the operation propagation should be done. |
All resources. |
|
|
"No operation" activity to be used for demonstration and testing purposes. It consists of a set of numbered steps, each taking a given time. |
Simple |
Y |
Y |
|
Duration of each step in milliseconds. |
0 |
|
Number of steps. |
1 |
|||||
|
Should a step of this activity be interruptible? Value of |
|
|||||
|
This is a place for customer-provided activities. |
Simple |
Customer-provided activities can have any configuration items and distribution (multi-threading, clustering) properties.