Build Forge must be set up to support international
data if you intend to display international data in the Management Console.
- 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 Windows, use the chcp command to check the code
page:
> chcp
- All databases:
Typically support for international data is specified
when you create the database.
The fonts you intend to use to display
data must be installed. Support for the UTF-8 character set and an appropriate
collation must be configured.
Build Forge requires the use of international
data (UTF-8 character sets) with the exception of Microsoft SQL Server which
does not support UTF-8.
- 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 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.
- Sybase (for use with Management Console on Windows only): Before
creating any tables, configure the default character set to be utf8 and
the default sort order to be utf8bin. Consult the Sybase
documentation for your version for more details. If the database server has
data on it, follow directions for data migration to utf8.