Multi Language Support(Localization)(Presentation Services)

One of the foremost important features in OBIEE is Localization i.e. Multi country implementation .It’s a robust feature indeed to make the application reusable across several countries in multi country roll-out deployment and thus internationalizing the application.

The Oracle Business Intelligence Presentation layer supports multiple language translations for any presentation column name and column description. When working with Oracle BI Answers or rendering a dashboard, users should see their local language strings in their reports. For example, English-speaking and French-speaking users would see their local language strings in their reports.

The Oracle Business Intelligence Presentation layer supports multiple language translations for any presentation column name and column description. When working with Oracle BI Answers or rendering a dashboard, users should see their local language strings in their reports. For example, English-speaking and French-speaking users would see their local language strings in their reports. There are two kinds of application strings required for the translation in Oracle Business

Policy Store

Testing JAZN translation file is straightforward. You need to deploy them in place of existing system-jazn-data.xml in your dev instance from biapps Installer(C:\Middleware\Oracle_BI1\biapps\admin\provisioning\localization) . You have to bring down the weblogic before replacing the existing jazn with translated jazn. You can then see the display name change in enterprise manager.

JAZN deployment Location - (C:\oracle\middleware\user_projects\domains\bifoundation_domain\config\fmwconfig)

Policy Store looks like below for Arabic language

Catalog Strings

To test the catalog localization, we need to deploy the translated strings (C:\Middleware\Oracle_BI1\biapps\catalog\res\l_xx) into a particular location in oracle instance home (ORACLE_INSTANCE\bifoundation\OracleBIPresentationServicesComponent\coreapplication_obipsn\msgdb\)

Please see this OBIEE documentation link for more details of this - http://docs.oracle.com/cd/E23943_01/bi.1111/e10541/deploylocal.htm#CIHHGIAC

Note: After deploying the translation strings, you should choose appropriate language in UI to see the translated content.

Repository Strings

We have to import the dat files given by translation team into W_LOCALIZED_STRING_G table in the warehouse. The import tool(dataimp.exe) is available in the clear case(biapps\seeddata\Bin) and will be shipped with biapps installer. We then need to configure the initialization block to populate the session variables (row-wise initialization) for translation

Please see the below link for details about importing repository strings (.dat) files into w_localized_string_g table

http://docs.oracle.com/cd/E20490_01/bia.7963/e19038/anyinstadmconfiglocalize.htm#i1039801