| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Changing encoding of a file inside broker |
« View previous topic :: View next topic » |
| Author |
Message
|
| maven |
 Posted: Wed Feb 25, 2009 12:41 am Post subject: Changing encoding of a file inside broker |
 |
|
Novice
Joined: 03 Jun 2007
Posts: 15
|
hi,
I wanted to change the enoding of a file from UTF-8 to ANSI inside broker.
Source system sends xml file with UTF-8 encoding, broker converts the message to flatfile and sends to the target system.
Target system has constraint while receiving foreign character message in UTF-8 format and reads it in double bye and it is a product limitation. So i wanted to send the message to target system having encoding as ANSI.
I tried parsing the messages again CCSID 819 in broker but the encoding doesnt change.
Can u please suggest me regarding this issue. |
|
| Back to top |
|
 |
| MQEnthu |
| Posted: Wed Feb 25, 2009 1:06 am Post subject: |
|
|
Partisan
Joined: 06 Oct 2008
Posts: 329
Location: India
|
|
| Back to top |
|
|
| kimbert |
| Posted: Wed Feb 25, 2009 1:46 am Post subject: |
|
|
Jedi Council
Joined: 29 Jul 2003
Posts: 5542
Location: Southampton
|
|
| Back to top |
|
|
| rekarm01 |
| Posted: Wed Feb 25, 2009 3:18 am Post subject: Re: Changing encoding of a file inside broker |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 1415
|
| maven wrote: |
I wanted to change the encoding of a file from UTF-8 to ANSI inside broker.
Source system sends xml file with UTF-8 encoding, broker converts the message to flatfile and sends to the target system.
Target system has constraint while receiving foreign character message in UTF-8 format and reads it in double bye and it is a product limitation. So i wanted to send the message to target system having encoding as ANSI. |
It's not clear what "ANSI" is supposed to mean here, but it presumably refers to a "single byte character set".
If the source system uses a single byte character set to generate the xml message, (and converts the message to UTF-8 before sending it to the broker), then the broker can safely convert the message back to the original character set.
If the source system does not use a single byte character set to generate the XML message, then the broker would have to handle non-convertible characters some other way, before converting the message to a single byte character set.
Which character set does the source system use to generate the message (or which character sets can the source system use)?
Which character set is the target system expecting, (or which character sets can the target system accept)?
| maven wrote: |
| I tried parsing the message again CCSID 819 in broker but the encoding doesn't change. |
More details would help here. |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
|
|
