NOTE: schema classes, which are not in use, can be deleted.
To delete a schema class
- Remove the schema class from all in which they are used.
For more information, see Editing mappings.
- Edit the system connection properties.
For more information, see How to edit system connection properties.
- Open the classes view.
- Select the schema class in the schema overview and click
in the toolbar.
If the schema class is still in use, the location is displayed.
- Confirm the security prompt with Yes.
Having used the project wizard to set up a for initial synchronization of a target system, you can use the synchronization project to load target system objects into the One Manager database. These objects can be edited with One Identity Manager tools. You must synchronization configuration in order to compare the database with the target system regularly and to synchronize changes. You can configure a synchronization project such that the necessary information about the direction of synchronization, objects to synchronize, and the property mapping rules to be applied, is made available when synchronization starts.
Edit the target system connection scope and the One Identity Manager database connection to specify which target system and database object are handled by synchronization. To prevent data inconsistencies, define the same scope in both systems. If no scope is defined, all objects will be synchronized.
You can use variables to create generally applicable synchronization configurations that contain the necessary information about the synchronization objects when synchronization starts. Variables can be implemented in base objects, schema classes, or processing method, for example.
Use variables to set up a synchronization project for synchronizing different target systems. For this, connection parameters for logging onto target systems are stored as variables.
Before activating a , check the consistency of the synchronization configuration. The consistency check detects configuration errors which would lead to errors during synchronization. The synchronization project cannot be activated until the configuration error are corrected.
The consistency check amongst others whether:
- All mandatory properties are mapped through property mapping rules.
- Dependencies can be automatically resolved in workflows.
- Different schema classes of a schema type are differentiated from one another by filters.
To check consistency the loaded synchronization project
-
Select the General view on the home page.
-
Click on Verify project.
Runs processing logic which would normally be implemented in the object code, such as mutual exclusion of properties. The Customizer contains special methods and has side effects on the table columns. Several customizers can be defined for one table. schema classes.