Get Live Help
Enter the following properties for a scope. Set a filter for the target system whose object are referenced from the connection system. For more information, see What is a Scope.
|SchemaData model of a connected system. The schema describes all the master data from the connected system. see target system schema; see One Identity Manager schema; see connector schema; see extended schema||Display name for the schema to which the scope will be applied.|
|Name||Scope display name. The name must be unique within a synchronization project.|
|Scope hierarchy||List of all schema types for the selected schema. To filter the list, click .
|Is filtered?||All schema types with a filter are marked.
|Condition||Specify the filter condition for the scope. Select an object type in the scope hierarchy for this.
|Hierarchy filterUsed to limit the number of objects to be loaded directly into the target system. It is based on the real objects of the target system. This filter can be used for defining the scope.||Filter created on the bases of existing system objects. This filter limits the number of objects to load in the connected system.
This filter is only available for certain target systems.
Certain target systems support the definition of a scope based on the hierarchy of existing target system objects. The hierarchy filter limits the number of objects to load in the connected system. The hierarchy filter can only be applied to objects and not to their schema properties.
The objects are displayed in their hierarchical structure on the right-hand side of the scope view. The Synchronization EditorOne Identity Manager tool for configuring target system synchronization. establishes a connection to the target system to do this. using the variable set selected in the 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. Editor's toolbar.
To create a hierarchy filter
All unmarked objects remain outside the scope.
If you enable the hierarchy's root note, new objects within the hierarchy are included by the scope. If the root node is disabled, only the marked objects are within the scope. New object are not synchronized.
|NOTE: Create an additional object filter to include schema properties as criteria in the scope definition.|
A fully defined hierarchy filter can be transformed into a variable. Thus the filter can be redefined in a specialized variable set and used for other synchronization configurations.
To convert a variable into a hierarchy filter
The hierarchy filter is saved as variable. To change the filter, edit the variable.
You can use variables to create generally applicable synchronization configurations which contain the necessary information about the synchronization objects when synchronization starts. For example, you can use variables in the target system connection to synchronize different Active Directory domains with the same synchronization project.
Variables can be used in the following Synchronization EditorOne Identity Manager tool for configuring target system synchronization. definitions.
|System connections||in parameters|
|Scopes||in the filter|
|SchemaData model of a connected system. The schema describes all the master data from the connected system. see target system schema; see One Identity Manager schema; see connector schema; see extended schema classes||in the filter|
|Schema properties||as defined value|
|Property mapping rules||in the condition|
|Processing methods||in the condition|
|Base objects||in the definition|
Variable sets are added for different instances of the variables. Each synchronization project has a default variable set, which has all the variables with a default value. The start up configuration contains a link to the variable set in use. If no variable set is given, the default variable set is used.
A default variable set is defined if the synchronization project was creating using a default project template. You can add variables to this variable set. If the synchronization project was created without a project template, no variable sets are set up.
Create a specialized variable set to use variables with other values. You can change the values of the variables individually. Assign the specialized variable set to a start up configuration in order to use it.
The default variable set contains all variables that are required in the synchronization project. New variables are created in the default variable set. They are automatically added to all specialized variable sets, with their default values. A variable's value can also be found with a script, for example, for reading a system user's password from an external password management system.
|Add a variable/variable set.|
|Delete variable/variable set.|
|Rename variable set.|
|Convert variable to script.|
|Convert script variable to a plain variable.|
|Display variable usage.|
|Default value for restoring the selected variable.|
To create a variable in the default variable set
The default variable set is displayed with all available variables in the upper part of the document view.
Click in the upper view's toolbar.
To create variables from connection parameters
For more information, see How to Edit System Connection Properties.
This button is not available if the parameter has already been converted into a variable. The variable name is displayed instead.