Page tree

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

There are cases when refresh task needs to be run explicitly on a selected group of shadows (e.g. migration scenarios). In that case the search filter may be explicitly specified in the refresh task:

Code Block
languagexml
titleRefresh shadows with pending operations on specific resource
<task>                             
    <name>Forced Shadow refresh</name>
    <extension>
		<modelext:objectQuery>
			<q:filter>
				<q:and>
					<q:ref>
						<q:path>resourceRef</q:path>
						<q:value>
							<q:oid>10000000-0000-0000-0000-000000000004</q:oid>
						</q:value>
					</q:ref>
					<q:exists>
						<q:path>pendingOperation</q:path>
					</q:exists>
				</q:and>
			</q:filter>
		</modelext:objectQuery>
	</extension>
    ...
    <handlerUri>http://midpoint.evolveum.com/xml/ns/public/model/shadowRefresh/handler-3</handlerUri>
    <recurrence>single</recurrence>
</task>


Code Block
languagexml
titleRefresh shadows on specific resource (regardless of pending operations)
<task>                             
    <name>Forced Shadow refresh</name>
    <extension>
		<modelext:objectQuery>
			<q:filter>
				<q:ref>
					<q:path>resourceRef</q:path>
					<q:value>
						<q:oid>10000000-0000-0000-0000-000000000004</q:oid>
					</q:value>
				</q:ref>
			</q:filter>
		</modelext:objectQuery>
	</extension>
    ...
    <handlerUri>http://midpoint.evolveum.com/xml/ns/public/model/shadowRefresh/handler-3</handlerUri>
    <recurrence>single</recurrence>
</task>

Whenever you specify query, it overrides the default query (all shadows on all resources with pending operations).

Performance

Refresh task is quite lightweight and efficient. Therefore it can usually be scheduled for quite a frequent execution, usually executing every few minutes.

...