Configure Run MA Delta Full Sync Schedule

The Run MA Delta Full Sync schedule step is a special case step for working with a MIM sync engine. It does not actually run a management agent per se. Instead it queries for objects in a pending state and performs a  full sync preview commit on each object.

The delta full sync step can be used in scenarios where extension code requires a full sync to achieve the desired effect, but SLA requirements don't allow sufficient time to do a full sync of the entire management agent.

The delta full sync has a number of configuration options for selecting individual sub-ranges of objects in the MA.

The delta full sync step MUST be run locally on the MIM Sync server as it accesses both the MIM database and the sync engine web service. For this step to function the sync provider must have the CSExport path correctly configured.

Settings

Environment – Sync environment to execute against

MA – Management agent to preview commit

Object Type – Optional: restricts scope to synchronize objects of a specific type

Disconnectors – Optionally include objects that are currently disconnectors. This is false by default since such objects would typically be covered by a regular delta sync.

Sync Users File – Optional: In many cases rather than preview committing all users in a pending state it is desirable to process only a specific list of users. The Sync Users File may be provided and pointed at the fully qualified path of a text file containing CS Object IDs in the target MA. The sync file should have one identifier per line.

Note: The MIM Test sync provider offers similar functionality, and is also able to identify objects by RDN. MIM Test is also able to perform Join, Disconnect, and Project operations.

Producing a sync users file is generally done using an SQL query against the FIM sync database. The following example will list all connected users in the AD LDS MA from the Chicago location. The results can then be copied into a text file. 

select c.object_id, c.rdn from mms_connectorspace c
JOIN mms_csmv_link cm ON c.object_id=cm.cs_object_id
JOIN mms_metaverse m ON cm.mv_object_id=m.object_id
JOIN mms_management_agent ma ON c.ma_id=ma.ma_id
WHERE 
m.LocationDescription='Chicago Office' AND
ma.ma_name='LDS'