Siebel Outbound Rest API Is Not Retaining Japanese Kanji Characters In The JSON Message Going Out From The Tomcat Application Container
(Doc ID 2626024.1)
Last updated on FEBRUARY 01, 2023
Applies to:
Siebel CRM - Version 19.9 and laterInformation in this document applies to any platform.
Symptoms
When using Siebel outbound rest call to send a message with Japanese characters, the SiebelMessage and Siebel XML request shows proper Japanese text in all the XML tags. However, during the Siebel PS to JSON conversion at the SES applicationcontainer (Tomcat) layer, the Japanese text is not handled properly, it shows up as question marks instead of actual Japanese characters.
For example, the siebeljbs_1.log shows the following for a particular field from Siebel which has Japanese characters:
"description": "?????????????????Question Comments????",
The behaviour occurs as follows:
1. Set up Siebel Outbound REST for Mobile integrations.
2. Use Siebel to send outbound REST with English character, this all works fine.
3. Use Siebel to send outbound REST with Japanese character, the Japanese characters are not handled properly at the PS to JSON conversion. The JSON text is appearing as ?????????? instead of Japanese text.
Changes
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
Symptoms |
Changes |
Cause |
Solution |
References |