| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
| SAP WBI Adaptor & Double byte chars |
« View previous topic :: View next topic » |
| Author |
Message
|
| Bravo |
 Posted: Thu Dec 06, 2007 6:01 pm Post subject: |
 |
|
Centurion
Joined: 03 Oct 2005
Posts: 146
|
Hi fazz,
I'm facing same problem!!! Any inputs to resolve the issue.
Opened PMR.
_________________
Bravo |
|
| Back to top |
|
 |
| fazz |
| Posted: Fri Dec 07, 2007 5:12 am Post subject: |
|
|
Centurion
Joined: 20 Feb 2004
Posts: 144
Location: England
|
Hello,
Thats interesting that someone else has the same problem.
There is still no resolution from IBM but they are working on it as I type.
We have another mySap.com adaptor running in Germany, and this is also suffering from the same problem.
As soon as I hear anything I will post up.
Out of interest, do you know which characters are causing you problems?
Good luck!
Simon |
|
| Back to top |
|
|
| Bravo |
| Posted: Fri Dec 07, 2007 3:20 pm Post subject: |
|
|
Centurion
Joined: 03 Oct 2005
Posts: 146
|
Thanks for your response fazz..
Its Hex 1A(Unicode Character).This is what I found out with my colleague.
Check this xml spec:
http://www.w3.org/TR/xml/#charsets
Relevant extract from the XML spec. You can see that #x1A does fall in this range. In fact, no character less that #20 is allowed, other than tab, carriage return and line feed.
Hex 1A is an invalid character in XML. It doesn't matter whether you place it in an node unencoded (relying on UTF- , or if you escape it. Eitherway, it's not valid XML, it will not be parsed.
Let me put in this way
Unicode are accepted in WBI adapters for mySAP from 604. Not all Unicode characters are valid charcter in XML.
WBI adapter for mySAP is responsible for creating the invalid XML is to blame. It should have thrown an error.
_________________
Bravo |
|
| Back to top |
|
|
| fazz |
| Posted: Tue Dec 11, 2007 5:54 am Post subject: |
|
|
Centurion
Joined: 20 Feb 2004
Posts: 144
Location: England
|
Hello Bravo,
I too am seeing HEX '1A', but the adaptor is converting the character
into it.
Which characters are being converted incorrectly for you?
I found that any char with a unicode greater than three digits long from this code page http://en.wikipedia.org/wiki/Code_page_852 were converted to '1A'.
IBM have come back and asked me to run this test:
| Quote: |
->You could also check the RFC destination.
For ECC 5 it can be found as follows:
SM59 -> 'TCP/IP connections# -> <RFC dest. name> -> 'Special Options'
-> 'Character With in Target System' must be 'Unicode'
TEST: Connect with adapter to SAP, press 'Unicode Test' on RFC destination page
|
When run here, the repsonse is:
| Quote: |
| Target is a unicode system (char.size 2) |
Which is fine....the puzzle continues. |
|
| Back to top |
|
|
| Bravo |
| Posted: Wed Jan 09, 2008 10:34 am Post subject: |
|
|
Centurion
Joined: 03 Oct 2005
Posts: 146
|
Did you resolve the issue?.
_________________
Bravo |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Wed Jan 09, 2008 1:24 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| fazz wrote: |
Hello Bravo,
I too am seeing HEX '1A', but the adaptor is converting the character
into it.
Which characters are being converted incorrectly for you?
I found that any char with a unicode greater than three digits long from this code page http://en.wikipedia.org/wiki/Code_page_852 were converted to '1A'.
IBM have come back and asked me to run this test:
| Quote: |
->You could also check the RFC destination.
For ECC 5 it can be found as follows:
SM59 -> 'TCP/IP connections# -> <RFC dest. name> -> 'Special Options'
-> 'Character With in Target System' must be 'Unicode'
TEST: Connect with adapter to SAP, press 'Unicode Test' on RFC destination page
|
When run here, the repsonse is:
| Quote: |
| Target is a unicode system (char.size 2) |
Which is fine....the puzzle continues. |
That is because you are converting a special char (Å¡) (kyrillic alphabet in roman char) into a CCSID that does not support it. Hence the invalid char X1A...
Like I said make sure that the message is in a CCSID that supports the char set and do not set the get with convert on the MQInput node if you are running in an env (broker Qmgr CCSID) where the Å¡ is not supported...
Enjoy 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
|
|
|
|
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
|
|
|
|
