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

Configuring Column Properties

To edit column properties

  1. Select the column on the Define column page and click the button.
  2. Configure the column properties.
  3. Click OK.

You can configure the following settings for a column.

Table 311: Configuring the Column Properties
Property Remarks
Name Technical identifier for the column.
Data type Permitted .Net data types are listed in a pop-up menu. These are represented internally as SQL data types.
Length A length is only given for the .Net data type "String". A length of 38 is entered for a UID.
Column contains UIDs Marks a column as a UID (table DialogColumn, column IsUID). This option is only permitted for columns with the .Net data type "String" and length 38.
Column contains unicode Marks the column as unicode. This option is only permitted for .Net data types "String" and "Text".
Primary key The primary key is used.
Compulsory field Labels column as compulsory (table DialogColumn, column CustomMinLen).
Display name Column name for displaying (table DialogColumn, column Caption).
Display in Filter Designer The column is displayed in the Filter Designer or the Rule Editor for creating request.
Do not auto extend permissions Permissions for predefined permissions groups are not issued automatically for this custom schema extension on a predefined table, even if the configuration parameter "Common\AutoExtendPermissions" is set.
Comment Enter a comment, which provides information about using the new column.(table DialogColumn, column CustomComment).
Initial value

Specifies an initial value for the column. This is transferred to the existing data set in the extended table. The initial value for numerical data types is "0". The initial value for the data type "Bool" is "False".

Sort order The sort order specifies the position for displaying the column on the generic form and the custom tab of the default form. Columns with a value less than one are not displayed.
Foreign key This is a foreign key column.
From table Only for foreign key tables: references tables by foreign key relations.
Delete restrictions Only for foreign keys: restrictions for testing referential integrity when an object is deleted.
Insert restrictions Only for foreign keys: restrictions for testing referential integrity when an object is inserted.

Only value types that are already in the One Identity Manager data model are permitted.

Table 312: List of Permitted Data Types
.Net Data Types SQL Server data type
Binary Image
Bool Bit
Date Datetime
Double Float
Int Int
Long Bigint
String Varchar/nVarchar and Char (only String(38))
Text Text, nText
Table 313: Permitted Restrictions for Testing Referential Integrity
Restriction Meaning
DeleteNotRestricted (D) Dependencies are not taken into account on deletion.
DeleteRestrict (DR) The object can only be deleted when no more references to other objects exist.
DeleteCascade (DC) All dependent objects are deleted when this object is deleted.
DeleteSetNULL (DS) All links to other objects are deleted when the object is deleted (SetNULL).
InsertNotRestricted (I) Dependencies are not taken into account on insertion.
InsertRestrict (IR) Checks for the referenced object when the object is added.
Related Topics

Creating a Read-Only Database View

Views with the table type "read only" can be parts but also unions of the underlying tables. Views with type "read only" are predefined. Templates and formatting rules cannot be defined for columns in these views.

Database views of type "read only" are mainly used to edit the user interface and for creating reports.

To create a database view of type "read-only" in the Schema Extension

  1. Open Launchpad and select One Identity Manager Schema Extension. This starts the program "Schema Extension".
  2. Click Next on the start page.
  3. Enter connection credential for the One Identity Manager database on the Database connection page and click Next.
  4. Select the extension method New view table on the Extension method page and click Next.
  5. Enter the properties for the database view on the Create view page and click Next.
    Table 314: Database View Properties
    Property Description
    Table Name of the table. The name of the new table must begin with the prefix "CCC". The table name is formatted as CCC<table name>.
    Display name The display name is used, for example, to identify the table in a database search or for error output.
    Description You can enter a comment on a table about using it in the data model.
    View definition Enter the database query as a SELECT instruction. The first column in the database query is used as primary key column in the database view.

    NOTE: It is recommended you reference the primary key column for the queried table as the first column in view definition. If this is not possible, then at least select a unique characteristic.

  6. Next step: Create foreign key relations on the page Create FK relations for view. For more information, see Creating Foreign Key Relations for Views.
Related Topics

Creating Foreign Key Relations for Views

If a database view contains a foreign key column, you specify which destinations tables should be referenced. The table and column relations are generated automatically.

To create a foreign key for a view in the Schema Extension

  1. You create foreign key relations on the page Create FK relations for view.
    1. Double-click on in front of the column name to release the "Destination table" column.
    2. Select the destination table in the column "Destination table".
    3. Click Next.
  2. Next step: You define the column properties on the Configure columns page. For more information, see Configuring Column Properties.
Related Topics

Creating a Union View

Database views with the table type "Union" are views of the union of different tables and supply a grouping of different object types with the same context. Thus the union view QERAccProductUsage determined, which service items are used in which products, for example.

Views of type "Union" are predefined. Templates and formatting rules cannot be defined for columns in these views. The object key column (XObjectKey) must be referenced in the view definition. This makes it possible to create single object with its valid permissions.

"Union" views are mainly used for editing the user interface and for creating reports.

To create a database view of type "union" in the Schema Extension

  1. Open Launchpad and select One Identity Manager Schema Extension. This starts the program "Schema Extension".
  2. Click Next on the start page.
  3. Enter connection credential for the One Identity Manager database on the Database connection page and click Next.
  4. Select the extension method New union table on the Extension method page and click Next.
  5. Enter the database view properties on the Create union view page and click Next.
    Table 315: Database View Properties
    Property Description
    Table Name of the table. The name of the new table must begin with the prefix "CCC". The table name is formatted as CCC<table name>.
    Display name The display name is used, for example, to identify the table in a database search or for error output.
    Description You can enter a comment on a table about using it in the data model.
    View definition Enter the database query as a SELECT instruction. You must reference the object key (XObjectKey) as the first column in the database query. Using the object key makes faster access to individual objects with valid permissions possible.
  6. Next step: Select the permissions groups to obtain permissions for the schema extensions on the page, Access permissions. For more information, see Permissions for Schema Extensions.
Related Topics
Related Documents