To delete the scope or scope reference.
- Edit the system connection properties.
For more information, see How to edit system connection properties.
- Select the view.
- Click Delete.
Enter the following properties for a scope. Set a filter for the target system whose object are referenced from the . For more information, see What is a scope?.
Table 56: Scope properties
| |
Display name for the schema to which the scope will be applied. |
| Name |
Scope display name. The name must be unique within a . |
| Scope hierarchy |
List of all schema types for the selected schema. To filter the list, click  .
| Show all object types |
All object types of the schema are displayed. |
| Only show hierarchically structured object types |
Only the object types of the schema that form a hierarchical structure are displayed. | |
| Is filtered? |
All schema types with a filter are marked.
 |
A filter is defined and effective. |
 |
A filter is effective. | |
| Condition |
Specify the filter condition for the scope. Select an object type in the scope hierarchy for this.
|
|
that immediately affects the connection system.
Enter the filter in system specific notation, for example, as Where clause for a database system or as LDAP filter for an LDAP system.
If tested against a fixed value that contains at least two dollar characters, the dollar characters must be masked.
This filter is only effective when loading the system objects. |
|
|
Filter that affects loaded objects.
|
Condition |
Formulate a query for loaded objects. Use the wizard for entering filter. |
|
Script |
You can also store a script which determines system objects. The script must be written in the script language specified in the synchronization project. | | |
| |
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 individual target systems.
For more information, see Creating hierarchy filters. |
Related topics
Certain target systems support the definition of a scope based on the hierarchy of existing target system objects. The limits the number of objects to load in the . 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 establishes a connection to the target system to do this. using the variable set selected in the Synchronization Editor's toolbar.
To create a hierarchy filter
-
Mark all the objects in this hierarchy which are included in the scope.
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 objects are not synchronized.
To select all objects that match certain criteria, use the wizard.
To create a hierarchy filter using the wizard
-
In the hierarchy filter's toolbar, click 
.
-
Enter a search pattern.
Select whether you want to filter objects by wildcard or regular expression.
-
To apply the search criteria, click Assign.
You can apply different search patterns one after another.
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
-
Click Convert into a variable.
- Confirm the security prompt with Yes.
The hierarchy filter is saved as variable. To change the filter, edit the variable.
Related topics
You can use variables to create generally applicable 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 .
Variables can be used in the following definitions.
| System connections |
in parameters |
| Scopes |
in the filter |
| 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 . 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.
Table 57: Meaning of icons in the variable set tool bar
|
|
Add a variable/variable set. |
|
|
Delete variable/variable set. |
|
|
Rename variable set. |
|
|
Convert variable to script. |
|
|
Convert to a plain variable. |
|
|
Display variable usage. |
|
|
Default value for restoring the selected variable. |
Section of a connected system