다음을 통해 공유

ILM/FIM Run Profile Definitions

  • 아티클

Compilation of run profile definitions in FIM 2010 as fully discussed in the help file of FIM 2010.

Run profile definitions also valid for MIIS/ILM (unless indicated otherwise).

 

Overview

Steps

Task

Delta Import (Stage Only)

Import of only those objects with content that has changed in the connected data source.

Objects are imported into the connector space only. No synchronization is applied.
Full Import (Stage Only).

Full import of all objects and attributes from the connected data source to the connector space.

Objects are imported to the connector space only, no synchronization is applied.

Delta Import and Delta Synchronization

To run a delta import of only those objects and attributes from the connected data source that have changed and synchronization rules are evaluated and applied to only those objects in the connector space that have changed.

Those objects and attributes in the connected data source that have changed are synchronized with the metaverse or they are disconnected, depending on rules criteria.

Full Import and Delta Synchronization

Import of all objects and attributes from the connected data source and to reevaluate and apply synchronization rules to those objects in the connector space that have changed.

Those objects and attributes in the connected data source that have changed are synchronized with the metaverse or they are disconnected, depending on rules criteria.

Objects in the connector space that no longer exist in the connected data source are marked obsolete, and disconnector rules are applied.

Full Import and Full Synchronization

Import of all objects and attributes from the connected data source and to evaluate and synchronization rules are applied to all objects and attributes in the connector space, regardless of pending state.

Objects and attributes are then synchronized with the metaverse or they are disconnected, depending on rules criteria.

Objects in the connector space that no longer exist in the data source are marked obsolete, and disconnector rules are applied.

Objects pending export are deleted from the connector space, reevaluated, and placed in the connector space again, depending on export rules.

Delta Synchronization

Reevaluate and apply synchronization rules to those objects and attributes that are staged in the connector space and that have changed.

Those objects and attributes are then synchronized with the metaverse or they are disconnected, depending on rules criteria.

Full Synchronization

Evaluate and apply synchronization rules to all objects and attributes in the connector space. Those objects and attributes are then synchronized with the metaverse or they are disconnected, depending on rules criteria.

Export

Run an export of objects and attributes from a connector space to a connected data source or to an export file.

An export is always delta.

Only objects and attributes in the connector space that are different from existing objects and attributes in the connected data source are exported.

On export, FIM does not get confirmation on a partial run, so the next export run sends out the same deltas.

Also, encrypted attributes, such as passwords, are not written to the intermediate file.

 

Thresholds

To specify a maximum number of objects to be processed, under Threshold, select the Specify number of objects to process check box, and then type or select the maximum number of objects that you want the management agent to import during a run.

By default, this option is not selected, which indicates that all objects will be processed.

To specify a maximum number of object deletions, under Threshold, select the Specify number of deletions to process check box, and then type or select the maximum number of deletions that you want the management agent to export during a run. By default, this option is not selected, which indicates that all object deletions will be processed.

The "Specify number of deletions to process" option can help prevent unwanted object deletions and critical loss of objects in the connector space and in your connected data source.

For the step types Delta Import (Stage Only), Full Import (Stage Only), Delta Import and Delta Synchronization, Full Import and Delta Synchronization, and Full Import and Full Synchronization, if the number of connector space object deletions or the number of connector space objects that become obsolete meets or exceeds the threshold number, the management agent run will stop, and an error will be entered in the event log.

For these run step types, objects will be deleted in the connector space until the threshold number is reached.

For the Export step type, the number of pending object deletions in the connector space will be counted before the export to the connected data source. If the number of pending object deletions exceeds the threshold number, the export to the connected data source will not proceed, objects in the connector space that are pending deletion will be retained, and an error will be entered in the event log.

You can specify a threshold number from 0 through 9,999,999. If 0 is specified, and if there are any deletions, obsolete objects, or objects that are pending deletion, the management agent run will stop, and an error will be entered in the event log.

Deletion of placeholders does not count toward the deletion threshold.

This option is not available for an Export step type with the Resume run from existing log file and export to data source.

If you specify a threshold number in Specify number of objects to process and in Specify number of deletions to process, if either threshold number is reached, the management agent run will stop, and an error will be entered in the event log.

Single step vs. multistep

A run profile with a single step of "Delta Import and Delta Synchronization" will not process disconnector objects that already exist in a connector space.

When you configure a run profile with a single step of the type "Delta Import and Delta Synchronization", a condition can occur in which existing disconnector objects from a previous run are not processed. This condition occurs because the existing objects in the connector space that have not changed since the last run are ignored.

For example, objects that have changed in a connected data source are imported to a connector space, rules determine that the object is not joined or projected to a metaverse object, and the object becomes a disconnector object. Subsequent runs with a single run profile step of type "Delta Import and Delta Synchronization" ignore the object because it has not changed, and the disconnector object will remain in the connector space. To prevent a buildup of disconnector objects in the connector space, run a run profile with a single step of the type "Delta Synchronization". The connector objects with pending changes and the normal disconnector objects that already exist in the connector space are then processed (according to rules).

 

Delta vs. Full

When you run a run profile with "Full Synchronization" or "Full Import and Full Synchronization" run profile steps, connector space objects that are pending export are deleted, and then rules for all linked metaverse objects are reevaluated.

Those objects that are configured for export are then staged again into the connector space for export. This can cause inaccurate synchronization statistics.

For example, a run profile might place 50 objects that are pending export into a connector space. These 50 objects appear again as Adds in Synchronization Statistics. If you then run a reevaluate rules step, these same 50 objects appear again as Adds in Synchronization Statistics. You also see this behavior with rules extensions that determine objects that are pending export in a connector space.

 

Resumable Run profile

As of FIM 2010 Update 1 (KB978864) you will see an option to "Resume Run Profile" when selecting a Full Sync operation if a previous run terminated prior to completion.

 

See Also