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

Icons and Images for Configuring the User Interface

When you are configuring the One Identity Manager tools’ user interfaces you can add icons and images for displaying in different parts of them. The default version of the One Identity Manager supplies the icons and images that you can use for configuring the user interface and to create reports. Predefined configurations are maintained by the schema installation and cannot be edited apart from a few properties.

Icons are required to be in PNG format with sizes of 16x16 pixels, 24x24 and 32x32 pixels for the graphical interface.

Icons are required for the following use cases.

Table 177: Meaning of the Icons
State Usage
Normal Icons showing an enabled state. These icons must exist in the One Identity Manager database.
Inverted Icons that show and enabled state on a black background. These icons can be converted automatically.
Disabled Icons showing a disabled state. These icons must exist in the One Identity Manager database.

To add an icon

  1. Select the category Base Data | General | Icons in the Designer.
  2. Select Object | New in the menu.
  3. Give the icon a name.
  4. Upload the icon using .

To add images for reports

  1. Select the category Base Data | General | Large images in the Designer.
  2. Select Object | New in the menu.
  3. Give the image a name.
  4. Upload the image using .
  5. Save the image with the button.

    The image is displayed with certain important image properties.

Language Dependent Data Representation

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 One Identity Manager default 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.

Detailed information about this topic
Related Topics

Basic Rules for Using Language Dependent Data

In order to use multi-language data representation in the One Identity Manager, the following prerequisites need to be fulfilled:

  • The language is set up in the database and labeled with Select in front-end.
  • A fallback language for the database is declared. The language "English - United States [en-US]" is used in the One Identity Manager default installation. This language is used if there is no translation available for language dependent drilling in the user’s requested language.
  • The option Multilingual has to be set on the column definitions in order to use multi-language display text.
  • Source and target of the translation are known.
  • #LD notation is used for outputting language dependent data from within VB.Net expressions. #LD text is automatically extracted for translation. To do this, a column must be labeled as #LD content.

The translations are stored in the table DialogMultiLanguage. A key, the language and the translation are entered into the table.

Example

The text "Resource" should be shown as column name for the column Ident_QERResource if the login language is "English - United States [en-US]" and "Ressource if the login language is "German - Germany [de-DE]". The value "Car" is entered in the column Ident_QERResource. If the login language is "English - United States [en-US]", the word "car" should be shown. If the login language is "German - Germany [de-DE]", the word "Auto" should be shown.

Table 178: Example for Language Dependent Entries in the table "DialogMultiLanguage" with Default Language "English - United States [en-US]"
Column Name Key Language Value
DialogColumn.Caption Resource English - United States [en-US] Resource
Resource German - Germany [de-DE] Resource
Ressource.Ident_QERResource Car English - United States [en-US] Car
Car German - Germany [de-DE] Auto
Related Topics

Labeling Columns for Translation

Columns must be marked for translation in order to enter multilingual captions.

To mark a One Identity Manager database column for translation

  1. Select the category One Identity Manager Schema in the Designer.
  2. Select the table and start the Schema Editor with the task Show table definition.

    NOTE: Select a table column in the Designer, then you can start the Schema Editor from the task Show column definition.

  3. Select the column in the Schema Editor and edit the property Multilingual and specify the following settings. The combination of values determines the resulting translation. The following values are permitted:
    Value Meaning
    Translation target The translated column content is displayed.
    Translation source The column supplies translations.
    #LD content The column has content in #LD notation. The contents are extracted for the translation.

    A translation target is normally the same as the translation source. If the translation, however, is taken from another translation source, enter this additionally as a language dependency.

    • Change to the Multilanguage dependencies tab and select the column to act as translation source under Translation source.

      NOTE: The column that is used as translation source, must be labeled as "translation source".

Example: a column is translation target and source

You want the contents of the column QERRessource.Ident_QERResource to be translated. The value "Car" is entered in the column Ident_QERResource. If the login language is "English - United States [en-US]", the word "car" should be shown. If the login language is "German - Germany [de-DE]", the word "Auto" should be shown. The translation itself maintained in the column QERRessource.Ident_QERResource.

  • Label the column QERRessource.Ident_QERResource with the value "translation target" in the Multilingual property.
  • Label the column QERRessource.Ident_QERResource with the value "translation source" in the Multilingual property.
  • Translate the entry for QERRessource.Ident_QERResource in the Language Editor

When the column is loaded, it is determined that QERRessource.Ident_QERResource should be translated. The corresponding key for QERRessource.Ident_QERResource is taken from the table DialogMultiLanguage as translation and displayed in the current user's login language.

Example: a column is translation target and takes its translation from another translation source

The action is displayed in the Manager process view in the current user's login language. The contents of the column DialogProcess.DisplayName are taken from the column JobEventGen.ProcessDisplay. The column JobEventGen.ProcessDisplay may use #LD notation to create the display string.

  • Label the column JobEventGen.ProcessDisplay with "translation source" and the value "#LD content" in the Multilingual property.
  • Label the column DialogProcess.DisplayName with the value "translation target" in the Multilingual property and enter the column JobEventGen.ProcessDisplay as Multilanguage dependencies.
  • Translate the entry for JobEventGen.ProcessDisplay in the Language Editor.

When the column is loaded, it is determined that DialogProcess.DisplayName should be translated. The corresponding key for JobEventGen.ProcessDisplay is taken from the table DialogMultiLanguage as translation and displayed in the current user's login language.

Using the text store

Translations, which occur frequently or cannot be associated with a particular database column, can be stored in text memory (table QBMTranslationAddOnSource). The Web Portal, for example, takes its translations from the text store. In the same way, output text from database triggers is found in the text store. The text store is also used as a fallback when a fitting translation cannot be found through other translation sources. You can also reference the text store as a translation source.

To enter an item in the text store

  • Select the category Base Data | Localization | Translatable texts in the Designer.
  • Select Object | New and enter the translation key.
  • Translate entries for QBMTranslationAddOnSource.EntryKey in the Language Editor.
Related Topics
Related Documents