| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| WBI/WMQ - Can it handle double byte data ? |
« View previous topic :: View next topic » |
| Author |
Message
|
| podowd |
 Posted: Fri Dec 02, 2005 1:39 pm Post subject: WBI/WMQ - Can it handle double byte data ? |
 |
|
Novice
Joined: 23 Sep 2004
Posts: 19
|
Hi,
We are looking to enhance our Middleware suite to enable applications from the Asian marketplace to trade transactions via our Middleware Hub (WBI version 5, WMQ version 5.3).
We are wondering if WBI and WMQ will be able to process double byte data as found in languages such as Japanese?
If it can, is it generally a case changes need to be made to existing queue manager/WBI flows or other components to cater specifically for double byte data? (From what I have read WBI stores everything internally in the flows as Unicode as does Java so that sounds like a good start).
We have channel exits on the Hub that we use for message tracking, we make a copy of all traffic and log to an Oracle database.
Typically sites talk to our middleware Hub using a Java adapter, we are looking to enhance the adapter to pass in data to the Hub as XML documents in UTF-8/UTF-16 format, format of the WMQ messages is MQRFH2. The Hub generally provides simple routing, based on interrogating values specified in the MQRFH2 header <usr> folder.
Any comments/suggestions/recommendations would be much appreciated.
Thanks,
Pat |
|
| Back to top |
|
 |
| jefflowrey |
| Posted: Fri Dec 02, 2005 1:47 pm Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
MQ and Broker can handle Unicode, and does translate everything given to it (when modeled, at least) into Unicode.
As long as your Java applications always use UTF-8 or UTF-16, you should be fine.
But expect to have to tweak things a bit, and understand what's going on with CodedCharSetId's and the way MQ does character translation.
Also expect that tools like amqsbcg will show you what appears to be blank spaces between every character - because you are looking at double-byte data.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| podowd |
| Posted: Mon Dec 05, 2005 2:50 pm Post subject: |
|
|
Novice
Joined: 23 Sep 2004
Posts: 19
|
Thanks Jeff
I am planning to write messages to the queue with an RFH2 header, in the RFH2 header there is a field CodedCharSetId, I am planning on using a value of 1208 in here which apparently is UTF-8.
Would 1208 be the common/typical value to use for Unicode data? (From the WMQ Java manual I see there are other values available for this field within the RFH2 header - 1200, 13488, 17584.)
What is the relationship between the MQMD ccsid field and the ccsid field specified within the RFH2 header? From the WMQ Java manual, I see I can use 1200 (Unicode) or 1208 (UTF8) for the MQMD ccsid (not sure what differs between 1200/1208, UTF-8 is what I normally use for XML docs). I am planning to set the MQMD ccsid to 1208 also and then apparently if I use the MQMessage writeString method it will convert my data to 1208.
Any recommendations on tools to use to browse msgs in hex that I write that contain double byte data (I currently use tools like q and rfhutilc, I know q can produce hex output, I will try this)?
Anyone got any example java code where you write an WMQ message that caters for double byte data?
Thanks,
Pat |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Mon Dec 05, 2005 5:06 pm Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
The CCSID on the MQMD should technically describe what CCSID the next part of the message is in. Since the next part of your message will be the MQRFH2, then you need to ensure that the MQMD sets the CCSID to a value that is valid for an MQRFH2 - which is only a few, and I believe 1208 is one of them.
Then the CCSID of the MQRFH2 will indicate the CCSID the next part of the message after the RFH2 is... which will likely be your message body, in which case... again you want it to be 1208 or 1200 or one of the Unicode/UTF CCSIDs.
_________________
I am *not* the model of the modern major general. |
|
| 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
|
|
|
|
