RSA Via Lifecycle and Governance - How to set up an environment to run WebServices with Turkish Characters
2 years ago
Originally Published: 2016-06-24
Article Number
000067810
Applies To
RSA Product Set: RSA Via Lifecycle and Governance (RSA Via L&G)
RSA Product/Service Type: Appliance
RSA Version/Condition: 7.0.0 P02
Platform: WildFly 8.2.0
 
Issue
When defining the CreateChangeRequest WebService API to create a change request, it fails on any Entitlements with Turkish characters.

See the following details of Request and Response.

Request.

<Changes>
<AccountChange>
<Operation>Add</Operation>
<Account>TCASOYDAN</Account>
<AccountCollector>ACC_COL_CashStation_RSA</AccountCollector>
<BusinessSource>CashStation-RSA</BusinessSource>
<ApplicationRole>Banka Bakiye Raporları Görüntüleme</ApplicationRole>
</AccountChange>
</Changes>



Response:

<html>
<head>
<title>Error</title>
</head>
<body><![CDATA[The change request could not be created. The application role could not be added to the account because the application role could not be retrieved. The application role 'Banka Bakiye Raporlar� G�r�nt�leme' could not be found for business source 'CashStation-RSA'. &lt;?xml version="1.0" encoding="UTF-8"?&gt;&lt;AccountChange&gt;
&lt;Operation&gt;Add&lt;/Operation&gt;
&lt;Account&gt;TCASOYDAN&lt;/Account&gt;
&lt;AccountCollector&gt;ACC_COL_CashStation_RSA&lt;/AccountCollector&gt;
&lt;BusinessSource&gt;CashStation-RSA&lt;/BusinessSource&gt;
&lt;ApplicationRole&gt;Banka Bakiye Raporlar� G�r�nt�leme&lt;/ApplicationRole&gt;
&lt;/AccountChange&gt;
Query String=cmd=createChangeRequest&token=ws31e8399c4c4e17bc6f%3A-3d5a4d4a%3A1550b843972%3A-7f230.07926415968157596&failOnViolation=true&password=]]></body>
</html>


As the above response, it could not understand the word of "Görüntüleme" with Turkish characters.
 

Tasks

 
Resolution
In general our WebServices work with all characters. It depends on how the WebService is being called.

As the above issue, need to make sure to set the correct charset/encoding from the application calling the WebService. It should use UTF-8 encoding.

Therefore, if using something like SoapUI, make sure that the encoding property is set to UTF-8, see screenshot as below, and then try again.

User-added image

The issue should be resolved.