Message encoding type supported by Apache RV module.
Article ID: KB0092810
Updated On:
| Products | Versions |
|---|---|
| TIBCO API Exchange | - |
| Not Applicable | - |
Description
Resolution:
Apache RV module supports only one type of encoding specified as the property below in the asg.properties file. The default value is UTF-8.
Apache RV module supports only one type of encoding specified as the property below in the asg.properties file. The default value is UTF-8.
# Enable RV channel to encode characters using specified encoding
tibco.clientVar.MessageEncoding=UTF-8
If the message flow is APIX <-> Apache (RV) <-> APIX <-> Target Service and the reply message from the target service is of Content-Type other than the specified value of the above property, then the response message is encoded incorrectly.
Example Scenarios
1). Message Encoding = utf-8, RV Channel encoding = utf-8 => There is no problem.
2). Message Encoding = iso-8859-1, RV Channel encoding = utf-8 => Latin characters in the message will not be broken.
3). Message Encoding = iso-8859-1, RV Channel encoding = iso-8859-1 => There is no problem with characters being limited to Latin.
Since Response encoding is dynamic and RV Channel encoding is static, i.e. RV Channel encoding is set once at Gateway engine start up, it is best to keep RV Channel encoding as utf-8 and require the incoming message to be always utf-8 encoded. Alternatively, the message flow can be changed to APIX <-> APIX (default http port) <-> Target Service, to completely eliminate the RV channel use. In this case, the above mentioned property does not kick in.
Issue/Introduction
Message encoding type supported by Apache RV module.
Environment
Product: TIBCO API Exchange
Version: ALL
OS: All Supported Operating Systems
--------------------
Additional Information
-
Feedback
Yes
No
Powered by
