Display the translated content.

15-16 System Administrators Guide for Oracle Business Intelligence Enterprise Edition

15.4.3.1 Handling the NLS Locale Not Supported Error Message

If you do not have the appropriate locale installed, then the Oracle BI Server does not start, and the NQSServer.log file contains the following error: [47013] NLS locale xxx is not supported by the operating system. where xxx is the locale that is specified in the NQSConfig.INI file for the SORT_ ORDER_LOCALE parameter. Take the following actions to resolve this error: ■ UNIX . Install the locale that is indicated in Table 15–2 for the requested language. ■ Windows . Add the corresponding language pack using the Regional Settings dialog.

15.4.3.2 Setting the Japanese Locale on AIX Systems

When using a Japanese localization on an AIX platform, you might discover that the Oracle BI Server does not start. If you encounter this issue, then use the following procedure. To set the Japanese locale on an AIX system: 1. Ensure that the JA_JP.UTF-8 locale is installed. If it is not, then install it. 2. Open the NQSConfig.INI file for editing, as described in Section 3.4, Using a Text Editor to Update Configuration Settings. 3. In the General section, set the following parameters, being aware that the settings are case-sensitive: – LOCALE = Japanese; – SORT_ORDER_LOCALE = Japanese; 4. Save and close the NQSConfig.INI file.

15.5 Localizing Metadata Names in the Repository

You can use the Externalize Strings utility in the Administration Tool to localize the names of subject areas, tables, hierarchies, columns, and their descriptions in the Presentation layer. You can save these text strings to an external file with ANSI, Unicode, and UTF-8 encoding options. To externalize strings for localization: 1. Open the repository in the Administration Tool. 2. Right-click any Presentation layer object, such as a subject area, presentation table, or presentation column, and select either Externalize Display Names then Generate Custom Names , or Externalize Descriptions then Generate Custom Descriptions to externalize strings. Selecting one of these right-click externalization options automatically selects the Custom display name or Custom description options in the Properties dialog for the selected object and all of its child objects. For example, if you right-click a subject area and select one of the externalization options, then the externalization flag is set on all presentation tables, columns, hierarchies, and levels within that subject area.

3. Select Tools, then select Utilities.

4. Select Externalize Strings and click Execute.

5. In the Externalize Strings dialog, select a subject area in the left pane. 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.