Adding Localization Resources for a Newly Supported Language

This section describes how to add and customize files that contain Access Manager Console authentication interface messages. It then explains how to add and customize the Access Manager Console user interface messages. Access Manager detects the client language that uses information in the HTTP request from the browser. Hence, to add L10n resources for a new language, the only requirement is to follow the Access Manager file name conventions and directory organization.

Localizing Authentication Interface Files

When providing authentication interfaces for localized environments, a separate directory for each language that contains customized XML files must be created. For each language, a subdirectory structure similar to the Access Manager information tree must also be created. The subdirectory starts from the authentication interface base directory, that is, AM_INS/web-src/services/config/auth/default_locale/

The first directory structure is needed to receive the new authentication interface file. This directory structure is then populated with existing interface files. Finally, these files are customized.

For instructions on how to localize authentication interface files for a new language, see Hands-on Lab Format.

The following procedures explain what must be done to localize authentication interface files.

To Create a Subdirectory Structure for the AMRoot Realm and All Its Sub-realms

1. Open a terminal window (if necessary) on a system where Access Manager is installed.

2. Navigate to the authentication interface base directory.

3. Create a subdirectory structure.

4. Change to the created subdirectory.

To Populate the Created Subdirectory With Desired Interface Files

1. Copy the default Login.jsp file to the current directory.

2. Copy the default Logout.jsp file to the current directory.

3. Copy the default LDAP.xml file to the current directory.

To Customize Previously Copied Files

1. Open the files in a text editor.

2. Insert the new strings.

3. Save the files.

Localizing the Access Manager Administration Console

To add language support to the Access Manager Administration Console, a new Java properties file for the desired module must be created. For example:

Example 3 Adding Language Support for the Policy Module for the Dutch Language

1. Change to the AM_INS/locale directory.

2. Copy the amPolicy.properties file to a new amPolicy_nl.properties file.

3. Modify the created amPolicy_nl.properties file.

4. Save the file.

5. Restart the web container.

Another example is the customization of the copyright notice displayed at the bottom of the Access Manager Administration Console Login page.

Example 4 Customizing the Copyright Notice

1. Change to the AM_INS/locale directory.

2. Copy the amAuthUI.properties file to a new amAuthUI_nl.properties file.

3. Modify the copyright.notice key in the created amAuthUI_nl.properties file.

4. Save the file.

5. Restart the web container.

After adding support for a new locale to Access Manager, newly added language software resources must be customized as described in the following section.