This chapter provides information on customizing Oracle Adaptive Access Manager for your locale.
Oracle Adaptive Access Manager 11g is translated into 26 languages for OAAM Server and 9 for OAAM Admin. These translations are bundled along with the English version of the product.
The languages and their locale identifiers (in parentheses) are listed below. A locale identifier consists of at least a language identifier, and a region identifier (if required).
OAAM Admin is translated into French (fr), German (de), Italian (it), Spanish (es), Brazilian Portuguese (pt_br), Japanese (ja), Korean (ko), Simplified Chinese (zh_cn), and Traditional Chinese (zh_tw).
When one of the non-admin locale languages is set in the browser (for example Arabic), OAAM Server uses the default locale, English.
OAAM Server is translated into 26 languages: French (fr), German (de), Italian (it), Spanish (es), Brazilian Portuguese (pt_br), Japanese (ja), Korean (ko), Simplified Chinese (zh_cn), Traditional Chinese (zh_tw) Arabic (ar), Czech (cs), Danish (da), Dutch (nl), Finnish (fi), Greek (el), Hebrew (iw), Hungarian (hu), Norwegian (no), Polish (pl), Portuguese (pt), Romanian (ro), Russian (ru), Slovak (sk), Swedish (sv), Thai (th), and Turkish (tr).
There is no flag to turn-off localization, but there is a user-defined enum that captures the locales supported by the deployment. The enum can be used to enable only one locale.
You would change the locale.enum.XXX.adminSupported and locale.enum.XXX.enabled properties to false for each unwanted locale.
The default locales are set in the client_resource_<locale>.properties file using the bharosa.locale. enum. Refer to "Extending/Customizing OAAM" in Oracle Fusion Middleware Developer's Guide for Oracle Adaptive Access Manager for instructions on customizing Oracle Adaptive Access Manager.
An example of a bharosa.locale. enum is shown here:
bharosa.locale.enum.german=2 bharosa.locale.enum.german.name=German bharosa.locale.enum.german.description=German bharosa.locale.enum.german.language=de bharosa.locale.enum.german.country= bharosa.locale.enum.german.adminSupported=true bharosa.locale.enum.german.enabled=true
To enable the default locale:
Add and set the bharosa.local.enum.<locale>.enabled properties of the locales you want to support to true.
Add and set the bharosa.local.enum.<locale>.enabled properties of the locales you do not want to support to false.
Add and set the bharosa.default.locale property to match the bharosa.locale.enum.<locale> property of your locale.
Note:
The only locales supported are the ones listed in the enums.A German bank wants to set German as the default language and wants to support only German. To do this, follow these steps for client_resource_de.properties:
If the locale enum does not exist, create it:
bharosa.locale.enum.german.enabled=true
If the locale enum already exists, set it to true.
If present, set other bharosa.local.enum.<locale>.enabled properties to false.
bharosa.locale.enum.italian.enabled=false bharosa.locale.enum.french.enabled=false bharosa.locale.enum.portuguese_br.enabled=false bharosa.locale.enum.spanish.enabled=false bharosa.locale.enum.korean.enabled=false bharosa.locale.enum.chinese_cn.enabled=false bharosa.locale.enum.chinese_tw.enabled=false bharosa.locale.enum.japanese.enabled=false bharosa.locale.enum.arabic.enabled=false bharosa.locale.enum.czech.enabled=false bharosa.locale.enum.danish.enabled=false bharosa.locale.enum.dutch.enabled=false bharosa.locale.enum.finnish.enabled=false bharosa.locale.enum.greek.enabled=false bharosa.locale.enum.hebrew.enabled=false bharosa.locale.enum.hungarian.enabled=false bharosa.locale.enum.norwegian.enabled=false bharosa.locale.enum.polish.enabled=false bharosa.locale.enum.portuguese.enabled=false bharosa.locale.enum.romanian.enabled=false bharosa.locale.enum.russian.enabled=false bharosa.locale.enum.slovak.enabled=false bharosa.locale.enum.swedish.enabled=false bharosa.locale.enum.thai.enabled=false bharosa.locale.enum.turkish.enabled=false
Set bharosa.default.locale property to match the value of the locale enum.
Since bharosa.locale.enum.german=2, set bharosa.default.locale property to 2.
If the property did not exist, create it.
A Brazilian bank wants to set Brazilian Portuguese as the default, but wants to display in OAAM Server in all the other languages that OAAM Server had been translated to. To do this:
If the locale enum does not exist, create it:
bharosa.locale.enum.pt_br.enabled=true
If the locale enum already exists, set it to true.
Set all other bharosa.local.enum.<locale>.enabled properties using the Properties Editor to false.
Set bharosa.default.locale property to the value of the locale enum using the Properties Editor.
If bharosa.locale.enum.pt_br=9, set bharosa.default.locale property to 9.
Set bharosa.locale.enum.<locale>.enabled property in client_resource_<locale>.properties for all the languages OAAM Server had been translated to and ensure they are set to true.
bharosa.locale.enum.german.enabled=true bharosa.locale.enum.italian.enabled=true bharosa.locale.enum.french.enabled=true bharosa.locale.enum.portuguese_br.enabled=true bharosa.locale.enum.spanish.enabled=true bharosa.locale.enum.korean.enabled=true bharosa.locale.enum.chinese_cn.enabled=true bharosa.locale.enum.chinese_tw.enabled=true bharosa.locale.enum.japanese.enabled=true bharosa.locale.enum.arabic.enabled=true bharosa.locale.enum.czech.enabled=true bharosa.locale.enum.danish.enabled=true bharosa.locale.enum.dutch.enabled=true bharosa.locale.enum.finnish.enabled=true bharosa.locale.enum.greek.enabled=true bharosa.locale.enum.hebrew.enabled=true bharosa.locale.enum.hungarian.enabled=true bharosa.locale.enum.norwegian.enabled=true bharosa.locale.enum.polish.enabled=true bharosa.locale.enum.portuguese.enabled=true bharosa.locale.enum.romanian.enabled=true bharosa.locale.enum.russian.enabled=true bharosa.locale.enum.slovak.enabled=true bharosa.locale.enum.swedish.enabled=true bharosa.locale.enum.thai.enabled=true bharosa.locale.enum.turkish.enabled=true
Set bharosa.default.locale property in client_resource_<locale>.properties to 9.
A French bank wants clients to see French as a default, and wants to support only French, German, English, and Italian. The French locale enum is already present in the client_resource_fr.properties file.
bharosa.locale.enum.french=5 bharosa.locale.enum.french.name=French bharosa.locale.enum.french.description=French bharosa.locale.enum.french.language=fr bharosa.locale.enum.french.country= bharosa.locale.enum.french.adminSupported=true bharosa.locale.enum.french.enabled=true
To configure the application:
In client_resource_fr.properties set bharosa.locale.enum.<locale>.enabled to true for German, Italian, and English.
bharosa.locale.enum.german.enabled=true bharosa.locale.enum.italian.enabled=true bharosa.locale.enum.english.enabled=true
Set all other bharosa.local.enum.<locale>.enabled properties to false.
Set bharosa.default.locale property to the value of the locale enum.
Since bharosa.locale.enum.french=5, set bharosa.default.locale property to 5.
To view the Dashboard in the language you want, set your browser's language preference to the appropriate language.
The data viewed in the Dashboard is based on the server's time zone, but information is presented per your browser settings.
Answers that "sound like" the registered answer, regional spelling differences, and common misspellings are handled by the phonetics algorithm.
For information on customization, see Section 6.10, "Customizing English Abbreviations and Equivalences."
The phonetics algorithm is only supported in English.
For information on customization for locales, see Section 6.11, "Customizing Abbreviations and Equivalences for Locales."
Oracle's Fat Fingering algorithm accounts for typos due to the proximity of keys on a standard keyboard and transposed letters. Answers with typos due to the proximity of keys on a standard keyboard are handled by the fat fingering algorithm.
The fat fingering algorithm is only supported in English.
During registration, Oracle Adaptive Access Manager presents customers with question menus. When a customer registers, he or she is required to select one question from each menu. These questions become the customer's "registered questions."
To add questions in Oracle Adaptive Access Manager:
Log in to OAAM Admin.
In the Navigation tree, double-click Questions under KBA. The Questions Search page is displayed.
From the Questions Search page, click the New Questions button.
The New Questions page appears where you can enter details to create a new question.
You could also open the New Questions page by right-clicking Questions under KBA in the Navigation tree and selecting Create from the context menu that appears.
When the New Question page first appears, the default value for the question status is Active.
Question, Category, Status, and Locale are required fields.
Pick a locale from the list of locales available.
By default, the Locale menu displays English and 27 other default locale languages.
Type the new question in the Question field.
Note:
The deployment administrator must ensure that there are enough questions in the database for each of the supported locale as configured in OAAM Admin during deployment; otherwise, OAAM Server displays only the English language questions during registration.The number of locale-specific questions must be equal to or greater than the "Questions User Will Register" multiplied by the "Questions per Menu" multiplied by the "Categories per Menu."
Oracle Adaptive Access Manager supports the concept of "fuzzy logic." Fuzzy logic, in part, relies on pre-configured sets of word equivalents, commonly known as abbreviations.
In the English version of Oracle Adaptive Access Manager, there are several thousand English abbreviations (and equivalences).
In all other languages, it is necessary for the installer to enhance the brief abbreviation files provided. Without additions, the fuzzy logic will be not as effective.
For information on customizing abbreviations and equivalences for locales, refer to Section 6.11, "Customizing Abbreviations and Equivalences for Locales."