|Microsoft Identity Integration Server 2003 Developer Reference|
The MIIS_ManagementAgent class has a several methods that you can use to ensure that you are altering the metaverse and the connector space according to your business rules. We recommend that you use the results of these methods to check the effects of importing and exporting objects prior to applying the changes to the metaverse or connected data source.
For example, you can set a limit of the number of objects to be deleted during each management agent run. This limit can either be expressed as a specified number of objects, such as delete up to 50 objects, or as a ratio of deleted objects to the total number of connector space objects, such as delete up to 20% of the connector space objects.
You only perform a synchronization run profile step if the suggested methods return a number less than the specified limits. If the number returned exceeds the specified limit, then you do not perform a synchronization run profile step.
When importing objects into the metaverse, you should stage the imports by running a management agent with a Full Import (Stage Only) or Delta Import (Stage Only) run profile step before a synchronization run profile. By staging the imports you can then check the results of the following method do not exceed your specified limits:
Important These methods return zero if you do not stage your imports prior to running these methods. You must stage the imports in order for these methods to return useful values.For an example in Visual Basic Scripting Edition (VBScript) of using these methods, see Example: Preventing Metaverse Damage.
For objects that will be exported to other connected directories, check the results of the following methods before running a management agent with a full export run profile step.
Example: Preventing Metaverse Damage, Example: Preventing Connected Data Source Damage