Sun[TM] Identity Manager 8.0 Deployment Overview |
Appendix B
Enabling InternationalizationThis appendix describes how to configure Identity Manager to use multiple languages or to display a language other than English.
Architectural Overview
The following catalog entries control how the product name is displayed:
PRODUCT_NAME=Identity Manager
LIGHTHOUSE_DISPLAY_NAME=[PRODUCT_NAME]
LIGHTHOUSE_TYPE_DISPLAY_NAME=[PRODUCT_NAME]
LIGHTHOUSE_DEFAULT_POLICY=Default [PRODUCT_NAME] Account Policy
Typical Entry
Messages are contained in key/text pairs and contain three parts:
- A text string, or key, that is an identifier used by the code to retrieve data. Do not translate this required component. This component is used in the product configuration, and acts as a placeholder for the translation.
- An equals (“=”) sign separating the key and text. This entry is required.
- A string containing data that is displayed when running the application. This entry is the translation, used in place of the key whenever the page is rendered in the browser.
Each line in the resource array contains two strings. Translate the second quoted string on each line.
Certain strings to be translated contain special codes for data that is inserted into the string when it is displayed. For example, if you have the following string to translate:
UI_USER_CONNECT={0}, connected at 100 mbs
the rendered version could appear as jfaux, connected at 100 mb
Translations typically appear inside a browser, so it is appropriate to add HTML tags to format the string, as shown below:
_FM_ACCOUNT_ID_HELP=<b>Account ID</b><br>Enter a name for this user. This field is required.
Enabling Support for Multiple LanguagesUse the instructions described in this section to enable multiple language support for Identity Manager.
Step One: Download and Install Localized Files
Before You Install
Perform the following tasks before you install localized files:
Refer to the documentation for these products for information about setting the locale.
Download Message Catalog Files
The Identity Manager software download website provides the following localized message catalogs. Download the appropriate message catalog jar file and place that file in the WEB-INF/lib directory.
Download the ZIP file to a temporary location. By default, the contents of the ZIP file are extracted to the FileName\IDM_8_0_l10n directory, where FileName matches the name of the downloaded file, minus the ZIP extension.
Zip File Contents
Every extracted ZIP file contains the following:
Additional translated publications might also be available.
Install Localized Files
Use the following steps to install localized files on your application server.
Step Two: Edit the Waveset.properties File
To edit the Waveset.properties file,
- Open the IdentityManagerInstallation/config/
Waveset.properties file with your editor of choice.- Change the Internationalization.enabled property to true.
- Save your changes and close the file.
- Either restart Identity Manager or click Reload Properties on the Debug pages available at the following location:
http://host:port/idm/debug.url
Maintaining ASCII Account IDs and Email Addresses During Anonymous Enrollment ProcessingBy default, Identity Manager’s anonymous enrollment processing generates values for accountId and emailAddress by using user-supplied first (firstName) and last names (lastName) as well as employeeId. Because anonymous enrollment processing can result in the inclusion of non-ASCII characters in email addresses and account IDs, international users must modify EndUserRuleLibrary rules so that Identity Manager maintains ASCII account IDs and email addresses during anonymous enrollment processing.
To maintain account ID and email address values in ASCII during anonymous enrollment processing, follow these two steps:
- Edit the following rules in the EndUserRuleLibrary as indicated in the following table:
- Edit EndUserAnonEnrollmentCompletionForm to remove the firstName and lastName arguments from calls to the getAccountId and getEmailAddress rules.