Skip Headers
Oracle® Fusion Middleware Administrator's Guide for Oracle Adaptive Access Manager
Release 11g (11.1.1)

Part Number E14568-06
Go to Documentation Home
Home
Go to Book List
Book List
Go to Table of Contents
Contents
Go to Index
Index
Go to Master Index
Master Index
Go to Feedback page
Contact Us

Go to previous page
Previous
Go to next page
Next
View PDF

F Globalization Support

This chapter provides information on customizing Oracle Adaptive Access Manager for your locale.

F.1 Supported Languages

Oracle Adaptive Access Manager 11g is translated into 9 Admin languages for OAAM Admin and 26 languages for OAAM Server. 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-OAAM Admin locale languages is set in the browser (for example Arabic), OAAM Admin uses the default locale, English. When one of the non-standard runtime locale languages is set in the browser, 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).

F.2 Turning Off Localization

There is no flag to turn-off localization, but there is a property that captures the locales supported by the deployment. The property 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.

F.3 Configuring Language Defaults for Oracle Adaptive Access Manager

You can configure language defaults in the client_resource_<locale>.properties file using the bharosa.locale. enum property. 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:

  1. Add and set the bharosa.local.enum.<locale>.enabled properties of the locales you want to support to true.

  2. Add and set the bharosa.local.enum.<locale>.enabled properties of the locales you do not want to support to false.

  3. 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.

F.3.1 Example 1

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:

  1. If the locale enum does not exist, create it:

    bharosa.locale.enum.german.enabled=true
    
  2. If the locale enum already exists, set it to true.

  3. 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
    
  4. 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 does not exist, create it.

F.3.2 Example 2

A Brazilian bank wants to set Brazilian Portuguese as the default, but wants to display all the other languages that OAAM Server had been translated to. To do this:

  1. If the locale enum does not exist, create it:

    bharosa.locale.enum.pt_br.enabled=true
    
  2. If the locale enum already exists, set it to true.

  3. Set all other bharosa.local.enum.<locale>.enabled properties using the Properties Editor to false.

  4. 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.

  5. 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
    
  6. Set bharosa.default.locale property in client_resource_<locale>.properties to 9.

F.3.3 Example 3

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:

  1. 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
    
  2. Set all other bharosa.local.enum.<locale>.enabled properties to false.

  3. 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.

F.3.4 Example 4

A German bank wants to set English as the default language and wants to support all other languages. To do this, follow these steps for client_resource_de.properties:

  1. If the locale enum does not exist, create it:

    bharosa.locale.enum.english.enabled=true
    
  2. If the locale enum already exists, set it to true.

  3. If present, set other bharosa.local.enum.<locale>.enabled properties to true.

    bharosa.locale.enum.italian.enabled=true 
    bharosa.locale.enum.german.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
    
  4. Set bharosa.default.locale property to match the value of the locale enum.

    Since bharosa.locale.enum.english=0, set bharosa.default.locale property to 0.

    If the property does not exist, create it.

F.4 Dashboard

The Oracle Adaptive Access Manager Dashboard is an application that provides a high-level view of real monitor data. Monitor data is a representative sample of data. It presents a real-time view of activity via aggregates and trending.

To view the Dashboard in the language you want, set your browser's language preference to the appropriate language.

All data viewed in the Dashboard is based on the time zone of the server. This means that any data generated by OAAM is governed by the time zone of the server, and not the user time zone, but the information is presented per your browser settings. For information on setting the time zone, refer to Section 2.10, "Setting the Time Zone Used for All Time Stamps in the Administration Console."

For more information on the dashboard, refer to Chapter 24, "Using the Dashboard."

F.5 Knowledge Based Authentication

Oracle Adaptive Access Manager provides out-of-the-box secondary authentication in the form of knowledge based authentication (KBA). KBA provides an infrastructure for challenge question creation and logic algorithm for registration and answers. This section contains information customizing certain KBA user experiences.

F.5.1 Answer Logic Phonetics Algorithms

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 7.10, "Customizing English Abbreviations and Equivalences."

The phonetics algorithm is only supported in English.

For information on customization for locales, see Section 7.11, "Customizing Abbreviations and Equivalences for Locales."

F.5.2 Keyboard Fat Fingering

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.

F.5.3 Adding Abbreviations and Equivalences for Answer Logic

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 7.11, "Customizing Abbreviations and Equivalences for Locales."

F.5.4 Adding Registration Questions

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."

For information on adding registration questions, refer to Section 7.5.3, "Creating a New Question."