You must set up Build Forge components to support international
data.
Procedure
- Configure web browsers.
- Set the language.
- Be sure that the correct fonts are installed.
- Configure agent hosts to use the UTF-8 character set.
On Windows, use the chcp command to check
the code page:
> chcp
On UNIX or Linux,
use the following command to check the locale and character set:
locale
You
should see values that designate your language and character set.
The following example is from a Solaris system where US English is
the language and UTF-8 is the character set:
LANG=en_US.UTF-8
LC_CTYPE="en_US.UTF-8"
- Configure databases to use the UTF-8 character set and
fonts that support international data.
- DB2:
- Set the codeset and territory. Example: CREATE DATABASE USING
CODESET UTF-8 TERRITORY US (or select the appropriate codeset and
territory in Control Center).
- Set the DB2CODEPAGE environment variable on the management console
computer to 1208.
On Windows, use the command:
set
DB2CODEPAGE=1208
On UNIX or Linux, use the command:
export
DB2CODEPAGE=1208
If an existing database has data in it that you need to migrate
to UTF-8, the following document can help: http://publib.boulder.ibm.com/infocenter/db2luw/v9/index.jsp?topic=/com.ibm.db2.udb.admin.doc/doc/t0024033.htm
- Microsoft SQL Server (for use with Management Console on
Windows only): No support for international data. Microsoft
SQL Server uses UCS-2 for storing Unicode data and does not support
UTF-8.
- MySQL: Set the server character set and collation. If your
installation of MySQL does not currently support international data,
you can recompile it from source and use ./configure -–with-charset=utf8
-–with-collation=utf8_bin. The Build Forge engine will not
start if this support is not configured.
- Oracle: Set the character set to UTF8 - Unicode
3.0 on the instance when you install it. In the Database
Configuration Assistant, the setting is made on the Initialization
Parameters step on the Character Sets tab. If you use the command
line, set the character set to AL32UTF8.
- (Optional) Configure messages for the Build Catalyst feature.
On Microsoft® Windows® platforms, Build Catalyst messages
are displayed in the correct translation automatically.
To
view these messages on UNIX and Linux platforms, set the NLSPATH environment
variable to the following value:
/opt/rational/buildforge/buildcatalyst/lib/nls/%L/utf8/%N.cat:$NLSPATH
where:
- %L substitutes the value of the LANG environment variable
- %N substitutes the value of the name parameter passed to catopen(3C)
Alternatively, you can explicitly specify the translation.
The following value is for the ja_JP translation:
/opt/rational/buildforge/buildcatalyst/lib/nls/ja_JP/utf8/%N.cat:$NLSPATH