| Author |
Message
|
| ein |
 Posted: Mon May 18, 2009 3:53 am Post subject: Encoding problem in WMB 6.1 |
 |
|
Centurion
Joined: 14 Mar 2009
Posts: 108
|
Hello Everybody..
I have configured a generic sap Out adapter to receive the ALE iDoc in a queue. It's working for all IDocs. Recently i have faced one bug with this Mesage flow.
An IDoc contains CZ republic country language in some fileds. Borker is able to identify the all the languages in the IDocs and they are coming exactly except CZ republic code.
I have tried to encoded the IDoc before send it to Queue. But it was not completely successfull. It was able to show some characters.
Please look below for
Here is the data in the IDoc
Å¡ťÅ¾ľčěďňřůĺ Å ŤÅ½ĽČĚĎŇŘŮĹ
Here is the Data in Queue once it coming out of adapter.
š?ž???????? Š?Ž????????
Can any one help me to resolve this issue please... |
|
| Back to top |
|
 |
| Maximreality |
| Posted: Wed May 20, 2009 1:01 am Post subject: Re: Encoding problem in WMB 6.1 |
|
|
Acolyte
Joined: 04 Jun 2004
Posts: 65
Location: Copenhagen
|
Verify the codepage of your system
Go to transaction SNLS in SAP to check the codepage of the system
Make sure to use the same codepage when configuring the adapter component.
Also check in SAP transaction SM59 that your RFC connection is running unicode (if your system is unicode)
Does "?" represent the same hex value, then it could be some configuration where all characters that it can not understand is converted to an error indicator. SAP has a default feature where conversion errors are replaced with U+0023 (#) |
|
| Back to top |
|
|
| ein |
| Posted: Fri May 22, 2009 2:35 am Post subject: Re: Encoding problem in WMB 6.1 |
|
|
Centurion
Joined: 14 Mar 2009
Posts: 108
|
| Maximreality wrote: |
Verify the codepage of your system
Go to transaction SNLS in SAP to check the codepage of the system
Make sure to use the same codepage when configuring the adapter component.
Also check in SAP transaction SM59 that your RFC connection is running unicode (if your system is unicode)
Does "?" represent the same hex value, then it could be some configuration where all characters that it can not understand is converted to an error indicator. SAP has a default feature where conversion errors are replaced with U+0023 (#) |
Hello MaximumReality,
We have checked with in SAP , They are using the code page 4102 , So I have configured adapter with this code page and i try to deployed it. But it was failed to due the following error.
" The adapter error message is '>> unknown RFC error, no error log found '
failed. Reason: >> unknown RFC error, no error log found
The message flow node failed to register with the adapter component to receive events. The node cannot function correctly until it has attached to the adapter component. "
Please suggest me what else we need to do to achieve this. |
|
| Back to top |
|
|
| ein |
| Posted: Sun May 24, 2009 11:07 pm Post subject: |
|
|
Centurion
Joined: 14 Mar 2009
Posts: 108
|
For more information about this error
The message broker received an invalid configuration message and has not updated its configuration. This can arise as a result of errors in the specification of either message flows or message sets which the configuration manager was unable to detect. It can also result from a message flow requiring a type of node that is not supported by the broker installation, from the broker having become out of step with the configuration database or from other applications sending extraneous messages to the broker's configuration queues (SYSTEM.BROKER.ADMIN.QUEUE & SYSTEM.BROKER.EXECUTIONGROUP.QUEUE). |
|
| Back to top |
|
|
| Maximreality |
| Posted: Mon May 25, 2009 3:43 am Post subject: Re: Encoding problem in WMB 6.1 |
|
|
Acolyte
Joined: 04 Jun 2004
Posts: 65
Location: Copenhagen
|
4102 is UTF-16 big endian, and is the application server encoding
In SNLS it will most like say codepage 4110 for the frontend, try and use that for your connection.
Have you tried pressing the "Unicode test" button in the config of the RFC connection?? (in transaction SM59)
You should get a reply like this:
Target is a unicode system (character size 2) |
|
| Back to top |
|
|
| ein |
| Posted: Mon May 25, 2009 9:07 pm Post subject: Re: Encoding problem in WMB 6.1 |
|
|
Centurion
Joined: 14 Mar 2009
Posts: 108
|
| Maximreality wrote: |
4102 is UTF-16 big endian, and is the application server encoding
In SNLS it will most like say codepage 4110 for the frontend, try and use that for your connection.
Have you tried pressing the "Unicode test" button in the config of the RFC connection?? (in transaction SM59)
You should get a reply like this:
Target is a unicode system (character size 2) |
Hell maximreality,
We have done the unicode test at SAP. it returns the same what you have mentioned.
I have configured my adapter to with this code page [4110 ]. I have tested it . Again it gives the same output with (?????') this marks .
Can you please suggest me how we can achieve this. |
|
| Back to top |
|
|
| Maximreality |
| Posted: Tue May 26, 2009 1:59 am Post subject: Re: Encoding problem in WMB 6.1 |
|
|
Acolyte
Joined: 04 Jun 2004
Posts: 65
Location: Copenhagen
|
I suggest that you raise a PMR for your problem and post IBM's reply here
It might be a character conversion problem between SAP and the SAPInput node |
|
| Back to top |
|
|
| kimbert |
| Posted: Tue May 26, 2009 2:15 am Post subject: |
|
|
Jedi Council
Joined: 29 Jul 2003
Posts: 5542
Location: Southampton
|
| If you have not already done so, please take a user trace. |
|
| Back to top |
|
|
| ein |
| Posted: Thu May 28, 2009 4:18 am Post subject: |
|
|
Centurion
Joined: 14 Mar 2009
Posts: 108
|
Hello Kimbert,
I have taken user trace. i have not seen any kind of information about those characters. |
|
| Back to top |
|
|
| kimbert |
| Posted: Thu May 28, 2009 4:46 am Post subject: |
|
|
Jedi Council
Joined: 29 Jul 2003
Posts: 5542
Location: Southampton
|
| Fair enough. I was hoping that the user trace would contain a more detailed reason for the deploy failure. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Thu May 28, 2009 6:29 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
Could the deploy failure just be that the adapter has been configured to attach to an SAP system configured as Unicode whereas said SAP system is not set up as a Unicode system? 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| ein |
| Posted: Thu May 28, 2009 11:23 pm Post subject: |
|
|
Centurion
Joined: 14 Mar 2009
Posts: 108
|
| Yes SAP System is configured as unicode system that we checked it. |
|
| Back to top |
|
|
| ein |
| Posted: Thu May 28, 2009 11:30 pm Post subject: |
|
|
Centurion
Joined: 14 Mar 2009
Posts: 108
|
The support team suggest that,
use the DBCS partner character set in my adapter. previously i have used ISO8859_2. its sigle byte character set.
can any one suggest me which character set is going to support DBCS. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Fri May 29, 2009 10:23 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| ein wrote: |
The support team suggest that,
use the DBCS partner character set in my adapter. previously i have used ISO8859_2. its sigle byte character set.
can any one suggest me which character set is going to support DBCS. |
CCSID 1200 or UTF-16 ?? If you are looking for the SAP CHARSET it should be present on the connection
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| ein |
| Posted: Sun May 31, 2009 11:20 pm Post subject: |
|
|
Centurion
Joined: 14 Mar 2009
Posts: 108
|
I have tried with UTF-16BE as my characterset.
Still i am getting the same output.('????'); |
|
| Back to top |
|
|
|
|
