Chat now with support
Chat with Support

Identity Manager 8.0.2 - Configuration Guide

One Identity Manager Software Architecture Working with the Designer Customizing the One Identity Manager Default Configuration Checking Data Consistency Compiling a One Identity Manager Database Working with Change Labels Basic System Configuration Data
One Identity Manager Authentication Module Database Connection Data Configuration Parameters for System Configuration Setting up the Mail Notification System Enabling More Languages for Displaying and Maintaining Data Displaying Country Information Setting Up and Configuring Schedules Password Policies in One Identity Manager Reloading Changes Dynamically TimeTrace Databases Machine Roles and Server Functions Files for Software Update Operating Systems in Use System Configuration Reports Using Predefined Database Queries Managing Custom Database Objects within a Database
The One Identity Manager Data Model Granting One Identity Manager Schema Permissions Working with the User Interface
Object definitions for the User Interface User Interface Navigation Forms for the User Interface Statistics in the One Identity Manager Extending the Launchpad Task Definitions for the User Interface Applications for Configuring the User Interface Icons and Images for Configuring the User Interface Language Dependent Data Representation
Process Orchestration in One Identity Manager
Declaring the Job Server One Identity Manager Service Configuration Handling Processes in the One Identity Manager
Tracking Changes with Process Monitoring Conditional Compilation using Preprocessor Conditions Scripts in One Identity Manager Maintaining Mail Templates Reports in the One Identity Manager Custom schema extensions Transporting One Identity Manager Schema Customizations Importing Data Web Service Integration SOAP Web Service One Identity Manager as SPML Provisioning Service Provider Searching for Errors in the One Identity Manager Processing DBQueue Tasks Appendix: One Identity Manager Configuration Files

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. Granting access 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

    Data is displayed in the user interface using 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 Manager to translate text for multilingual captions in the Designer, for example, column names, comments, menu items, form names.

    For more information, see Language Dependent Data Representation.

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.

Table 316: Transport Package
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.

NOTE: If a hotfix only contains modified files, load these files into the database using the "Software Loader" program.

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.

Detailed information about this topic
Related Topics

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:

  • Insert

    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.

  • Update

    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

Create a custom configuration package, which you import into the target database, in order to exchange customizations between the development database, test database and the production database.

You can specify restricting export criterion for creating custom configuration packages. System user modifications, modifications as from a defined date, or individual objects can be exported. A limited custom configuration package is recommended for transporting individual changes from a development database to a test database. However, you should create a transport of the entire system configuration package to transfer changes from the test database to the productive database.

NOTE: The current user must be entitled to use the program function "Allows transport packages to be imported into the database." in order to import a transport package with the Database Transporter. (Transport_Import).

To create a transport package

  1. Start the Launchpad and select Transport custom modifications. This starts the program "Database Transporter".
  2. Select Create a transport file on the start page.
  3. Enter the connection credentials for the One Identity Manager database on the Select the database connection page.
  4. Enter the information about the transport file on the Define file name page.
    1. Enter the name of the transport file and change the output directory as required.
    2. To create an export log file, set the option Create a log file for data export.

      The log file is saved in the output directory of the transport file.

  5. Enter a description of the transport data on the Show and define transport parameters page.
  6. Select the export criteria on the Define transport data page.

    NOTE: You can combine several export criteria.

    Table 317: Export Criteria
    Export Criteria Description
    Run SQL statements before data import You can integrate SQL statements into the custom configuration package, which are executed before the data is imported.
    Transport of favorite objects All modified processes, scripts, report and mail templates from a specific time period are available for preselection.
    Transport by change label Transport modifications to objects or object properties, which are grouped under a change label.
    Transport by change information Limit transportation data by user, time period and database tables.
    Transporting Schema Extensions Transport custom schema extensions, like tables, columns, database procedures, functions, triggers, views and indexes.
    "Transport selected objects and their dependencies Select single objects and their dependencies for transporting.
    System Configuration Transport Transport the complete system configuration.
    Transports system files Transport single files. These files are distributed with the automatic software update.
    Run SQL statements after data import You can integrate SQL statements into the custom configuration package, which are executed after the data is imported.
  7. Click Next to start exporting.

    The program determines the data to export and displays the progress of the export in the dialog box. The export procedure can take some time.

  8. Click Finish on the last page to end the program.

The export date, the export description, database revision and the name of the export file in the source database transport history are recorded when a transport package is created with the Database Transporter.

Detailed information about this topic
Related Topics
Related Documents