How to Delete Synchronization Steps

How to Delete Synchronization Steps

To delete a synchronization step

1. Select the category Workflows.
2. Select a workflow in the navigation view.
3. Click in the synchronization step in the workflow view to open the synchronization step dialog box.
4. Click .
5. Confirm the security prompt with Yes.

General Properties of a Synchronization Step

General Properties of a Synchronization Step

Enter the following general properties for a synchronization step.

Table 49: General Properties of a Synchronization Step

Property	Meaning
Name	An arbitrary name for the synchronization step. The name must be unique within a synchronization workflow.
MappingList of object matching rules and property mapping rules which map the schema properties of two connected systems to one another.	Select the mapping to be processed by the synchronization step.
Direction of SynchronizationThe process of comparing data between One Identity Manager and a target system. Objects and their properties are compared by fixed rules. Synchronization results in the identical data situation in the target system and One Identity Manager database.	Select the direction in which synchronization should take place. Use workflow template The direction of synchronization is specified with the workflow. For more information, see Properties of a Workflow. Target system One Identity Manager is the master system for synchronization. One Identity Manager The target system is the master system for synchronization.
RevisionHighest value for change data for all system objects to be synchronized when synchronization is run. This value is saved in the table "DPRRevisionStore", column "value". filtering	The revision filtering can be used to limit synchronization to just the objects that have been modified since the last synchronization. For more information, see How does Revision Filtering Work. Use workflow template The desired behavior is specified with the workflow. Use revision filter Only modified object are synchronized. Do not use revision filter All objects are synchronized.
Error Handling	Specify whether synchronization should be continued if an error occurs during processing of synchronization objects (adding, deleting, updating and reloading objects). Object processing is continued using the next object; the error is logged. To optimize error localization, you can abort synchronization if an error occurs during the processing of synchronization objects. In this case, no further synchronization objects are processed. NOTE: This property does not affect configuration, network or general synchronization errors (for example, if it is not possible to resolve a reference). The effectiveness of this property depends on the actual error, error position, the target system and the implementation of the target system connectors. Use workflow template The desired behavior is specified with the workflow. Continue on error Processing is continued with the next object. Errors are logged. This option should be used for productive systems. Break on error The entire synchronization is aborted. This option should only be used to find errors, for example in going live processes.
Data import	Set this option if the synchronization step synchronizes a secondary system and changes are immediately provisioned in the primary system. Do not set this option if the synchronization step synchronizes a primary system. For more information, see Synchronizing User Data with Different Systems.
Description	Spare text box for additional explanation.
Disabled	If this option is set, the synchronization step is not synchronized.

Specifying Processing Methods

Specifying Processing Methods

Specify how changes to system objects should be handled on the Processing tab. You can select the following default methods. Furthermore, the schema types of the various target systems provide additional processing methods if required.

The processing methods are defined for different sets of synchronization objects.

• Objects only found in the target system and missing in One Identity Manager.
• Objects only found in One Identity Manager and missing in the target system.
• Objects with modified properties

  This means there are object pairs whose objects differ.

• Objects without modifications:

  This means there are object pairs whose objects are identical.

Table 50: Default Processing Methods in a SynchronizationThe process of comparing data between One Identity Manager and a target system. Objects and their properties are compared by fixed rules. Synchronization results in the identical data situation in the target system and One Identity Manager database. Step

Processing MethodMethod used to process objects within a synchronization step. Example: Add object (insert), update object (update), delete object (delete). Processing methods and their mandatory parameters are define with the schema type. (technical name)	Meaning
Insert	Objects that only exist in one of the connected system are added to the other system.
Delete	Objects that only exist in one of the connected system are deleted from the system. The following applies to synchronization in One Identity Manager. The object is immediately deleted if it came from a primary system. Deferred deletion is not taken into account. Deferred deletion is taken into account if the object comes from a secondary system. For more information, see Synchronizing User Data with Different Systems.For more information about deferred deletion, see the One Identity Manager Configuration Guide.
Update	Objects whose properties have change are updated.
MarkAsOutstanding	Objects that only exist in the One Identity Manager are marked as outstanding during synchronizing in the direction of One Identity Manager. These objects can be reworked after synchronization is complete. Objects marked as outstanding are ignored by subsequent synchronization.
No processing	No processing methods are executed.

Table 51: Meaning of the Icons

Icon	Meaning
	Adds an extra processing method for the object set. If you allow several processing methods for one object set, add conditions for executing these methods.
	Create a condition for executing the method. All objects are processed the same way if you do not create a condition.
	Moves the processing method forwards in the order of execution.
	Moves the processing method backwards in the order of execution.
	Deletes the processing method.

Detailed information about this topic

• Editing Subsets
• Specifying Additional Processing Methods
• Deleting Objects in One Identity Manager

Specifying Additional Processing Methods

Some target systems provide extra processing methods in addition to the default ones. One Identity Manager can execute different processing methods in sequence for the same set of objects.

To define different processing methods for a set of objects

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. Use and to specify the order in which to execute the processing methods.

Example

You can enter external user IDs for SAP user accounts in One Identity Manager. User accounts that only exist in One Identity Manager are added if SAP user accounts from One Identity Manager are synchronized with SAP R/3. The associated external user ID's are also transferred into the target system.

Object Set	Processing MethodMethod used to process objects within a synchronization step. Example: Add object (insert), update object (update), delete object (delete). Processing methods and their mandatory parameters are define with the schema type.
Objects only found in One Identity Manager are:	Insert AddExtID

Related Topics

• Specifying Processing Methods