Whats the deal with encoding and padding of char.n fields when sending messages to adpaters like SAP ?
Article ID: KB0089007
Updated On:
| Products | Versions |
|---|---|
| TIBCO IntegrationManager | - |
| Not Applicable | - |
Description
Resolution:
1. IN IM4.5,the default repo encoding is changed from "UTF-8" to "ISO8859-1" for performance benefits.While reading the repo, IM uses this encoding. So if you wish to use UTF-8, you should set it explicitly. IM picks up the encoding from the repo.
2. If the encoding is "ISO8859-1[Latin-1]" or "cp1252[RV's defaultencoding], then padding is added when the data size is lesser than the type size. i.e. if the field type is char.2 and if the data is "a" then two characters are sent with the second character being 0. This is compatible with SDK.
3.For any other encoding no padding is added. This is compatible with SDK. Ex. If the encoding is UTF-8 and if the field type is char.2 and if the data is "a" then only one character is sent.
4. There is a new property 'Config.Primary.Compatibility.StrictBinding' available. By default it is set to false.
If it's false, and you are trying to send 4 characters in char.2 field, then the data will be truncated and only 2 characters will be sent, no matter what encoding
If it's true, and you are trying to send 4 characters in char.2 field, all 4 characters will be sent, no matter what encoding. A warning message is thrown.
1. IN IM4.5,the default repo encoding is changed from "UTF-8" to "ISO8859-1" for performance benefits.While reading the repo, IM uses this encoding. So if you wish to use UTF-8, you should set it explicitly. IM picks up the encoding from the repo.
2. If the encoding is "ISO8859-1[Latin-1]" or "cp1252[RV's defaultencoding], then padding is added when the data size is lesser than the type size. i.e. if the field type is char.2 and if the data is "a" then two characters are sent with the second character being 0. This is compatible with SDK.
3.For any other encoding no padding is added. This is compatible with SDK. Ex. If the encoding is UTF-8 and if the field type is char.2 and if the data is "a" then only one character is sent.
4. There is a new property 'Config.Primary.Compatibility.StrictBinding' available. By default it is set to false.
If it's false, and you are trying to send 4 characters in char.2 field, then the data will be truncated and only 2 characters will be sent, no matter what encoding
If it's true, and you are trying to send 4 characters in char.2 field, all 4 characters will be sent, no matter what encoding. A warning message is thrown.
Issue/Introduction
Whats the deal with encoding and padding of char.n fields when sending messages to adpaters like SAP ?
Feedback
Yes
No
Powered by
