Parsing XML issues with Special Characters
We are trying to parse an xml in Pega which has some tags with values having special characters like in-één ABCD. While parsing this tag the parse xml adds some unknown characters like in-����n ABCD. Is there a way by which we can remove this encoding in parse-xml?
***Updated by moderator: Lochan to close post***
This post has been archived for educational purposes. Contents and links will no longer be updated. If you have the same/similar question, please write a new post.
Accepted Solution
Cognizant Technology Solutions
IN
Indeed it was with the file encoding parameter in the JVM settings,Once it was changed from the admin console (since we run on weblogic), the parsing went fine, Thanks John for the quick and helpful insight on this.
Updated: 13 Jul 2015 11:52 EDT
Pegasystems Inc.
GB
Hi Anoojit,
Can you post your PRPC version and also check your PRSYSMGMT for the JVM setting "file.encoding" - it is set to UTF-8 or something else ?
Thanks !
John
Cognizant Technology Solutions
IN
Hi John,
Thanks for the prompt response. The version of PRPC is 7.1.7 and indeed the file.encoding in the system is set to ISO646-US. how can I change this to UTF-8?
Pegasystems Inc.
GB
Hi Anoojit,
No worries - the setting 'file.encoding' is actually a JVM ("-Dfile.encoding") argument - SMA just shows what it is set to : you can alter this value from at the Application-Server level - on Tomcat this is usually done in the 'setenv.bat' (or 'setenv.sh' on *nix) in the JAVA_OPTS variable:
Here's an example from a test system I have here:
set JAVA_OPTS=-Djava.awt.headless=true -Xms700M -Xmx1024M -XX:PermSize=64M -XX:MaxPermSize=384M -Xloggc:gc.log -Dfile.encoding=utf-8
On other App Servers - you can usually do from from the 'admin' console - change the JVM startup options.
You will need to restart the JVM for this option to be changed - then re-check in PRSYSMGMT and make sure it shows up.
If you still have the issue after making this change - let us know - maybe there is something else in-play here as well.
Thanks,
John
Accepted Solution
Cognizant Technology Solutions
IN
Indeed it was with the file encoding parameter in the JVM settings,Once it was changed from the admin console (since we run on weblogic), the parsing went fine, Thanks John for the quick and helpful insight on this.
Pegasystems Inc.
GB
Great - glad it worked out ! When you get chance - can you mark the question as 'answered' - so others can see the question and answer together when searching the forum in the future.
Cheers !
John