You can use variables to create generally applicable synchronizationThe processSequence of process steps for mappingList of object matching rules and property mapping rules which map the schema properties of two connected systems to one another. an operational workflow. The process steps are connected to one another by predecessor/successor relationships. This functionality allows flexibility when linking up actions and sequences on object events. 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. configurations that 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 projectA collection of all data required for synchronizing and provisioning a target system. Connection data, schema classes and properties, mappings, and synchronization workflows all belongs to this..
Variables can be used in the following Synchronization EditorOne Identity Manager tool for configuring target system synchronizationPost processing of objects that were marked as outstanding by synchronization.. definitions.
System connections | in parameters |
Scopes | in the filter |
SchemaData model of a connected systemSystem the objects and their properties are transferred to during synchronization. The connected system is defined by the synchronization direction. Example of synchronization direction "Target system" (One Identity Manager -> Active Directory): Here Active Directory is the connected system and One Identity Manager is the primary system of synchronization.. The schema describes all the main 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.
NOTE: If synchronization projects are updated, connection parameters from the default variable set are always used. Ensure that the variables in the default variable set contain the correct values.
A default variable set is defined if the synchronization project was creating using a default project templateTemplateRule for mapping object properties. Templates can be applied to an object and also have a cross-object effect. used by the project wizard to create a preconfigured synchronization project.. You can add variables to this variable set. If the synchronization project was created without a project template, no variable sets are set up.
The default variable set contains all variables that are required in the synchronization project. New variables are created in the default variable set.
Create a specialized variable set to use variables with other values. You can change the values of the variables individually. Specialized variable sets only contain variables with modified values. Assign the specialized variable set to a start up configuration in order to use it.
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.
Icon | Meaning |
---|---|
|
Add a variable/variable set. |
|
Delete variable/variable set. |
|
Rename variable set. |
|
Convert variable to script. |
|
Convert script variableVariable whose value is determined by a script. to a plain variable. |
|
Display variable usage. |
|
Default value for restoring the selected variable. |