This topic describes the globalization features for Common Auditing and Reporting Service.
This section contains the following topics: v “Language support overview”
v “Installing language support packages” on page 18 v “Uninstalling language support packages” on page 19 v “Locale environment variables” on page 19
v “Message catalogs” on page 20
v “Text encoding (code set) support” on page 21
Attention: Review the globalization section in the IBM Security Access Manager for
Web Release Notes or Technotes in the support knowledge database for any
language-specific limitations or restrictions.
Language support overview
The Common Auditing and Reporting Service software is translated into the following languages: v Brazilian Portuguese v Czech v Chinese (Simplified) v Chinese (Traditional) v French v German v Hungarian v Italian v Japanese v Korean v Polish v Spanish v Russian Note:
1. The installation wizard uses your language of choice, without installing the language pack.
2. The installation wizards and the Windows native installation utility do not support the bidirectional languages (for example, Arabic and Hebrew).
The translations for these languages are provided as language support packages on the IBM Security Access Manager for Web Version 7.0 DVD. To obtain language support for Common Auditing and Reporting Service, you must install the language support package for that product. Each language is a separately installable product installation image.
You must install the language package after installing the Common Auditing Service components but before configuring them. If you do not install the language support package, the associated product displays all text in English.
If language support is installed and you upgrade the product, you must also install the corresponding language support product, if one exists. If you do not install the language support after upgrading, the associated product might display some fields and messages in English.
Installing language support packages
To install language support packages for Security Access Manager, follow these steps:
Procedure
1. Log on as root or as an administrative user.
2. Insert or mount the IBM Security Access Manager for Web Version 7.0 DVD for the appropriate operating system, and change to the root directory where the DVD is located.
3. Ensure that IBM Java Runtime 1.6, provided with Security Access Manager, is installed for your particular operating system. For instructions, see the IBM
Security Access Manager for Web Installation Guide.
The language pack message files, by language, for IBM Java Runtime 1.6 include: Java6.msg.Ja_JP Java6.msg.Zh_CN Java6.msg.Zh_TW Java6.msg.ja_JP Java6.msg.ko_KR Java6.msg.zh_CN Java6.msg.zh_TW
4. Depending on the component that you want to install, run one or more of the following setup scripts.
v To install with Launchpad, select the scripts for the required components.
Note:
a. Scripts are used for AIX, Linux, and Solaris operating systems; batch files (.bat extension) are used for Windows operating systems. b. If you issue a script without specifying the jre_path, you must ensure
that the Java executable program is part of the PATH statement. Otherwise, issue the script that specifies the jre_path as follows:
language_package jre_path
To install the language package for Common Auditing and Reporting Service, enter the following command:
install_cars_lp /usr/bin
where install_cars_lp installs the language packages for Common Auditing and Reporting Service, and /usr/bin is the path to the JRE. v To install in console mode, complete the following steps:
v Ensure that the IBM Java Runtime 1.6 is available in the command execution path (or prefix the command with the JRE directory.) v Run the following command:
java -jar language_package.jar run -console
carslp.jar
Installs the language packages for Common Auditing and Reporting Service.
5. Click Next to begin installation. The Software License Agreement window is displayed.
6. To accept the license agreement, select the I accept check box to accept the terms.
7. Click Next to display a dialog that shows a list of the languages. 8. Select the language packages that you want to install.
9. Click Next to display a dialog that shows the location and features of the languages that you selected.
10. Click Next to accept the languages selected.
The installation wizard validates that sufficient disk space is available. 11. Click Next to install the languages that you selected.
12. After installation for the language pack completes successfully, click Finish to close the wizard and restart your system.
Uninstalling language support packages
Uninstall the language packs if you no longer need the language support for your environment.
Procedure
1. Change to one of the following directories:
AIX®, Linux, and Solaris operating systems:
/opt/IBM/Tivoli/CommonAuditService/CARSLP/lp_uninst
Windows operating systems:
C:\Program Files\IBM\Tivoli\CommonAuditService\CARSLP\lp_uninst
2. Uninstall the language support packages with the following command:
AIX, Linux, and Solaris operating systems:
jre_path/java -jar cars_lp_uninstall.jar
Windows operating systems:
jre_path\java -jar cars_lp_uninstall.jar
where jre_path is the path where the Java executable program is located. If the Java executable program is in the path, you do not have to specify jre_path.
Locale environment variables
As with most current operating systems, localized behavior is obtained by specifying the required locale. You set the LANG environment variable to the required locale name as specified by POSIX, X/Open, or other open systems standards.
Note: If you are in a Windows environment, you can alternatively modify the
language setting in the Regional Settings of the Control Panel.
If you specify the LANG environment variable and modify the regional settings, the LANG environment variable overrides this regional setting.
As specified by open systems standards, other environment variables override LANG for some or all locale categories. These overriding variables include the following variables: v LC_COLLATE v LC_CTYPE v LC_MONETARY v LC_NUMERIC v LC_TIME v LC_MESSAGES v LC_ALL
If any of the previous variables are set, you must remove their setting for the LANG variable to have full effect.
LANG variable on AIX, Linux, or Solaris systems
Most AIX, Linux, and Solaris operating systems use the LANG variable to specify the required locale. Different AIX, Linux, and Solaris operating systems require different locale names to specify the same language. Ensure that you use a value for LANG that is supported by the AIX, Linux, or Solaris operating system that you are using.
To obtain the locale names for your AIX, Linux, or Solaris operating system, enter the following command:
locale –a
LANG variable on Windows systems
Most Windows operating systems do not use the LANG environment variable. However, you can use LANG to determine the required language. To do so, set the LANG environment variable to the canonical locale name based on the ISO
language or territory codes without a code set suffix. For example: v fris the locale for standard French
v jais the locale for Japanese
v pt_BRis the locale for Brazilian Portuguese v Cis the locale for English in C locale
Using locale variants
Although Security Access Manager software currently provides only one translated version for each language, you can use a preferred locale variant, and Security Access Manager finds the corresponding language translation. For example, Security Access Manager provides one translation for French, but each of the following locale settings finds the appropriate translation:
v fris the locale name for standard French v fr_FRis the locale name for French in France v fr_CAis the locale name for French in Canada v fr_CHis the locale name for French in Switzerland
Message catalogs
Message catalogs are typically installed in a /msg subdirectory and each of these message catalogs is installed under a language-specific subdirectory. For example, the Security Access Manager base components use the following directories: v On AIX, Linux, and Solaris operating systems:
/opt/PolicyDirector/nls/msg/locale v On Windows operating systems:
install_dir/nls/msg/locale
Other Security Access Manager components use similar directories for their message catalogs.
Security Access Manager recognizes variations in AIX, Linux, or Solaris locale names and is typically able to map the specified value to the appropriate message catalog.
The NLSPATH environment variable is used to find the appropriate message catalog directory, as specified by open systems standards. For example, if the message catalogs are in /opt/PolicyDirector/nls/msg, the NLSPATH variable is set to:
/opt/PolicyDirector/nls/msg/%L/%N.cat:/opt/PolicyDirector/nls/msg/%L/%N
Note: For Windows, use a semicolon (;) instead of a (:) as the separator. For example:
C:\Program Files\PolicyDirector\nls\msg\%L\%N.cat;C:\Program Files\PolicyDirector\nls\msg\%L\%N
The %L directive is expanded to the message catalog directory that most closely matches the current user language selection. Also, %N.cat expands to the required message catalog.
If a message catalog is not found for the required language, the English C message catalogs are used.
For example, suppose that you specify the AIX locale for German in Switzerland as follows:
LANG=De_CH.IBM-850
The %L directive is expanded in the following order to locate the specified locale: 1. de_CH
2. de 3. C
Because Security Access Manager does not provide a German in Switzerland language package, de_CH is not found. If the Security Access Manager German language package is installed, de is used. Otherwise, the default locale C is used, causing text to be displayed in English.
Text encoding (code set) support
Different operating systems often encode text in different ways. For example, Windows systems use SJIS (code page 932) for Japanese text, but AIX, Linux, or Solaris operating system often use eucJP.
In addition, you can provide multiple locales for the same language. By doing so, you can use different code sets for the same language on the same machine. Providing multiple locales for the same language can cause problems in one of the following situations:
v Text is moved from system to system.
Security Access Manager addresses these problems by using Unicode and UTF-8 (the multibyte form of Unicode) as the internal canonical representation for text.
Message catalogs are encoded by using UTF-8, and the text is converted to the locale encoding before being presented to the user. In this way, the same French message catalog files can be used to support various Latin 1 code sets, such as: v ISO8859-1
v Microsoft 1252 v IBM PC 850 v IBM MVS™1047
UTF-8 is also used to achieve text interoperability. For example, Common Object Request Broker Architecture (CORBA) strings are transmitted as UTF-8. Doing so enables remote management within a heterogeneous network in which local text encoding can vary. For example, Japanese file names can be manipulated on Japanese PC endpoints from a desktop that executes in the AIX Japanese EUC locale.
Text interoperability across the secure domain is also achieved by storing strings as UTF-8 within the object database. Strings are converted to the local encoding for viewing and manipulation by applications that are executing on different operating system code sets.
Location of code set files
Interoperability across your secure domain depends on code set files, which are used to complete a UTF-8 conversion and other types of encoding-specific text processing.
These files are installed in the following directories: v On AIX, Linux, and Solaris operating systems:
/opt/PolicyDirector/nls/TIS v On Windows operating systems: