An app that we developed in RUI is working just fine in RBD preview mode (when on local server), but after we install the app on our remote server we get problems with (this we are suggesting) charset. We don't have a problem with displaying special (Croatian) characters. Problem occurs after calling web service, precisely, after trying to pass some data that user entered on the screen to the remote server. We deploy on WAS 7.0. Here is the error message, so please help with any ideas.
ERROR MESSAGE:
"EGL1546E The request could not be converted to a service call. The received request was '{"uri":"","queryParameters":{},"method":"POST","body":"{\"bindingName\":\"sbp0001CallService\",\"method\":\"klijentKomentar_function\",\"params\":{\"rPrijedlogKlijent\":{\"prijedlog\":1000,\"tipPrijedloga\":\"F\",\"maticni\":\"12345678000\",\"tipKlijenta\":\"\",\"naziv\":\"HOBÄ+ D.O.O.\"},\"akcija\":\"S\",\"tipKomentara\":\"OD\",\"tekstKomentara\":\"\"},\"EGL_PARAMETER_ORDER\":\"ulaz _return\",\"binding\":{\"type\":\"WebBinding\",\"interfacename\":\"sbut.servis.sbp0001CallService\",\"name\":\"sbp0001CallService\",\"wsdlLocation\":\"sbp0001CallService.wsdl\",\"wsdlService\":\"sbp0001CallServiceService\",\"wsdlPort\":\"Sbp0001CallService\",\"uri\":\"\"}}","headers":{"EGLSOAP":"sbutWeb","Content-Type":"application/json; charset=UTF-8"'. EGL0001I The error occurred in EGL Rich UI Proxy."
P.S. In deployed RUI handlers HTML source charset is UTF-8.

Still need Your help...

When testing the app with string containing Croatian characters in RBD Web Service Explorer (no RUI interface) i see all letters (entered and returned) are ok. What remote WAS returns becomes displayed well, as it is sent, but the problem, looks so, appears when going in the other direction, that is when starting the app and when RUI interface does the interpretation of the on screen entered text and forwards it to the web service.
It would be nice if someone had any idea what should we adjust/try to do to get good response, or the only solution is to write our own converter.
Thanks

Hello malabiljka,

You could try the solution I provide on the last reply of the discussion Re: Service data conversion problem when communicating with IBM i
Maybe it is somewhat similar and works for you.

Ortwin

Edited by: markevans on Aug 20, 2010 5:46 PM

Hi Ortwin,
I really appreciate Your help. While I was searching for the solution, before my EGL Café post, I came over Your problem and it did seem similar, but I'm not sure is this solution the one that I really need, so it would be great if You could help me clarify this - Here is my situation with the app, as simple as I can:
When starting the app we have some initial database data get and displayed on the RUI screen (with special and other characters included) with no problem.
The char transformation happens later, when we choose an onscreen action, example when we enter some characters in an textarea and push a button to call a web service to store this string. The chars that webservice function receives (some of them) as an input argument are transformed, they are not the ones entered in RUI textarea, and cannot be recognized as an valid input so we get an error.
On the other hand, if we approach the service (and server) through the 'RBD Web Service Explorer' and test the web service function this way, by directly inputting the same string (as did before through the RUI screen - the string entered in the textarea), the function is executed, transaction doesn't fall.
So, what do you think?
Hope I'm clear enough to let You have the big picture. If You need any more info, please tell. Thank You once again.
Best regards
Marijo

Hello Marijo,

Are you using the Dynamic Loader?

Ortwin

Yes, Ortwin, I'm using D.L. Could it be something with it?
Once again, thanks for your interest.
Marijo

Hello Marijo,

We also still have a Dynamic Loader issue concerning wrong conversion of characters.
In our case this is a low priority issue for we do not get errors, just wrong characters.

Maybe you can test your case without the DL and see if the problem disappears.

Anyway, I just asked IBM for the status on resolving the issue.

Ortwin

Good thing You asked them, Ortwin.
Thanks for Your help.
I,ll get back with more info if I manage to get some good news.
Best regards, have a nice day.
Marijo

Dear Ortwin,
Good news!!
It works now. We had our hour or two playing with the server atributes and made some adjustments similar to those in the response You got from IBM and now we have a big celebration. You are invited!
Best regards
Marijo

We encountered this problem again when we moved from RBD 8.5.1 to RBD 9.5.0.1.

 

This time the solution was to change the JVM codepage on WAS.

This can be done under Application servers > server1 > Process definition > Java Virtual Machine by setting the 'Generic JVM arguments' to '-Dclient.encoding.override=UTF-8'

 

Happy EGL-in',

Ortwin