Localization refers to the process of adapting the Oracle Business Intelligence deployment to a particular language.
If your users speak languages other than English, then use the information about localization to adapt your deployment to support multiple languages.
For information about supported languages, see System Requirements and Certification.
Several areas of the interface are translated into a user’s native language.
The following list outlines which components of Oracle Business Intelligence are translated into languages other than English:
Installer
Web user interface
Job Manager interface of the Oracle BI Scheduler
Catalog Manager
Oracle BI Presentation Services messages:
error
warning
information
Oracle BI Server functions:
DayName
MonthName
Note:
If a query is issued using the DayName or MonthName function, but the function is not shipped to a back-end database, then the day or month name is returned in the localized language but the column name remains in English (or might be affected by other localization controls). As an example of this situation, if the LOCALE parameter is set for German, the MonthName query returns the string "Mai" but the column header remains "Name of Month."Oracle BI Server and Oracle BI Scheduler messages:
error
warning
information
Log files:
nqserver.log for Oracle BI Server
nqquery.log for Oracle BI Server
If Clustering is enabled, nQCluster.log for Oracle BI Server Cluster
Metadata:
Dashboards and analyses (Oracle BI Presentation Catalog)
Presentation table and column names (.rpd file)
Oracle BI Administration Tool interface
ODBC setup
The following list outlines which components of Oracle Business Intelligence are not localized:
ODBC client tools:
nqcmd (UNIX)
nqcmd.exe (Windows)
nqclient.exe (Windows)
Numerous Oracle Fusion Middleware components, such as Oracle WebLogic Server Administration Console and Fusion Middleware Control, are translated. See Oracle Fusion Middleware documentation for information.