Converse agora com nosso suporte
Chat com o suporte

Identity Manager 9.2.1 - Configuration Guide

About this guide One Identity Manager software architecture Customizing the One Identity Manager default configuration Customizing the One Identity Manager base configuration One Identity Manager schema basics
Overview of the One Identity Manager schema Table types and default columns in the One Identity Manager data model Notes on editing table definitions and column definitions Table definitions Column definitions Table relations Dynamic foreign key Supporting file groups
Editing the user interface
Object definitions for the user interface User interface navigation Forms for the user interface Statistics in 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 Using predefined database queries
Localization in One Identity Manager Process orchestration in One Identity Manager
Mapping processes in One Identity Manager Setting up Job servers
The One Identity Manager Service functionality Tracking changes with process monitoring Conditional compilation using preprocessor conditions Scripts in One Identity Manager
Visual Basic .NET scripts usage Notes on message output Notes on using date values Tips for using PowerShell scripts Using dollar ($) notation Using base objects Calling functions Pre-scripts for use in processes and process steps Using session services Using #LD notation Script library Support for processing scripts in the Script Editor Creating and editing scripts in the Script Editor Copying scripts in the Script Editor Testing scripts in the Script Editor Testing script compilation in the Script Editor Overriding scripts Permissions for running scripts Editing and testing script code with the System Debugger Extended debugging in the Object Browser
One Identity Manager query language Reports in One Identity Manager Adding custom tables or columns to the One Identity Manager schema Web service integration One Identity Manager as SCIM 2.0 service provider Processing DBQueue tasks One Identity Manager Service configuration files

Advanced configuration of columns

To edit column properties

  1. Select the column on the Configure columns of table page and click the button.

  2. Configure the column properties.

  3. Enter the following information on the Advanced tab.

    Table 170: Advanced configuration of columns
    Property Remarks

    Name

    Technical identifier for the column The column name is formed from CCC_<column name.

    Data type

    Column data type Permitted .Net data types are listed in a pop-up menu. These are represented internally as SQL data types. The only permitted data types are those already used in the One Identity Manager data model.

    Length

    Column length The column length is only specified for the .Net String data type. For columns containing UIDs, enter the value 38.

    Column contains UIDs

    Specifies whether this is UID column. This option is only permissible for columns with the String .Net data type and a length of 38 characters.

    Column contains unicode

    Specifies whether the column contains Unicode. This option is only permissible for String .Net data types.

  4. Enter the following information on the Base values tab.

    Table 171: Column base values
    Property Remarks

    Primary key

    Specifies whether the column is used as a primary key.

    Required field

    Specifies whether a column must be filled.

    Display name

    Specifies how the column is labeled.

    Show in wizards

    Specifies whether the column is offered in the Rule Editor for compliance rules to create queries and in the Web Portal to display tabular overviews.

    Do not auto extend permissions

    For custom columns in a predefined table, permissions are not automatically assigned to predefined permissions groups, even though the Common | AutoExtendPermissions configuration parameter is set.

    Comment

    Additional information about the column.

    Initial value

    Initial value for the column This value is transferred to the existing data records of the extended table. The initial value for numerical data types is 0. The initial value for the Bool data type is False.

    Sort order

    The sort order specifies the position for displaying the column on the generic form and the custom tabs of the default form. Columns with a value less than 1 are not displayed on the forms.

  5. Enter the following information for foreign key columns on the Key column values tab.

    Table 172: Properties for foreign key columns
    Property Remarks

    Foreign key

    Specifies whether the column is a foreign key column.

    From table

    Referenced table for foreign key relations

    Delete restrictions

    Restriction for testing referential integrity when deleting an object

    Insert restrictions

    Restriction for testing referential integrity when inserting an object

  6. Enter the following information for dynamic foreign key columns on the Dynamic foreign key tab.

    Table 173: Properties for foreign key columns
    Property Remarks

    Referenced table

    Select the tables to be referenced. All tables are permitted, if there are no restrictions.

    Delete restrictions

    Restriction for testing referential integrity when deleting an object

    Insert restrictions

    Restriction for testing referential integrity when inserting an object

  7. Click OK.
Related topics

Creating database views with read-only type

