Skip Headers
Oracle® Access Manager Installation Guide
10g (
Go to Documentation Home
Go to Book List
Book List
Go to Index
Go to Feedback page
Contact Us


12 Installing Language Packs Independently

This chapter describes how to add one or more optional Language Packs after installing and setting up Oracle Access Manager components (or after upgrading from an earlier release). Topics include:

For an overview of languages, see the Oracle Access Manager Introduction and Chapter 3, "About Multi-Language Environments".

12.1 About Language Packs and Installation

Oracle provides the capability to localize Oracle Access Manager applications to display static data such as error messages and display names for tabs, panels, and attributes to users in their native language. The English language is always available, which requires no special installation or configuration. In addition, you can install Oracle-provided Language Packs and select a default Administrator language for Oracle Access Manager


Oracle Access Manager supports Latin1 and UTF-8 data, including multibyte languages such as Chinese, Japanese, and so on. Contact Oracle for information about specific Language Packs.

For each language that Oracle supports, one Language Pack installer is provided for the Identity System and one is provided for the Access System. Language Packs can be installed together with Oracle Access Manager components, as described in other chapters. However you may also install a Language Pack independently, after Oracle Access Manager installation and setup, as discussed in this chapter.

As discussed in Chapter 3, "About Multi-Language Environments" the installation directory you specify for the Language Pack must match the installation directory of the component with which it is to operate. For example:






In addition, if you install a Language Pack on Identity System components you must install the same language Pack on all Access System components.

During installation, a \langTag directory is created in the file system under the main Oracle Access Manager component's installation directory. For example, component_install_dir\identity|access\oblix\lang\langTag, where langTag represents specific language, such as English (en-us) or French (fr-fr). See "Installed Files" for an example.

A language entry is created for each installed language under the Oblix node in the LDAP directory as follows: obid=langTag, configDN, where configDN is the configuration DN in the directory.

The obnls.xml configuration file is updated for each component in \component_install_dir\identity|access\oblix\config\obnls.xml. Installed languages and entries in obnls.xml must match for each component. In the following sample obnls.xml file, installed languages include English, Arabic, Czech, Japanese, and simplified Chinese:

 <?xml version="1.0" encoding="UTF-8" ?> 
- <ParamsCtlg xmlns="" CtlgName="obnls.xml">

- <CompoundList xmlns="" ListName="">- <SimpleList>
  <NameValPair ParamName="default" Value="en-us" />   </SimpleList>
- <ValList xmlns="" ListName="languages">
<ValListMember Value="en-us" /> <ValListMember Value="ar-ar" /> <ValListMember Value="cs-cs" /> <ValListMember Value="ja-jp" /> <ValListMember Value="zh-CN" /> </ValList> - <ValNameList xmlns="" ListName="en-us"> <NameValPair ParamName="sortRulesFile" /> <NameValPair ParamName="dirPath" Value="en-us" /> </ValNameList> - <ValNameList xmlns="" ListName="ar-ar"> <NameValPair ParamName="sortRulesFile" /> <NameValPair ParamName="dirPath" Value="ar-ar" /> </ValNameList> - <ValNameList xmlns="" ListName="cs-cs"> <NameValPair ParamName="sortRulesFile" /> <NameValPair ParamName="dirPath" Value="cs-cs" /> </ValNameList> - <ValNameList xmlns="" ListName="ja-jp"> <NameValPair ParamName="sortRulesFile" /> <NameValPair ParamName="dirPath" Value="ja-jp" /> </ValNameList> - <ValNameList xmlns="" ListName="zh-CN"> <NameValPair ParamName="sortRulesFile" /> <NameValPair ParamName="dirPath" Value="zh-CN" /> </ValNameList> - <!-- List of locales that require bidi support --> - <ValList xmlns="" ListName="bidiLanguages"> <ValListMember Value="he" /> <ValListMember Value="ar" /> <ValListMember Value="iw" /> </ValList> </CompoundList> </ParamsCtlg>

Task overview: Installing a Language Pack independently

  1. Run the Identity System Language Pack installer, as described in "Installing the Language Pack Independently", on each computer hosting an installed (or upgraded) Identity Server and an installed WebPass.

  2. Confirm that the languages you installed are enabled, as described in "Confirming Language Status".

  3. Run the Access System Language Pack installer, as described in "Installing the Language Pack Independently" on each computer hosting an installed (or upgraded) Policy Manager, Access Server, and WebGate.

    Even though there are no user interfaces for the Access Server and WebGate, you need to install the same Language Packs for these components as you do for others.

  4. Confirm that the languages you installed are enabled, as described in "Confirming Language Status".

12.2 Language Pack Installation Considerations

Installing additional languages to enable multi-language functionality in Oracle Access Manager may be done either during or after installation of each component.

If you install a Policy Manager and WebGate in the same directory, you may then install a Language Pack in the same directory and both components will use it. This means that you do not need to install a Language Pack for the Policy Manager then repeat the process for a WebGate that resides in the same directory.


Do not install the Policy Manager, then install a Language Pack, then install a WebGate in the same directory. Otherwise, the appropriate language entries will not appear in the WebGate obnls.xml file.

On UNIX systems, you must ensure that the Language Pack has execute permissions before launching the installer. For example:

     chmod +x "Oracle_Access_Manager10_1_4_3_0_FR_sparc-s2_LP_Identity_System"
     chmod +x "Oracle_Access_Manager10_1_4_3_0_FR_sparc-s2_LP_Access_System"

If you prefer to install the Language Pack silently while installing each Oracle Access Manager component, the Language Pack installer must reside in the same temporary directory as the component installer. See Chapter 3, "About Multi-Language Environments" and individual installation chapters in this guide for more information.

12.3 Language Pack Prerequisites Checklist

Before you begin installing the Language Pack independently, check the tasks in "Language Pack Prerequisites Checklist". It ensure they have been completed. Failure to complete prerequisites may adversely affect your Oracle Access Manager installation.

Table 12-1 Language Pack Installation Prerequisites Checklist

Checklist Language Pack Installation Prerequisites

Review and complete all prerequisites and requirements that apply to your environment, as described in Part I, "Installation Planning and Prerequisites"

Complete all activities in Part II, "Identity System Installation and Setup".

Complete all activities in Part III, "Access System Installation and Setup"

To install a Language Pack at the same time as the Oracle Access Manager component, move any Language Pack installation packages into the same directory as the component installation package and refer to the appropriate chapter in this guide.

12.4 Installing the Language Pack Independently

This procedure walks you through adding a Language Pack independently, after Oracle Access Manager component installation and setup.

To perform independent Language Pack installation

  1. Log in as a user with Administrator privileges.

  2. Locate and launch the installation package for the desired Language Pack and component and launch the installer.

    For example:

    • GUI Method, Windows




    • Console Method, UNIX.

      / Oracle_Access_Manager10_1_4_3_0_sparc-s2_langTag_Identity_System


      / Oracle_Access_Manager10_1_4_3_0_sparc-s2_langTag_Access_System

      where langTag refers to a specific language tag, such as FR (French).

      The Welcome screen appears.

  3. Click Next to dismiss the Welcome screen.

  4. Respond to the question about administrator rights based on your platform.

  5. Change the destination directory to match the main component for which this is being installed, then click Next.

    For example:


    You are informed that the Language Pack is being installed, which may take a few seconds. ReadMe information appears next.

  6. Review the ReadMe information, then click Next to dismiss it.

    A summary screen appears.

  7. Click Finish to complete this installation.

  8. Restart the service for which you just installed the Language Pack.

  9. Repeat the Language Pack installation for:

    • All WebPass components, using the Identity System Language Pack

    • All Access System components, using the Access System Language Pack

      • Policy Managers

      • Access Servers

      • WebGates

12.5 Installed Files

As discussed in Chapter 3, "About Multi-Language Environments", the \lang directory and the \lang\en-us and \lang\shared subdirectories are included with all installations. When you install additional languages, a \langTag subdirectory is created under \lang. It includes the same type of content as \en-us, only localized.

12.6 Confirming Language Status

Use the following procedure to confirm which languages are installed and enabled within Oracle Access Manager.

To confirm which languages are enabled

  1. Navigate to the Identity System Console, and log in as usual.


    where hostname refers to computer that hosts the Web server; port refers to the HTTP port number of the WebPass Web server instance; /identity/oblix connects to the Identity System Console.

  2. Click Identity System Console, select System Configuration, then click Server Settings.

  3. Click the Multi-Language link at the bottom of the page.

    The Manage Multiple Languages page appears showing which languages are currently installed and which are enabled.

  4. Click the box beside the languages you want to enable, then click the Enable button.

  5. Refresh the browser screen or reopen the browser.

    After installation, you must enable all the languages that you want to use, then configure the User, Group, or Org Manager applications to use the installed languages by entering display names (at the Object Class level) for attributes, tabs, and panels using the Identity System Console.

  6. See the following documentation for additional information: