In this step, you copy all the schema extensions, such as new tables, columns or indexes into the database.
To add schema extensions in the Schema Extension
The schema extensions are added to the database and the necessary extensions are made to the One Identity Manager system data model. This make take some time.
After completing the schema extensions, you can access them with One Identity Manager tools and make further changes.
After you have extended the schema with a custom table or column, other steps are required to display the extensions in the Manager user interface.
Properties include, for example, display names, descriptions, display patterns for tables and columns as well as templates, formatting, mandatory field definitions. You already specify some of the properties when you extend the schema with the program "Schema Extension". Use the Designer Schema Editor to make more changes to the tables and columns.
For more information, see Mapping Table Definitions and Mapping Column Definitions.
You already grant permissions for permissions groups when you extend the schema with the program Schema Extension. You can carry on editing permissions in the Designer Permissions Editor and also create permissions groups with the User & Permissions Group Editor.
For more information, see Granting One Identity Manager Schema Permissions and Editing Permissions Groups and System Users.
The data in the user interface is represented by objects. A generally valid object definition without limited selection criteria has already been created with the program "Schema Extension". You can create other object definition constraints in addition. You create object definitions in the Designer.
For more information, see Object definitions for the User Interface.
Extend the navigation in order to display data in the Manager. Use Designer's User Interface Editor to create menu items for navigation and result lists.
For more information, see User Interface Navigation.
Create or extend forms for displaying and editing in the Manager.
For more information, see Editing Interface Forms, Forms for Custom Extensions and Working with Overview Forms.
If you want to provide specific tasks in the Manager, you can create method definitions in the Designer.
For more information, see Task Definitions for the User Interface.
Create statistic definitions and reports to analyze data and add these into the user interface.
For more information, see Statistics in the One Identity Manager and Reports in the One Identity Manager.
Use the Language Editor in the Designer to translate text for multilingual captions in the Manager, for example, column names, comments, menu items, form names.
For more information, see Language Dependent Data Representation.
Automatic version control is integrated into the One Identity Manager, ensuring that One Identity Manager components are always consistent with each other and with the database. If program extensions that change the structure are implemented, for example, table extensions, the database needs to be updated.
You need to update the database if hotfixes and service packs for your installed version of the One Identity Manager are available or complete version updates. In addition, you are repeatedly required to transfer custom changes from a development database into the live database.
The One Identity Manager schema is customized by loading so-called ‘transport packages’. One Identity Manager recognizes the following types of transport packages that can be copied to the database depending on requirements.
Transport Package Type | Description | Tool Used | ||
---|---|---|---|---|
Migration package |
Migration packages are provided by for the initial database schema installation, for service pack and complete version updates. A migration package contains all the necessary tables, data types, database procedures and the default One Identity Manager configuration. |
Configuration Wizard | ||
Hotfix package |
Hotfix packages are provided to load individual corrections to the default configuration such as templates, scripts, processes or files into the database.
|
Database Transporter Software Loader | ||
Custom configuration package |
A custom configuration package is used to exchange customer specific changes between the development, test and productive system database. This transport package is created by the customer and loaded into the database. |
Database Transporter |
|
NOTE: If more custom configuration adjustments are made to a One Identity Manager database, then create a custom configuration package and import this transport package in the target database with the Database Transporter. There is no support for merging a hotfix package with a custom configuration package into one transport package. |
Prerequisite for transporting modifications between One Identity Manager databases:
Different methods are implemented for transporting modifications.
This method is implemented, for example, if you create and import custom configuration packages with the program "Database Transporter" which contain modifications to system users, modifications from a specific date or single objects.
This method is used if custom configuration packages, which contain the entire system configuration, are created and imported with the program "Database Transporter". This method is also used when installing and updating the One Identity Manager schema with the Configuration Wizard.
When a transport package is imported into a One Identity Manager database the following operations are carried out:
No object was found in the destination database using the primary key or alternative key, therefore a new object is created with this key value.
If an object is found in the destination database using the primary key or an alternative key, this object is updated. The update is done using the configuration buffer.
If transporting modifies a default configuration, the default configuration is moved into the configuration buffer. You can retrieve changes from the configuration buffer and restore the default configuration in this way.
If, during a One Identity Manager version upgrade, the default configuration is changed by a service pack, a complete version upgrade or by loading a hotfix package, a check is made to see if it has already been customized. In this case, the modified default configuration is copied to the configuration buffer. This ensures that customizations do not go missing.
Objects that are no longer needed are deleted. This operation is always executed if the entire system configuration is transported.
© 2021 One Identity LLC. ALL RIGHTS RESERVED. Feedback Terms of Use Privacy