Build Forge must be set up to support international data
in the Management Console.
Before you begin
- Web browsers:
- must have the language set
- must have the fonts you use to display data installed
- Agents
Build Forge recommends using the UTF-8 character
set on agent servers.
On UNIX/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"
- All databases:
Typically support for international data
is specified when you create the database; international data support
cannot be configured after database creation.
The fonts you
intend to use to display data must be installed on the database host
computer.
Build Forge requires the use of international
data (UTF-8 character sets).
- 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
- 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.