Work Definition (Types of Activities)

Last modified 08 Nov 2024 22:01 +01:00

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

recomputation

Recomputes specified objects.

Simple

Y

Y

objects

What objects to recompute.

All of AssignmentHolderType.

executionOptions

What options to use.

reconcile

import

Imports specified resource objects.

Simple

Y

Y

resourceObjects

What resource objects to import.

This is obligatory parameter.

reconciliation

Reconciles specified resource objects.

Predefined composite

Y

Y

resourceObjects

What resource objects to reconcile.

This is obligatory parameter.

asynchronousUpdate

Processes asynchronous updates for given resource objects (EXPERIMENTAL).

Simple

Y

N

updatedResourceObjects

What resource objects to receive updates for. (Not all configuration items are supported - TODO.)

This is obligatory parameter.

liveSynchronization

Processes live synchronization events for give resource objects.

Simple

Y

N

resourceObjects

What resource objects to synchronize.

This is obligatory parameter.

batchSize

See Live Synchronization.

0

updateLiveSyncTokenInDryRun

See Live Synchronization.

false

shadowReclassification

Reclassification of specified resource objects shadows.

Simple

N

Y

resourceObjects

What resource objects to reclassify.

This is obligatory parameter.

cleanup

Cleans up obsolete objects: audit records, closed tasks, closed cases, closed certification campaigns, output reports, and dead nodes.

Predefined composite

N

N

policies

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.

reportExport

Exports any report in a "classical" way. (Does not support bucketing.)

Simple

Y

N

reportRef

Definition of the report.

Obligatory.

reportParam

Definition of the report parameters.

No parameters.

distributedReportExport

Exports a report on repository objects or audit records.

Predefined composite

Y

Y

reportRef

Definition of the report.

Obligatory.

reportParam

Definition of the report parameters.

No parameters.

reportImport

Imports a report.

Simple

Y

N

reportRef

Definition of the report.

Obligatory.

reportParam

Definition of the report parameters.

No parameters.

reportDataRef

Report data to be imported.

Obligatory.

iterativeScripting

Executes a script (a.k.a. action) over a set of objects.

Simple

Y

Y

objects

What objects to process.

All objects in repo.

scriptExecutionRequest

Script to execute (ExecuteScriptType). Contains scripting expression, options, and variables. Note: input can be set, but it is ignored.

Obligatory.

nonIterativeScripting

Executes a script (a.k.a. action) on an empty or explicitly specified input. NOTE: not implemented yet, but hopefully will be in 4.4.

Simple

N

N

scriptExecutionRequest

Script to execute (ExecuteScriptType). Contains scripting expression, input, options`, and variables.

Obligatory.

focusValidityScan

Executes validity scan on focal objects.

Predefined composite

Y

Y

objects

What objects to scan.

All of FocusType.

queryStyle

How to find the objects: singleQuery or separateObjectAndAssignmentQueries.

singleQuery

validityConstraint

Custom validity constraint.

None.

triggerScan

Executes trigger scan on repository objects. Invokes trigger handlers for any triggers that have fire time less than or equal currentTime. (Unlike validity scanner, this one intentionally ignores lastScanTimestamp.)

Simple

Y

Y

objects

What objects to scan. If a query is present, the filter computed by the activity is added to it (as a conjunction).

All of ObjectType.

shadowRefresh

Looks for pending operations in shadows and updates their status.

Simple

Y

Y

shadows

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.

changeExecution

Executes specified changes on specified objects.

Simple

Y

Y

objects

What objects to process.

All of ObjectType (can be dangerous!)

delta

What delta to apply.

Obligatory.

executionOptions

What execution options to use.

Default execution options.

reindexing

Re-indexes specified repository objects.

Simple

Y

Y

objects

What objects to reindex.

All of ObjectType.

shadowCleanup

Deletes all shadows that have not been updated for given time. (I.e. their fullSynchronizationTimestamp is either null or less or equal "current time - specified interval".)

Simple

Y

Y

shadows

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.

interval

How "stale" must be a shadow to be deleted.

Obligatory.

objectIntegrityCheck

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

objects

What objects to analyze.

All objects in repository.

histogramColumns

Number of columns in the histograms of object sizes.

80

shadowIntegrityCheck

The purpose of this activity is to detect and optionally anomalies in resource object shadows stored in the repository.

Simple

N

N

shadows

What shadows to analyze.

All shadows.

aspectsToDiagnose

Aspects that should be diagnosed.

All.

aspectsToFix

Aspects that should be fixed.

None.

duplicateShadowsResolver

Class name of the duplicate shadows resolver to be used.

Built-in one.

checkDuplicatesOnPrimaryIdentifiersOnly

Whether to check uniqueness on primary identifiers (or on secondary ones as well).

false (meaning all identifiers)

activityAutoScaling

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

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.

minReconciliationInterval

Minimal interval between reconciliations, i.e. it will not reconcile workers if this time has not elapsed since the last one.

0

maxReconciliationInterval

Maximal interval between reconciliations, i.e. it will always reconcile workers after this time has elapsed since the last one.

infinity

skipInitialReconciliation

Whether to skip initial reconciliation of the workers on the activity start.

false

propagation

Executes eligible pending operations on a resource.

Simple

Y

Y

resourceRef

Resource on which the operation propagation should be done.

Obligatory.

multiPropagation

Executes eligible pending operations on set of resources.

Simple

Y

Y[1]

resources

Set of resources on which the operation propagation should be done.

All resources.

noOp

"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

delay

Duration of each step in milliseconds.

0

steps

Number of steps.

1

stepInterruptibility

Should a step of this activity be interruptible? Value of none means that the activity is not interruptible, except at step boundaries. If hard is used, the activity can be interrupted only in "hard" way, i.e. by sending the Java interrupt signal. Finally, full means that the activity can be interrupted any time.

none

certificationNextStage

Open a next stage of campaign based.

Simple

N

N

certificationCampaignRef

Specified certification campaign for opening next stage.

None.

certificationRemediation

Start remediation process for certification campaign.

Simple

N

N

certificationCampaignRef

Specified certification campaign for remediation.

None.

extension

This is a place for customer-provided activities.

Simple

Customer-provided activities can have any configuration items and distribution (multi-threading, clustering) properties.


1. What can be distributed are resource, not individual shadows on the resource.
Was this page helpful?
YES NO
Thanks for your feedback