Chat now with support
Chat mit Support

Identity Manager 9.0 LTS - 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 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 Windows 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

Language-dependent data representation

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.

Detailed information about this topic
Related topics

Basic rules for using language-dependent data

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

  • The language is set up in the database and labeled with the Select in front-end option.

  • A fallback language for the database is set. In default installation of One Identity Manager, the language used is English - United States [en-US]. This language is used if there is no translation available for a language-dependent data break down in the user’s requested language.

  • The Multilingual option 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 Visual Basic .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 DialogMultiLanguage table. A key, the language and the translation are entered into the table.

Example:

The QERResource.Ident_QERResource column has the Resource text displayed as its column name in the login language English - United States [en-US] (DialogColumn.Caption). The Ressource column name should be used for the login language German - Germany [de-DE].

The QERResource.Ident_QERResource column contains the value Car. A user with the login language English - United States [en-US] is shown the Car value. A user with the login language German - Germany [de-DE] is shown the Auto value.

Table 67: Example of language-dependent entries in the DialogMultiLanguage table
Column Name Key language Value

DialogColumn.Caption

Resource

English - United States [en-US]

Resource

Resource

German - Germany [de-DE]

Resource

QERResource.Ident_QERResource

Car

English - United States [en-US]

Car

Car

German - Germany [de-DE]

Auto

Related topics

Flagging columns for translation

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

To label a column for translation

  1. In the Designer, select the One Identity Manager schema category.

  2. Select the table and start the Schema Editor with Show table definition.

  3. Select the column and then the Column properties view.

  4. Select the Column tab and edit the Multilingual property. Specify the following settings:

    • Translation target: The column content is displayed in translation.

    • Translation source: The column supplies the translation.

    • #LD content: The column has contents in #LD notation. The contents are extracted for translation.

    • Without text memory fallback: The text store is not used as fallback for the column.

    You can combine the values. The combination of values determines the resulting translation.

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

    • Switch to the Language dependencies tab. Under Translation source, select the column that is to be used as the translation source.

      NOTE: Ensure that the column used as a translation source has been labeled with Translation source.

Example: A column is translation target and source

The contents of the QERResource.Ident_QERResource column are to be translated. The Ident_QERResource column contains the value Car. A user with the login language English - United States [en-US] should be shown the value Car. A user with the login language German - Germany [de-DE] should be shown the value Auto. The actual translation should be maintained in the QERResource.Ident_QERResource column.

  • Label the QERResource.Ident_QERResource column in the Multilingual property with Translation target.

  • Label the QERResource.Ident_QERResource column in the Multilingual property with Translation source.

  • In the Language Editor, translate the entries for the Ident_QERResource column of the QERResource table.

When the column is loaded, it is determined that QERRessource.Ident_QERResource should be translated. For translation, the relevant key for the QERRessource.Ident_QERResource column is determined from the DialogMultiLanguage table and the value saved for the user’s login language is displayed.

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 JobEventGen.ProcessDisplay column in the Multilingual property with the values Translation source and #LD content.

  • Label the DialogProcess.DisplayName column in the Multilingual property with Translation target and as the Language dependecy, enter the JobEventGen.ProcessDisplay column.

  • In the Language Editor, translate the entries for the ProcessDisplay column of the JobEventGen table.

When the column is loaded, it is determined that DialogProcess.DisplayName should be translated. For translation, the relevant key for the JobEventGen.ProcessDisplay column is determined from the DialogMultiLanguage table and the value saved for the user’s login language is displayed.

Related topics

Using the text memory for translation

Translations, which occur frequently or cannot be associated with a particular database column, can be stored in a text memory (QBMTranslationAddOnSource table). 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. You can reference the text store as a translation source.

The text store is also used as a fallback when a fitting translation cannot be found through other translation sources.

TIP: To deactivate use of the text memory as a fallback, flag the column in the Multilingual property with Without fallback translation source.

To enter an item in the text store

  1. In the Designer, select the Base Data > Localization > Translatable texts category.

  2. Select the Object > New menu item and enter the translation key.

  3. In the Language Editor, translate the entries for QBMTranslationAddOnSource.Entrykey.

Related topics
Verwandte Dokumente

The document was helpful.

Bewertung auswählen

I easily found the information I needed.

Bewertung auswählen