Adding Schema Extensions

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

1. Changes to the schema are displayed on the page System modifications. This displays all the Data Definition Language (DDL) statements that are used by the extensions.
   1. If you want to save statements in a file
      • Set the option Attach statements to existing file to add the statements to an existing file.
      • Select Save to file in the repository path and enter a file name. The statements are saved as an SQL file.
      • To create the file, click Save.
      • Click Next.
      • Confirm the security prompt with Yes.
   2. If you do not want to save the extensions in a fileConfirm the security prompt with Yes
      • Click Next.
      • .

   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.

2. Start compilation on the Compiling page. This make take some time. Click Next after compilation is complete.
3. New calculation tasks are queued in the DBQueue Processor due to the schema extension. The current DBQueue Processor calculation tasks are displayed on the System queue page. After the calculation tasks have finished processing, click Next.
4. On the last page, you return to the beginning of the wizard to enter more extensions or click Finished to end the program.

After completing the schema extensions, you can access them with One Identity Manager tools and make further changes.

Adding in Custom Extensions to the User Interface

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.

1. Edit the table, column and table relation properties.

   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.

2. Grant editing permissions

   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.

3. Creating object definitions

   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.

4. Editing navigation

   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.

5. Creating the forms for the user interface

   Create or extend forms for displaying and editing in the Manager.

   • To edit custom table, create an interface form with the form definition "VI_Generic_MasterData" using Form Editor in the Designer.
   • Default forms can be used to customize column extensions on default tables under certain conditions.
   • Create the corresponding overview form with the Overview Form Editor in the Designer.
   • One Identity Manager provides a set of form templates and definitions in the default installation. These can be used for easily creating your own forms.

   For more information, see Editing Interface Forms, Forms for Custom Extensions and Working with Overview Forms.

6. Creating method definitions

   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.

7. Creating analyzes

   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.

8. Localizing text

   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.

Transporting One Identity Manager Schema Customizations

Transporting One Identity Manager Schema Customizations

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.

Detailed information about this topic

• Basics for Transport of One Identity Manager Schema Modifications
• Creating a Transport Package with the Database Transporter
• Displaying Contents of a Transport Package
• Importing a Transport Package with the Database Transporter
• Displaying Transport History

Related Topics

• Files for Software Update
• One Identity Manager Installation Guide

Basics for Transport of One Identity Manager Schema Modifications

Basics for Transport of One Identity Manager Schema Modifications

Prerequisite for transporting modifications between One Identity Manager databases:

• Source and destination database have the same underlying database system.

Different methods are implemented for transporting modifications.

• Transport of single objects is done through the object layer. This means, permissions, templates and Customizer are taken into account when a transport package is imported.

  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.

• The transport of the entire system configuration is done through a transfer buffer. All relevant tables are checked when creating the transport package. The condition applied to the table, defines which objects are transported. The primary key is used to establish whether the transport entry has a GUID module and whether it is transferred to the source database transfer buffer. The transfer buffer is read and transport package is created. When importing into the target database, the contents of the transport package is transferred to the target database's transfer buffer. The information is then transferred to the target tables.

  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:

• Paste

  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.

• Refresh

  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.

• Delete

  Objects that are no longer needed are deleted. This operation is always executed if the entire system configuration is transported.

Related Topics

• Creating a Transport Package with the Database Transporter
• Importing a Transport Package with the Database Transporter