Copyright © TIBCO Software Inc. All Rights Reserved
Copyright © TIBCO Software Inc. All Rights Reserved


Chapter 5 Advanced Topics : Internationalization

Internationalization
This section discusses internationalization. You learn about the following topics:
Introduction
TIBCO products can store, process, display and transmit data in multiple character sets including Latin-1, Korean, Japanese, Chinese, and so on. To support this, encoding is set as follows:
This wireformat encoding is called TIBCO Messaging Encoding and is determined by the encoding property of the administration domain in which the TIBCO application is running. Having one encoding per administration domain ensures that all TIBCO products in the administration domain use the same encoding to communicate.
Design-Time Encoding vs. Runtime Encoding
At design-time, you specify a TIBCO messaging encoding for a project. This encoding is used when the project is running in debug mode, or if you run it as a legacy project using a local repository (that is, exported as .dat file).
After the project has become a deployed application in TIBCO Administrator, the administration domain encoding supersedes the project-level encoding. This assures all TIBCO products working in the domain use the same wireformat encoding to communicate.
When an enterprise archive file is loaded, the design-time encoding is verified to be compatible with the domain encoding.
If a .ear file created using UTF-8 is deployed in a non-EMS domain, it gives a validation error and prompts the user to change the parameters values repo.encoding and tibcoadmin.client.encoding of the .tra file for the TIBCO Administator. There is no such issue in the EMS domain that uses ISO 8859 - 1.
Setting Encoding for an Administration Domain
The encoding for an administration domain is set during domain creation. You can create multiple administration domains on the same machine, each using a different encoding.
For the encoding:
Default Encoding
When you install an administration server and create an administration domain, the default encoding used for the domain is ISO8859-1 (Latin-1). The value is used for different properties of which three are in the tibcoadmin_domain.tra file:
tibcoadmin.client.encoding—encoding that is used to encode the HTML that displays the TIBCO Administrator GUI.
file.encoding—encoding of the tibcoadmin_domain.tra file contents.
repo.encoding—TIBCO Messaging encoding (discussed in the previous section). This encoding used by TIBCO Administrator and other TIBCO products in the domain to communicate.
-character_encoding—used by the TIBCO Hawk agent. The property is defined in the hawkagent.cfg file.
Changing Encoding for a Domain
In some situations, it may be necessary to choose UTF-8 as the encoding for all these properties. TIBCO Administrator stores encoding information per domain in two files. One is the domain’s .tra configuration file used to launch TIBCO Administrator, and the other is the configuration file used by the TIBCO Hawk agent.
For example, to change the encoding for a domain called myDomain:
1.
Change directory to TIBCO_ADMIN_DOMAIN_HOME\domain-name\bin.
2.
Using a text editor, open the tibcoadmin_myDomain.tra file.
3.
Change the tibcoadmin.client.encoding entry to UTF-8.
4.
Change the repo.encoding entry to UTF-8.
5.
6.
Change directory to TIBCO_TRA_DOMAIN_HOME\domain-name.
7.
8.
Change the -character_encoding entry to UTF-8.
9.
The client.encoding value can be any valid encoding value. It is used to enforce the encoding of the contents pushed to the browser. The repo.encoding value is used as TIBCO Rendezvous encoding and only UTF-8 and ISO8859-1 are supported.
If this domain has a secondary server or if other machines join this domain, you must apply the same changes on each secondary server and machine.
Changing Selected Properties
In some situations, you may wish to change the value of one, but not all properties. For example, if you are going to use aeXml as the message format, you must change repo.encoding to UTF-8 even if you are actually using ASCII characters. If you are using a .tra file that uses non-Latin1 characters, you must change file.encoding to UTF-8.
You can edit individual properties in the tibcoadmin_domain-name.tra file.
The following table shows some example for which project content should be used with what TIBCO Messaging encoding.
Users and Passwords with Double-Byte Characters
You can create users and assign passwords with double-byte characters if you configure the administration domain to use UTF-8.

Copyright © TIBCO Software Inc. All Rights Reserved
Copyright © TIBCO Software Inc. All Rights Reserved