Chat now with support
Chat with Support

Identity Manager 8.0 - 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 One Identity Manager Scripts 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 One Identity Manager Configuration Files

Assigning Target Tables and Columns

Specify how the data is stored in the One Identity Manager database.

  • Target table

    Select the target table into which to import the data.

  • Target columns and key

    Columns and their values are displayed.

    • Select the target column of the target table. If there is no target column assigned you will see "not assigned" displayed in the column header.
    • Specify which columns are used as key columns. Key columns are labeled with a key icon in front of the column ID.

    TIP: Use the button in the section "Target table" to automatically sort the target columns and keys. Assigns a column if one is found in the target table whose name matches the name in the source column. It is strongly recommended that you check the assignment afterward.

    TIP: Use the assignment wizard to select the target system columns to insert the data into.

Related Topics

Assigning Target Columns with the Assignment Wizard

Assigning Target Columns with the Assignment Wizard

To assign target columns and keys with the wizard

  1. Open the wizard in the section "Target columns and keys" using the arrow button in the column header of any column.
    Table 324: Functions in Assignment Wizard
    Icon Meaning
    < Moves to previous column.
    > Moves to next column.
    Automatic assignment of target column. Assigns a column if one is found in the target table whose name matches the name in the source column. It is strongly recommended that you check the assignment afterward.
    Inserts a column. A column is inserted with a fixed value.
    Deletes a column. Deletes a column with a fixed value.
  2. Enter the following data for each column:

    TIP: Use the option Show caption to swap between the display name and the technical column name.

    TIP: You can see a preview of the values in the section "Data preview".

    Table 325: Target Column and Key Properties
    Property Description

    Use as key column

    Specifies whether the column is used as a key column.

    More than one key columns can be defined. The data records to import into the database are determined based on key columns. Data records should be uniquely identified with these key columns.

    Conversion script

    Use the conversion script to modify source column values to match the permitted value of the target column. This is required, for example, if a list of permitted values is defined for the target columns. Write the conversion script in VB.Net syntax. You access the values with the variable value. Use dollar notation to access the source columns.

    Target columns

    Select the target columns to be imported into the data. All columns from the target table are displayed with their data type. Following applies:

    • Compulsory data is labeled with a blue triangle in front of the data type.
    • Columns without sufficient permissions are displayed in gray.
    • Columns, deactivated by preprocessor condition, are not shown.

    TIP: If a column is found in the target table whose name matches the name in the source column, the button suggests a another column. You should always verify this suggestion!

  3. After completing your assignments, close the wizard by click on a point outside the wizard.

Inserting Columns with Fixed Values

You can also add additional columns with fixed values to the import data and import it to a defined column.

To insert columns with fixed values

  1. Start the assignment wizard.
  2. Add a new column using the button in the assignment wizard.
  3. Enter the value you want in Fixed value.

    - OR -

    Enter a conversion script if the value should be taken from the source column.

  4. Assign the target column.
Related Topics

Specifying the Hierarchy

If an import contains inter-dependent data, you must ensure that the reference targets are handled before the reference sources.

For example, child departments (Department.UID_Department) are imported after parent departments (Department.UID_ParentDepartment).

NOTE: Sorting data in a hierarchical structure can take up a lot of memory. Therefore, only use this procedure for imports with small amounts of data.

To sort data hierarchically

  1. Set the option Sort by hierarchy.
  2. Select the Key columns in which to map the data (for example, Department.UID_Department) and Parent key column (for example, Department.UID_ParentDepartment)

NOTE: Sort the data in the import files accordingly beforehand, to resolve object dependencies in larger CSV imports. For larger imports from external data sources, use the "ORDER BY" clause to sort the data.

Related Topics

Options for Handling Records

Options for Handling Records

Specify how new and existing data sets are handling when they are imported. During import, the source data sets (case C) are compared with the entries in the database (case A).

You can restrict the number of relevant database entries by using the Condition for target objects (case B). The condition is tested when importing begins. There is a wizard available though the button next to the input field, to help you formulate your condition.

The import needs to take several cases into account and react accordingly to each one:

  • The data set from the source data does not exist in the database (case E) yet. The entry will be added if the option Insert new data set is set.

    IMPORTANT: If the option Insert new data set is set, the entries that are in the source data but are not in the range of relevant database entries due to the Condition for target objects, are treated as a new data set and are inserted into the database (case G). This can lead to errors (double data sets).

  • There is an entry in the database that corresponds to the source data set (case D). If the option Update existing data set is set, the entry in the database is updated.
  • There are several entries in the database that correspond to the source data set. A error is logged.
  • There is an entry in the database that does not exist in the source database (case F). If the option Delete sentences that no longer exist is set, the entry is deleted from the database.

Figure 57: Example for Handling Data Sets

Table 326: Key for Handling Data Sets
Case Description
A All objects in the database.
B Database set restricted by condition.
C Entry in source data.
D All entries in the database and in the source data. Typical action: update all entries in the database.
E Entries that are only in the source data but not in the database. Typical action: add new entry in the database.
F Entries that are in the database but not in the source data. Typical action: clean up entries in the database.
G Entries that are in the source data but no in range selected in the database. These entries are treated as in case E although adding entries may cause conflicts in certain circumstances.
Related Documents