on 02-15-2013 8:19 AM
When we send the message from the XI Runtime Workbench -> Component Monitoring -> Integration Engine -> Test Message.
<?xml version="1.0" encoding="UTF-8"?><REGIONS>-<REGION><BLAND>04</BLAND><BEZEI>Республика Алтай</BEZEI></REGION></REGIONS>
In a message has Russian text. In the recipient system message comes, but Russian text are replaced with ???????????? symbols.
Massage in sxi_monitor
Payloads
<?xml version="1.0" encoding="UTF-8" ?>
<REGIONS>
<REGION>
<BLAND>04</BLAND>
<BEZEI>?????????? ?????</BEZEI>
</REGION>
</REGIONS>
Please tell me where to configure the encoding.
Installed PI 7.1
Hi Rinaz,
You dont mention which adapter are you working. Check this document http://scn.sap.com/docs/DOC-16138
Also you should check Nabendu Sen's answer in this thread: http://scn.sap.com/message/13735916#13735916
Regards.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
пишы по русски
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Anand,
Thanks for the reply.
but...
This problem occurs only when you send a message from RWB. If we send the message from the system, it goes through a scenario without error encoding.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
We too have encountered the encoding problem while using Celtic characters when sending test data via RWB.
For testing I suggest you use some file sender channel and use sample file in such a way that encoding is preserved (instead of direct copy pasting).
It may not be necessary that source is sending the file in UTF-8 format. Mostly it is ISO-8859-1/2/3 etc for European chars.
Hi Rinaz,
We stopped using RWB and triggered message for testing directly from source (proxy in our case).
Whenever there is encoding issue it is better to avoid test tab as we do not know, for certain, which encoding the data is in, while copying it from the files.
Interestingly, our issue was resolved by keeping transfer mode and data mode both in text mode (instead of binary) and encoding was kept blank. XI automatically assigned ISO-8859-1 encoding while transferring the data.
regards,
Anirudh.
Hi Rinaz,
You can configure encoding in the sender channel. To find the various unicode refer to the link below.
http://docs.oracle.com/javase/1.5.0/docs/guide/intl/encoding.doc.html
I have used IBM866 earlier for russian characters.
Thanks
Anand
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
81 | |
25 | |
12 | |
9 | |
7 | |
6 | |
5 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.