Support Article
German Special Character Problem
SA-6538
Summary
A specific Service of the PRPC system is called from external system and a string with German Special Character is sent into the PRPC system. We find this string is in proper format (with proper German Character) in the Tracer. But the same string once displayed on portal becomes distorted for the German characters.
Error Messages
N/A
Steps to Reproduce
Run the Service with the Service Request XML along with the Correlation ID.
Trace the activity where the 'German Special Character' string is being set.
Go back to the portal where this specific value is displayed.
Root Cause
German characters were not being shown properly in UI due to charset encoding issue.
Resolution
Issue is resolved by following local change:
Set charset encoding in web.xml and redeploy the war/ear file and restart application server.
<servlet>
<servlet-name>WebHTTPService</servlet-name>
<display-name>WebHTTPService</display-name>
<description>HTTP interface to PegaRULES, using internal authentication</description>
<servlet-class>com.pega.pegarules.internal.web.servlet.WebStandardBoot</servlet-class>
<init-param>
<param-name>PegaEtierClass</param-name>
<!--param-value>com.pega.pegarules.services.http.HTTPService</param-value-->
<param-value>com.pega.pegarules.integration.engine.internal.services.http.HTTPService</param-value>
</init-param>
<init-param>
<param-name>CharacterEncoding</param-name>
<param-value></param-value>
</init-param>
<!-- Indicate that R-S-HTTP never handles static content-->
<init-param>
<param-name>HasStaticContent</param-name>
<param-value>false</param-value>
</init-param>
</servlet>
Published January 31, 2016 - Updated October 8, 2020
Have a question? Get answers now.
Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.