Chat now with support
Chat with Support

Identity Manager 8.1 - Configuration Guide

About this guide One Identity Manager software architecture Customizing the One Identity Manager default configuration Adjusting the One Identity Manager base configuration One Identity Manager schema basics 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
Setting up Job servers in Designer Configuring the One Identity Manager Service Handling processes in One Identity Manager
Tracking changes with process monitoring Conditional compilation using preprocessor conditions Scripts in One Identity Manager Reports in One Identity Manager Adding custom tables or columns to the One Identity Manager schema Web service integration SOAP Web Service One Identity Manager as SPML provisioning service provider Processing DBQueue tasks Appendix: Configuration files of the One Identity Manager Service

Using predefined database queries

Direct database queries cannot be carried out from front-ends and web application when an application server is implemented due to security issues. Database queries, which are required on forms for example, must be formulated in One Identity Manager as predefined database queries. Database queries are always executed with the permissions of the current user. Prefined database queries must be assigned to a permissions group.

A wizard in the Web Designer helps you to create database queries for the Web Portal and to link it with at least one permissions group. You can enter more predefined database queries in the Designer.

To create predefined database queries

  1. In the Designer, select Base data | Advanced | Predefined SQL.
  2. Select Object | New.
  3. Edit the master data.
    Table 67: Properties of predefined database queries
    Property Description
    Processing status

    Object processing status. The processing status is used for creating custom configuration packages.

    Description Spare text box for additional explanation.
    Identifier for SQL code A unique identifier that is used to identify the query
    Code Full database query SQL syntax. You can also use SQL parameters in the query.
  4. Assign permissions groups.
    1. Select the View | Select table relations menu item and enable the QBMGroupHasLimitedSQL table.
    2. In the edit view, select the Permissions groups view and select the permissions groups.

Localization in One Identity Manager

The One Identity Manager requires country information at different stages, for example, employee country and state assignments are accessed when email notifications are created or IT Shop workflows are being determined. Language, time zones, public holidays and working hours are mapped as well as countries and states. The basis data is loaded into the database during schema installation.

The One Identity Manager supports language-dependent representation of data. You can use this feature to edit display text in different languages for the One Identity Manager tool user interfaces. You can also create multi-language text for process information output, script processing as well as processing messages.

The default One Identity Manager installation is supplied in the languages English - United States [en-US] and German - Germany [de-DE]. You can use other languages if required. To do this it is advisable to translate the required text before starting to use the One Identity Manager. There is a Language Editor in the Designer to help you do this. A special control element is provided in the One Identity Manager tools which aids multi-language input.

Other languages are made available with the One Identity Manager Language Pack translating the Web Portal.

NOTE: You will find the One Identity Manager Language Pack in the Support Portal under

Detailed information about this topic

Working in different time zones

Time stamps, for example, insert dates or modification dates, are stored in the One Identity Manager with the respective UTC. The object layer transforms this time data into the currently valid time zone data when an object is loaded. The user, therefore, sees all the values in local time. When an object is saved the current time zone data is transformed into UTC data.

Countries and time zones are linked to another in the One Identity Manager schema. This makes it easier to find out the time zones when web fronts such as Web Portal are in use.

Related Topics

Determining working hours

Working hours are calculated for various function in One Identity Manager. For example, to determine working hours in the IT Shop or for determining reaction and solution times for calls in the Helpdesk Module. Weekends and public holidays are taken into account when calculating working hours.

To determine the working hours

  • Ensure that a state and/or county is entered into the employee’s master data.
  • Public holiday are entered by state (county) in the One Identity Manager. You can add separate public holidays for states.
  • To exclude public holidays from the working hours calculation, enable the QBM | WorkingHours | IgnoreHoliday configuration parameter in the Designer.
  • To exclude wekends from the working hours calculation, enable the QBM | WorkingHours | IgnoreWeekend configuration parameter in the Designer.
Related Topics
Related Documents