15BR_LocalizingOracleBIMetadata

8/22/2019 15BR_LocalizingOracleBIMetadata

1/20

Copyright 2010, Oracle and/or its affiliates. All rights reserved.

Localizing Oracle BI Metadata


2/20

Copyright 2010, Oracle and/or its affiliates. All rights reserved.15 - 2

Objective

After completing this lesson, you should be able to configureOracle Business Intelligence metadata to support multilingual

environments.


3/20


Business Challenges and Solution

Challenges: Companies require multilingual support for global

deployments of Oracle Business Intelligence.

End users need to make decisions based on applications

and data presented in their own language.Solution:

Add multilingual support to Oracle BI.


4/20


Oracle BI Multilingual Support

Requires three types of configurations: Repository metadata, such as presentation folders

Database data, such as product names

Report and dashboard metadata, such as chart labels

Focus of this lesson

Focus of next lesson

Covered in a separate course


5/20


Configuring Oracle BI Metadata

Involves configuring names and descriptions of repositorymetadata:

Uses a translation table to store language-specific names

and descriptions for metadata

Uses initialization blocks and variables to select thepreferred language of the user and the corresponding

names and descriptions


6/20


WEBLANGUAGE Session Variable

Is populated with a two-character, lowercase language codewhen a user selects a language during login

Example: en for English

User selects language during

login, which populates theWEBLANGUAGE session variable.


7/20Copyright 2010, Oracle and/or its affiliates. All rights reserved.15 - 7

LOCALE Configuration Setting

Specifies how data is returned from the server Localizes message strings, such as names of days and

months

Default LOCALE is specified

in the NQSConfig.ini file.



Changing Localization Preferences

Users can change localization preferences on the My Accountpage.



ABC Example

Localize metadata to the French language.

Localized

metadata



Steps to Localize Metadata

1. Externalize metadata objects.2. Run the Externalize Strings utility.

3. Modify the translation file.

4. Load the translation table.

5. Import the translation table.6. Create an initialization block.

7. Modify My Account preferences.

8. Verify the translations.



1. Externalize Metadata Objects

To set display variables, select Externalize Display Names orExternalize Descriptions for each Presentation layer object thatrequires translation.

Name display variable

Description display variable



2. Run the Externalize Strings Utility

Exports the names of the Presentation layer objects to afile in comma-separated value, tab-delimited, or XML

format

Externalizes the Presentation layer strings to enable setup

of local language translations for them

Display variablePresentation layer object Presentation layer object string



3. Modify the Translation File

Modify the file generated by the Externalize Strings utilityto include language translations:

Add a row for each language and display variable.

Include required columns needed for translation table:

LANG_ID identifies the language. MSG_NUM identifies the display variable to be translated.

MSG_TEXT contains the translated text. Add row for each languageand display variable.



4. Load the Translation Table

Use SQL Loader to load the translation file into an existingtable.



5. Import the Translation Table

Import the translation table to the Physical layer to give OracleBI Server access to the translation information.

Import populated translation

table to the Physical layer.



6. Create an Initialization Block

Create a row-wise initialization block that populates sessionvariables with values from the translation table based on thevalue ofWEBLANGUAGE.

Populates the MSG_NUM and

MSG_TEXT session variables

based on the WEBLANGUAGE

session variable

Row-wise initialization



7. Modify My Account Preferences

Set locale or language on the My Account page.

Setting a locale automatically

selects the native language for

that locale.



8. Verify the Translations

Verify that objects are translated as expected.

Check NQQuery.log and verify that the initialization block

issued a SQL query.

Metadata objects

translated



Summary

In this lesson, you should have learned how to configure OracleBI metadata to support multilingual environments.


20/20

Practice 15-1 Overview:

Localizing Repository Metadata

In this practice, you localize Oracle BI repository metadata.

15BR_LocalizingOracleBIMetadata

Documents