Setting the Current Locale in Catalog Manager

Localizing Oracle Business Intelligence 15-17 You can select all the subject areas at once, or select them individually and create a separate string file for each one. In the right pane, the translated values and the original strings names and descriptions are displayed. These are placed in session variables for use by Presentation Services. Only those objects with the externalization flag set in the Presentation layer are displayed in the right pane

6. Click Save.

7. In the Save As dialog, select a type of file and an encoding value and click Save.

8. In the Externalized Strings dialog, click Close.

9. Optional To disable externalization, right-click a Presentation layer object and select Externalize Display Names, then Disable Externalization, or Externalize Descriptions then Disable Externalization. Selecting one of these options automatically deselects the Custom display name or Custom description options in the Properties dialog for the selected object and all of its child objects. When you have created the string file using the Externalize Strings utility, you can use it to translate the strings for the metadata objects, as described in the following procedure. To translate strings for metadata from the exported string file: 1. Open the string file and examine the columns: ■ The first column contains the actual repository object names, which have a prefix of their type. ■ The second column contains the session variables that correspond to the name of each object or description, with a default prefix of CN_ for custom names and CD_ for custom descriptions. 2. In the third column of the file, ask the translation team to provide the translation of the name of each object. 3. Add a fourth column called Language. In this column, specify the code for the language in which the name was translated, such as de. 4. Load the string file into a database table. 5. In the Administration Tool, import the table into the physical layer. 6. Load the translated strings using row-wise initialization blocks. Ensure that you set the target of the initialization block to Row-wise initialization and that the execution precedence is set correctly. For example, you could do the following: a. Create a session initialization block that has the data source from a database, using a SQL statement such as the following one: SELECT VALUEOFNQ_SESSION.WEBLANGUAGE FROM DUAL b. In the Session Variable Initialization Block dialog for SET Language, specify the LOCALE session variable for the Variable Target. This ensures that whenever a user signs in, the WEBLANGUAGE session variable is set. Then this variable sets the LOCALE variable using the initialization block. 15-18 System Administrators Guide for Oracle Business Intelligence Enterprise Edition c. Create another session initialization block that creates a set of session variables using a database-specific SQL statement such as the following one in the Session Variable Initialization Block Data Source dialog: select SESSION_VARIABLE, TRANSLATION from external where LANGUAGE = VALUEOFNQ_SESSION.LOCALE This block creates all the variables whose language matches the language that the user specified during sign-in. d. In the Session Variable Initialization Block Variable Target dialog, set the target of the initialization block to Row-wise initialization. e. In the Execution Precedence area of the Session Variable Initialization Block dialog, specify the previously created initialization block, so that the first block that you created earlier is executed first. 7. Save your changes.

15.6 Supporting Multilingual Data

This section describes how you can configure the Oracle BI Server to display field information in multiple languages, and contains the following topics: ■ Section 15.6.1, What is Multilingual Data Support? ■ Section 15.6.2, What is Lookup? ■ Section 15.6.3, What is Double Column Support? ■ Section 15.6.4, Designing Translation Lookup Tables in a Multilingual Schema ■ Section 15.6.5, Creating Logical Lookup Tables and Logical Lookup Columns ■ Section 15.6.6, Creating Physical Lookup Tables and Physical Lookup Columns ■ Section 15.6.7, Supporting Multilingual Data in Essbase Through Alias Tables ■ Section 15.6.8, Enabling Lexicographical Sorting For information about using the Administration Tool, see Oracle Fusion Middleware Metadata Repository Builders Guide for Oracle Business Intelligence Enterprise Edition. 15.6.1 What is Multilingual Data Support? Multilingual data support is the ability to display data from database schemas in multiple languages. Oracle BI Server supports multilingual schemas by simplifying the administration and improving query performance for translations. Multilingual schemas typically store translated fields in separate tables called lookup tables. Lookup tables contain translations for descriptor columns in several languages, while the base tables contain the data in the base language. Descriptor columns provide a textual description for a key column where there is a logical one-to-one relationship between the descriptor column and the key column. An example of a descriptor column might be Product_Name, which provides textual descriptions for a Product_ Key column. Tip: If you have an Oracle Application Development Framework data source, then you can propagate labels and tooltips from that data source, instead of using the Externalize Strings utility. See Oracle Fusion Middleware Metadata Repository Builders Guide for Oracle Business Intelligence Enterprise Edition for more information.