| Author |
Message
|
| akash.vit |
 Posted: Sat May 25, 2013 10:56 am Post subject: how to handle Spanish character in flow even the CCSID=1208 |
 |
|
Newbie
Joined: 25 May 2013
Posts: 4
|
Using Unix Aix and WMB v6.1
I have 2 flow
1. 1st flow take the message having spanish character(sólo) from SOAP UI. Flows shows CCSID=1208 Encoding=546 in trace. The sólo gets converted to others character which i m not worried about. then route to the other flow based on the message content by putting in a queue. Before sending the message to the Queue, I configure MQMD to CCSID=1208 and Encoding=546.
2. 2nd flow picks up the message and trace show CCSID=1208 Encoding=546 and then call Datapower using hhtp request node which response back saying received malformed character from client.
Now the thing is If i include the tracenode in 2nd flow after MQinput and do step 1 and 2 I receive the successful response from DP.
If I remove the trace node I received malformed character from client.
The sólo get converted to other character do i have to be worried about?
Does trace node parse and converts the data?
What CCSID i can use to solve the problem?
Please help. Thanks! |
|
| Back to top |
|
 |
| Vitor |
| Posted: Sun May 26, 2013 5:15 am Post subject: Re: how to handle Spanish character in flow even the CCSID=1 |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| akash.vit wrote: |
| The sólo get converted to other character do i have to be worried about? |
How are we supposed to know that? Do you use that part of the data in your process?
| akash.vit wrote: |
| Does trace node parse and converts the data? |
Well, let's think for a moment. You've got a Trace node, which I'm assuming you're using to investigate this problem and hence has either ${Root} or a subset of that as a pattern. How's it going to display that output for you (which is the sole purpose of that node) without parsing & converting the message tree?
| akash.vit wrote: |
| What CCSID i can use to solve the problem? |
You indicate above that if the trace node parses the tree there's no problem in DP. This indicates to me that 1208 contains the needed characters.
Personally I wonder if the original message is not your problem. You say:
| akash.vit wrote: |
| 1st flow take the message having spanish character(sólo) from SOAP UI. Flows shows CCSID=1208 Encoding=546 in trace. The sólo gets converted to others character |
If you're using 1208 throughout and the original message payload is already in a 1208 code page why is conversion occurring? Investigation there might yield some points of interest.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| akash.vit |
| Posted: Sun May 26, 2013 11:23 am Post subject: |
|
|
Newbie
Joined: 25 May 2013
Posts: 4
|
| Quote: |
How are we supposed to know that? Do you use that part of the data in your process?
|
Answer: There is logging process that display the inbound message there i see the converted character in unix.
I used trace with ${Root}. But i did not understand how trace make the DP process successful . Yes trace is introduce to display message properties and MQMD. |
|
| Back to top |
|
|
| akash.vit |
| Posted: Tue May 28, 2013 7:23 am Post subject: |
|
|
Newbie
Joined: 25 May 2013
Posts: 4
|
Trace node, has ${Root} and the spanish character(sólo) get converted to SM-slo in the trace ouptput.
Where as when the message is picked up by 1st and 2nd flow it get converted to Sólo in the log file.
I suppose Sólo is UTF-8 of sólo |
|
| Back to top |
|
|
| stevarg |
| Posted: Thu May 30, 2013 2:55 am Post subject: |
|
|
Novice
Joined: 20 Nov 2012
Posts: 24
|
@akash.vit
could you try converting the CCSID to 850 and run the flow.
This supports spanish characters. |
|
| Back to top |
|
|
| akash.vit |
| Posted: Wed Jun 05, 2013 9:27 am Post subject: |
|
|
Newbie
Joined: 25 May 2013
Posts: 4
|
@stevarg
yes 850 supports.. but this also does not work.
Today i included the trace node just after MQinput for 2nd flow with destination property set as None and Pattern ${Root}.. i got t successful response from Datapower.
Is the trace node internally parse t data some how?? |
|
| Back to top |
|
|
| Vitor |
| Posted: Wed Jun 05, 2013 9:42 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| akash.vit wrote: |
| Is the trace node internally parse t data some how?? |
See above - if the Trace Node doesn't cause WMB to parse the entire message tree, then how could it possibly cause the message tree to be expressed in a human readable form?
Again as I indicate above, the fact that this works indicates what's wrong and how you can fix it.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
|
|
