During the startup process the Designer fills an internal database. SQLite is used for the database system. This internal database contains the schema and the files from the system components of the connected One Identity Manager database.
Depending on the program’s configuration, the internal database is either loaded into main memory or copied to the hard drive of the workstation. To avoid data inconsistencies, only one instance of the program should be started per database. If the database from the first instance is copied to hard disk then the databases for all other instances are loaded into main memory.
All changes to objects in the program are made in the internal database. Permissions, formatting rules and side-effects of the Customizer are taken into consideration. Changes made by the user are recorded in a change log. If the internal database is stored on the hard drive, all additional changes are also logged to this database. This means that you can restore to the last working state after connecting to the database if the program crashes.
When the data is transferred all recorded changes are made to the One Identity Manager database. This is done at object level so that, for example, processes are generated and formatting rules are observed. The principle "last writer wins" applies here as opposed to the previous object processing. That means that changes have been made by a user to object properties in the mean time are overwritten.
Depending on the program settings, the internal database is deleted from the hard drive when the program has finished. This means that all the data has to be loaded from the One Identity Manager database when the program is restarted. If the internal database is not deleted when the program finishes, the next program start up can be accelerated because only changes from the One Identity Manager that is connected have to be loaded.
You can access One Identity Manager documentation in the Designer by selecting the Help > Search in local help menu item.
You can open the general help for Designer from the Help menu or by selecting F1. The Help menu offers specific help information for each editor.
In addition, a Designer help is available for individual properties of the currently displayed object. Clicking on the help icon 
changes the cursor into the help icon. Then when you click on a column description, tips for using the column are displayed in the form of tooltips.
The following views are displayed in the Designer: There are several editors used for editing data. Their functionality and methods are tailored to the different configuration tasks.
Table 41: Designer views
|
Navigation view |
The navigation structure of the user interface is hierarchical and allows users to drill down to the selection of an object definition. The top level of the hierarchy is used to classify One Identity Manager data into specified categories. |
|
Document view |
Overview forms and selected editors are displayed in the document view. When an object is selected in the navigation view, the corresponding overview form is displayed.
TIP: If quick edit is enabled, you skip the overview and go straight to the first editor available for the object. |
|
Task view |
When you select an object in the navigation view, the available editors are displayed together with the tasks that can be run. The relevant editor is opened in the document view when the object is selected. |
|
Change log |
Changes made by the user are recorded in the change log. |
|
Error log |
The program’s error log displays all warnings and error messages that have occurred since the program started up. When the Designer restarts, the error log is reinstalled. For more information about the error log, see the One Identity Manager Process Monitoring and Troubleshooting Guide. |
|
Change label |
In this view, change labels are created and edited. For more information about working with change labels, see the One Identity Manager Operational Guide. |
Related topics
