Chat now with support
Chat with Support

Identity Manager 8.0 - Target System Synchronization Reference Guide

Target Synchronization with the Synchronization Editor Basics of Target System Synchronization Setting up Synchronization
Starting the Synchronization Editor Creating a Synchronization Project How to Configure Synchronization
Setting Up Mappings Setting up Synchronization Workflows Connecting Systems Editing the Scope Using Variables and Variable Sets Setting up Start up Configurations Setting up Base Objects
Overview of schema Classes Customizing Synchronization Configuration Checking Synchronization Configuration Consistency Activating the Synchronization Project
Running Synchronization Synchronization Analysis Setting up Synchronization with Default Connectors Updating Existing Synchronization Projects Additional Information for Experts Error Handling Appendix: Example of a Configuration File

Editing Subsets

Editing Subsets

Processing methods can be limited to a set of the objects. To do this, specify the condition under which the processing method is to be executed. You can specify different processing methods for different sets of objects. These are executed in the given order.

To define processing for different sets

  1. Select a processing method from the menu for synchronizing an object set.
  2. Click to specify another processing method for this object set. Select a processing method from the menu.
  3. Create the condition defining the execution point the processing method. Click next to the method.

    Enter the condition. You can use comparisons, logical operators and variables. You can write queries with a wizard or enter them directly.

    • Use the following expression in the condition to access the schema properties of the system in which the processing method is to execute: Base.<schema property>
    • Use the following expression in the condition to access schema properties of the other system: Other.<schema property>
  4. Use and to specify the order in which to execute the processing methods.
Example

All user accounts that only exist in One Identity Manager are processed as follows when synchronizing Active Directory user accounts from Active Directory in the direction of One Identity Manager:

 

Object Set Processing MethodClosed Condition
1 All user accounts, connected to an employee, are marked for deletion. MarkForDeletion Base.UID_Person <> ''
All user accounts, not connected with an employee, are deleted. Delete Base.UID_Person = ''
2 All user accounts, in container A, are deleted. Delete Base.UID_ADSContainer = '4b53ff19-6ae4-4a87-86bd-eca3ddf5ebf2'
All user accounts, not belonging to container A, are marked for deletion. MarkForDeletion Base.UID_ADSContainer <> '4b53ff19-6ae4-4a87-86bd-eca3ddf5ebf2'
       
Related Topics

Specifying Quotas

Specifying Quotas

Errors in the synchronization configuration can cause system objects to be processed incorrectly. Errors in the data through incorrect configuration can be reduced. Often, it is known how many system objects have been modified, added or deleted in a connected system. If this number is exceeded when a processing method is executed, a warning appears and synchronization is aborted. The synchronization step and mapping configurations can be checked and corrected before repeating synchronization.

A quotaClosed can be defined for each processing method in each synchronization step to specify the part of the system objects to process. A quota provides the number of object to process relative to the total number of all objects in the schema class to be synchronized. When a synchronization step is executed, One Identity Manager calculates the number of objects to process for each processing method with a quota. If this number exceeds the quota, the synchronization step is aborted.

Quotas can only be defined for processing methods which modify data (for example, Insert, Update, Delete).

Note: One Identity Manager takes total number objects to be synchronized into account when it calculates the number of objects to process. Conditions defined for processing methods are not taken into account!

Enter an higher quota for processing methods which limit the number of objects to synchronize with a condition.

Table 52: Quotas for a SynchronizationClosed Step
Property Meaning
No quota If this is set, quotas are not included.
Use these settings

Specify which processing methods include a quota. Enter the quota in percent.

One Identity Manager specifies quotas for synchronization in the target system in workflows created with the workflow wizard, by default.. These quotas can be changed later.

Processing MethodClosed quota
Update 75 %
Delete 10 %

Rule Filter

Rule Filter

You can specify which Property mapping rules must be applied to each synchronization step. For example, dependencies between schema class objects can be resolved this way.

Included rules: Select the property mapping rule to be applied during synchronization.
Excluded rules: Select the property mapping rules which should not be applied during synchronization.

Note: Unmarked rules are included automatically.
Detailed information about this topic

Extended Synchronization Step Properties

Extended Synchronization Step Properties

You can optimize memory usage for processing synchronization step data on the Extended tab.

Table 53: Extended SynchronizationClosed Step Properties
Property Description
Performance/memory factorClosed This controls the behavior of memory and performance in the synchronization step. If more memory is available, you can change the performance/memory factor in favor of performance. Reduce the performance/memory factor if there are memory problems.

The performance/memory factor specifies the percentage with which the reload threshold, partition size and bulk level are applied to an object type.

Use the slider to set the performance/memory factor.

  • Move the slider to the right to increase performance. This requires more memory.
  • Move the slider to the left to reduce the memory requirement. This decreases performance.

Reload threshold

Specifies the maximum number of properties that can be loaded by synchronization to prevent partitioned reloading. You can increase this value to accelerate synchronization of target systems with small mappings. However, more memory is required.

The default value for all data to be processed is fixed in the start up configuration. It can be specified separately for every synchronization step.

To specify the threshold for a synchronization step

  1. Disable Use start up configuration settings.
  2. Change the preset reload threshold.

TIP: You can adjust the memory requirements for all the data to be processed in the start up configuration. You can set the reload threshold, partition size and bulk level here. These setting are only possible in expert mode. For more information, see Extended Properties for Start Up Configuration.

Detailed information about this topic
Related Documents