Database views with the Read only table type may be subsets or unions of the underlying tables. Database view with the Read only type are predefined database views. Templates and formatting rules cannot be defined for columns in these views.

Database views of the Read only type are for display only and are mainly used for editing the user interface and creating reports.

Technical details

  • The technical identifier for the database view is automatically formed according to the CCC<Table name> schema.

  • The first column of the database query (view definition) is used as the primary key column of the database view.

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

  • 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.

  • If you want to index the database view for the full-text search, the XDateInserted, XDateUpdated, and XObjectKey columns must be available.

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

  1. Start the Launchpad and log in to the One Identity Manager database.

  2. Open the Launchpad and select the One Identity Manager Schema Extension entry. This starts the Schema Extension program.

  3. Click Next on the start page.

  4. On the Database connection page, check the connection data for the One Identity Manager database.

  5. On the Select method page, select Create view.

  6. On the Create view page, enter the following information.

    Table 174: Database view properties
    Property Description

    Table

    A technical name for the database view.

    Display name

    Name displayed for the database view. The display name is used, for example, to identify the database view in a database search or error output.

    Description

    Comments on using the database view.

    View definition

    Enter the database query as a Select statement.

  7. (Optional) Create the foreign key relations on the Create FK relations for views page.

    • Double-click the icon in front of the column name and select the target table in the Target table column.

  8. On the Configure columns of table page, enter display names for the columns.

  9. (Optional) Click to configure more column properties. For more information, see Advanced configuration of columns.

Related topics

Using Common Table Expressions in read-only database views

In One Identity Manager 7.0, the behavior was changed for Common Table Expressions (CTEs) with the with keyword as condition for view definitions in Read-only database views. Conditions for view definitions are embedded in a summarized query. This means, there is no guarantee that CTEs are placed right at the top of the query.

Possible error messages

(execute slot single)50000 0 re-throw in Procedure QBM_ZViewBuildR, Line 1050000 0 rethrow in Procedure QBM_PViewBuildR_intern, Line 10250000 0 re-throw in Procedure QBM_PViewBuildR_intern, Line 8250000 0 re-throw in Procedure QBM_PViewBuild_FromAddOn, Line 6550000 0 re-throw in Procedure QBM_PSQLCreate, Line 26156 0 detected in (...) Procedure ..., Line 6156 0 Incorrect syntax near the keyword 'with'

Recommended action

  1. Create a database view using the CTE.

    Example:

    create view CCC_Vxy as

    with myWithClause (column1, column2) as (

    select 1 as column1, 2 as column2

    )

    select * from myWithClause

    go

  2. Use the database view in the additional view definition (QBMViewAddon) of Read-only database views.

    select * from CCC_Vxy

Creating database views with Union type

Database views with the Union table type are union views of various tables and are mainly used to group various object types with the same context. In the QERAccProductUsage union view, for example, you determine which service items are used in which IT Shop products.

Database views with the Union type are predefined database views. Templates and formatting rules cannot be defined for columns in these views. In the view definition, the object key column (XObjectKey) must be referenced. This makes it possible to create a single object with its permitted permissions.

Database views of the Union type are mainly used for editing the user interface and creating reports.

Technical details

  • The technical identifier for the database view is automatically formed according to the schema CCC<Table name>.

  • As the first column of the database query (view definition), the object key (XObjectKey) must be referenced. The object key allows faster access to a single object with its valid permissions.

  • If you want to index the database view for the full-text search, the XDateInserted, XDateUpdated, and XObjectKey columns must be available.

To create a database view of Union type in the Schema Extension

  1. Start the Launchpad and log in to the One Identity Manager database.

  2. Open the Launchpad and select the One Identity Manager Schema Extension entry. This starts the Schema Extension program.

  3. Click Next on the start page.

  4. On the Database connection page, check the connection data for the One Identity Manager database.

  5. On the Select method page, select Create union view.

  6. On the Create union view page, enter the following information.

    Table 175: Database view properties
    Property Description

    Table

    A technical name for the database view.

    Display name

    Name displayed for the database view. The display name is used, for example, to identify the database view in a database search or error output.

    Description

    Comments on using the database view.

    View definition

    Enter the database query as a Select statement.

Related topics
Documentos relacionados

The document was helpful.

Selecione a classificação

I easily found the information I needed.

Selecione a classificação