Page tree

Versions Compared

Key

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

...

Code Block
languagehtml/xml
<capabilities xmlns:cap="http://midpoint.evolveum.com/xml/ns/public/resource/capabilities-3">
  <configured>
    <cap:create>
      <cap:enabled>false</cap:enabled>
    </cap:create>
    <cap:update>
      <cap:enabled>true</cap:enabled>
    </cap:update>
    <cap:delete>
      <cap:enabled>false</cap:enabled>
    </cap:delete>
  </configured>
</capabilities>


Anchor
preciseTokenValue
preciseTokenValue
Another example: Precise token value in Live synchronization


Info
titleMidPoint 4.0 and later

As another example let's consider preciseTokenValue property in cap:liveSync  capability:

Code Block
<capabilities xmlns:cap="http://midpoint.evolveum.com/xml/ns/public/resource/capabilities-3">
    <configured>
        <cap:liveSync>
            <cap:preciseTokenValue>true</cap:preciseTokenValue>
        </cap:liveSync>
    </configured>
</capabilities>

This tells midPoint that the resource provides live synchronization capability with the additional assurance that token values that are attached to each change emitted by the resource are precise enough to guarantee correct restart of live synchronization process after processing of each given change. If this information is not present, midPoint restarts live synchronization (in case of suspension or failure) at the same place where it was started, instead where it was stopped.

Some resources are known to provide precise token values, others are known of not doing so (e.g. for performance reasons). Others - e.g. those served by ScriptedSQL connector - depend on particular configuration of the connector.