| Author |
Message
|
| EnthusiasticSatya |
 Posted: Tue Nov 15, 2011 9:46 pm Post subject: Special Character Issue |
 |
|
Apprentice
Joined: 10 Aug 2011
Posts: 26
|
Hi All,
I am working on a Inbound flow ( SAP --> WMB (7.0)) , so I am receiving the data from SAP via JCA Adpater.
There are some italian character inserted in the SAP and send to WMB via adapter.
I checked in debug mode and found that those characters are not getting recognised by XML ( BAPI always generates the data in XML format ,(dataobject)) , and it is throwing the error as " XML Parsing Error ".
When I checked with SAP guyz, they say that they are sending the data in UTF-8 format.
I am not sure how to handle this , as the exception is throwing right after the BAPI , I cannot even handle this in Java/ESQL node ( with CCSID encoding ).
Is there any settings in WMB 7.0 SAP adapter to handle this.
Any sugestions. |
|
| Back to top |
|
 |
| EnthusiasticSatya |
| Posted: Wed Nov 16, 2011 1:46 am Post subject: |
|
|
Apprentice
Joined: 10 Aug 2011
Posts: 26
|
| Can some respond to this ASAP. |
|
| Back to top |
|
|
| smdavies99 |
| Posted: Wed Nov 16, 2011 2:13 am Post subject: |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
If you need a response within a set timeframe then this forum is NOT the place to goto for support like this, you need to raise a PMR with IBM.
This forum is run by volunteers. Sometimes those with specific knowledge of your problem might not ne 'on-line' whant you make a post. For example, most of the people who respond here AND who live on the western side of the Atlantic will be sendibly tucked up in bed at 05:46GMT.
That said, your post was very general in nature. What Italian characters? Please give examples of what you are getting etc.
Did you use a tool like wireshark to sniff out exactly what SAP is sending to you?
All of this sort of 'self help' will help us to help you. As will telling us what you have done to resolve the problem. This helps us not to suggest the things you have already done.
_________________
WMQ User since 1999
MQSI/WBI/WMB/'Thingy' User since 2002
Linux user since 1995
Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions. |
|
| Back to top |
|
|
| mqjeff |
| Posted: Wed Nov 16, 2011 3:01 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| just because the SAP guys say that they are sending it in UTF-8 does not mean that it was stored into SAP in UTF-8. |
|
| Back to top |
|
|
| EnthusiasticSatya |
| Posted: Wed Nov 16, 2011 3:36 am Post subject: |
|
|
Apprentice
Joined: 10 Aug 2011
Posts: 26
|
Since this was an issue in the production , so I was looking for the quick reply ,I am suppose to providethe resolution at the earliest.
Characterd are : УЛ.КУЙБЫШЕВА.
Sap JCA adapter is IBM tool . So when checked in debug mode, we get error as "XML Parsing Error "
I have also checked the SAP Input property , but ddn't find anything.
Please provide any suggestions. |
|
| Back to top |
|
|
| smdavies99 |
| Posted: Wed Nov 16, 2011 3:46 am Post subject: |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
| EnthusiasticSatya wrote: |
Characterd are : УЛ.КУЙБЫШЕВА.
|
May I suggest that the characters are NOT ISO-Latin-8859-1, Italian or any ISO-Latin variant but they are Cyrillic (via Russian, Bulgarian etc)
Can you get someone who has SAP Access to actually view the data from inside SAP?
My Russian is a little rusty but the last part proably translates to KUYBYSHEVA. I once worked on Kuybysheva St in Yekaterinberg, Russia. It could be part of an address.
_________________
WMQ User since 1999
MQSI/WBI/WMB/'Thingy' User since 2002
Linux user since 1995
Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions. |
|
| Back to top |
|
|
| rekarm01 |
| Posted: Wed Nov 16, 2011 3:55 am Post subject: Re: Special Character Issue |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 1415
|
| EnthusiasticSatya wrote: |
| I checked in debug mode and found that those characters are not getting recognised by XML ( BAPI always generates the data in XML format ,(dataobject)) , and it is throwing the error as " XML Parsing Error ". |
Is that the debugger, or usertrace? What is the complete error message? (If the error has excessively long lines, break up the long lines before posting.) |
|
| Back to top |
|
|
| EnthusiasticSatya |
| Posted: Wed Nov 16, 2011 3:59 am Post subject: |
|
|
Apprentice
Joined: 10 Aug 2011
Posts: 26
|
SAP Team is able to this cyrillic characters УЛ.КУЙБЫШЕВА as it is in SAP.(VD03 transaction).
The problem with WMB is due to this characters , as SAP adapter is not able to procees this. |
|
| Back to top |
|
|
| mqjeff |
| Posted: Wed Nov 16, 2011 4:00 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| EnthusiasticSatya wrote: |
| Since this was an issue in the production , so I was looking for the quick reply ,I am suppose to providethe resolution at the earliest. |
The operative point here is that it is you that has this requirement and not us.
Nobody here is getting paid to respond to anything. If you have a requirement that requires an immediate response, then you need to open a PMR. |
|
| Back to top |
|
|
| EnthusiasticSatya |
| Posted: Wed Nov 16, 2011 4:00 am Post subject: |
|
|
Apprentice
Joined: 10 Aug 2011
Posts: 26
|
| The only error message I could see in debugger is "XML Parsing Error " |
|
| Back to top |
|
|
| kimbert |
| Posted: Wed Nov 16, 2011 4:41 am Post subject: |
|
|
Jedi Council
Joined: 29 Jul 2003
Posts: 5542
Location: Southampton
|
You cannot always find a problem in a message flow using only the debugger. Sometimes you need Trace nodes and user trace. Sometimes you need to use other tools to inspect the data before it arrives at the input node of your flow.
The advantage of a user trace is that you *always* get *all* of the message. |
|
| Back to top |
|
|
| EnthusiasticSatya |
| Posted: Tue Jan 10, 2012 9:46 pm Post subject: |
|
|
Apprentice
Joined: 10 Aug 2011
Posts: 26
|
Hi ,
Thanks to all . My problem is resolved.
The input data from SAP Adapter contained special character (Cyrillic character ) . The adapter was directly attached to the MqOutput queue.
This was the issue as the queue was not accepting the special character.
So in between adapter and the queue , I placed a ESQL node , where I changed the CCSID to 1208.
This solved my problem and I could receive the data from SAP. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Tue Jan 10, 2012 10:01 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| EnthusiasticSatya wrote: |
Hi ,
Thanks to all . My problem is resolved.
The input data from SAP Adapter contained special character (Cyrillic character ) . The adapter was directly attached to the MqOutput queue.
This was the issue as the queue was not accepting the special character.
So in between adapter and the queue , I placed a ESQL node , where I changed the CCSID to 1208.
This solved my problem and I could receive the data from SAP. |
Let's keep it professional here... queues do not accept or refuse any special characters.
The problem was that without passing the CCSID explicitly you might have had the qmgr default set on the MQOutput node and that default probably did not support your Cyrillic characters... or have mislabeled the CCSID of a text message or content...
Don't know enough about the DataObject to know whether it is CCSID sensitive...
Have fun and thanks for posting the solution. 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
|
|
