Character Encoding used for the communication between TIBCO product components in this project at design time (debug mode), or if the project is running as a legacy local file-based project. The communication transport could be either TIBCO Rendezvous or TIBCO Enterprise Message Service.
User have two choices:
— ISO8859-1 (Latin-1)—Preferred encoding for projects that deal only with English and other Western European languages that belong to the ISO Latin-1 character set. If this encoding is used for languages that do not belong to the Latin-1 character set (such as Japanese, Arabic, etc.), data loss may result.
— UTF-8—Preferred encoding for projects dealing with languages not belonging to the Latin-1 character set. This includes most languages except for English and other western European languages.
- How can user set preferred encoding?
At design time, the message encoding property can be set when creating a new project. In the Save Project dialog, choose either ISO8859-1 or UTF-8 in the TIBCO Messaging Encoding option list.
After the project is deployed, the messaging encoding is determined by the encoding property of the TIBCO Administrator domain. This property is set when the domain is created. ISO8859-1 and UTF-8 are the two supported character encoding options. The messaging encoding set for the domain overrides any encoding set for a project.
- Can we change the encoding of any existing application?
The easiest way to change the default encoding for the bw application add the below property in application tra file.
java.property.file.encoding=UTF-8
- What's the default encoding used for EMS communication?
- For EMS, BW uses UTF-8 as a default encoding. The JMS messages are received or sent in UTF-8 format. If user wants to change the default setting, user needs to add the following java property in deployed TRA file.
java.property.file.encoding=UTF-8
- How can we set XML encoding in BW?
User can set encoding in edit->preferences-> XML-Editing tab, it defined the xml encoding when user create and edit xml in designer with xml tools.
- Can we change the encoding for any specific activity in a TIBCO ActiveMatrix BusinessWorks application?
TIBCO also allow changing the encoding at activity level for different relevant palettes, please refer to the TIBCO ActiveMatrix BusinessWorks™ Palette Reference doc for more information.
Examples:
- For Http, the encoding is set on Http palettes (ex: HTTP Receiver -> Configuration -> Default Encoding).
- For SendHTTP resource user can set the charset in the content-type header ex: Content-Type: application/json;charset=UTF-8
- Whether users are allowed to set the encoding for TIBCO ActiveMatrix BusinessWorks application logs?
Yes, user can also specify the character encoding of the TIBCO ActiveMatrix BusinessWorks log file by using the log.file.encoding property. If this property is not specified, the default encoding of the Java Virtual Machine used by the process engine is used.