I got remedy adapter running in Windows (with windows native lib), and had
problem when I send Arabic text (UTF-8 encoded). In Remedy client they see all the text characters as question marks (which means encoding of text is corrupted).
I tried to use “Language / Locale” in connection properties (which defines encoding at session level) but it seems it has no effect. I tried to use several including “ar_SA.ISO-8859-6”, “ISO-8859-6”, UTF-8.
Coincidently I found a workaround which worked in Windows, it is as following:
- Language/Locale is set to empty - Convert text encoding pub.string:stringToBytes (encoding=Cp1256) pub.string:bytesToString (encoding=autodetect) - Map the text to the create adapter service.
After this workaround in remedy client we can see the Arabic text correctly. I checked the text we are sending, it is Cp1256 encoded when mapped to create
Also I got remedy adapter running in Solaris (with Solaris native lib), and had the same problem the Arabic text I send is viewed as question marks in Remedy client. I tried the same workaround in Solaris but did not work using ISO_8859-6 as encoding.
Does anyone knows how the native lib of Remedy uses the encoding, is there any environmental variables I need to set in Solaris.
IS Version 6.5
IS Updates IS_6-5_SP1
OS Platform sparc
OS Version 5.8
Adapter Version 6.0
AR system version 6.3
AR platform sparc-sun-solaris2.9
Your help is appreciated