| Author |
Message
|
| mfractal |
 Posted: Thu Apr 17, 2008 8:20 am Post subject: Unconvertable character with SAP adapter |
 |
|
Novice
Joined: 07 Apr 2008
Posts: 14
|
Hi All!
We've been using SAP adapter with Broker (version 6.1).
Our flow recieves an Idoc from SAP, does copyEntireMessage and puts in to MQOutput node.
Usually the flow works great, but when an Idoc arrives containing "strange" characters we get an exception.
Here's what we see in the exception list (just the relevant part)
| Code: |
Text:CHARACTER:XML Writing Errors have occurred
RecoverableException
File:CHARACTER:F:\build\S000_P\src\CommonServices\ImbConverter.cpp
Line:INTEGER:312
Function:CHARACTER:ImbConverterCPP::internalFromUnicode
Type:CHARACTER:
Name:CHARACTER:
Label:CHARACTER:
Catalog:CHARACTER:BIPv610
Severity:INTEGER:3
Number:INTEGER:2136
Text:CHARACTER:Unconvertable character
Insert
Type:INTEGER:5
Text:CHARACTER:8e00
Insert
Type:INTEGER:5
Text:CHARACTER:4c0061006e00640031003e00420052003c002f004c0061006e00640031003e003c005a006c007300630068003e0046003c002f005a006c007300630068003e003c00540065007800740031003e0041
0052002d00560065006e0064006100200041006e00740065006300690070006100640061003c002f00540065007800740031003e003c002f005
300610070005a0073006400740054006100620065006c00610073005a0073006400730054003000340032007a003000300030003e003c005300610070
005a0073006400740054006100620065006c00610073005a0073006400730054003000340032007a003000300030003e003c004d0061006e006400740
03e003100340030003c002f004d0061006e00640074003e003c004c0061006e00640031003e00420052003c002f004c0061006e00640031003e003c005a
006c007300630068003e0047003c002f005a006c007300630068003e003c00540065007800740031003e00410052002d00560065006e00640061002000
43006f006c00690067006100640061003c002f00540065007800740031003e003c002f005300610070005a0073006400740054006100620065006c00610
073005a0073006400730054003000340032007a003000300030003e003c005300610070005a0073006400740054006100620065006c00610073005a007
3006400730054003000340032007a003000300030003e003c004d0061006e00640074003e003100340030003c002f004d0061006e00640074003e003c0
04c0061006e00640031003e00420052003c002f004c0061006e00640031003e003c005a006c007300630068003e0049003c002f005a006c007300630068
003e003c00540065007800740031003e00410052002d0043006f006200720061006e00e700610020005000650072006d007500740061003c002f005400
65007800740031003e003c002f005300610070005a0073006400740054006100620065006c00610073005a0073006400730054003000340032007a0030
00300030003e003c005300610070005a0073006400740054006100620065006c00610073005a0073006400730054003000340032007a00300030003000
3e003c004d0061006e00640074003e003100340030003c002f004d0061006e00640074003e003c004c0061006e00640031003e00420052003c002f004c0
061006e00640031003e003c005a006c007300630068003e004b003c002f005a006c007300630068003e003c00540065007800740031003e00410052002d
00430061007200740065006900720061003c002f00540065007800740031003e003c002f005300610070005a0073006400740054006100620065006c006
10073005a0073006400730054003000340032007a003000300030003e003c005300610070005a0073006400740054006100620065006c00610073005a0
073006400730054003000340032007a003000300030003e003c004d0061006e00640074003e003100340030003c002f004d0061006e00640074003e003
........
400730054003000340032007a003000300030003e003c005300610070005a0073006400740054006100620065006c00610073005a0073006400730054003000340032007a00300030
0030003e003c004d0061006e00640074003e003100340030003c002f004d0061006e00640074003e003c004c0061006e00640031003e0
0430048003c002f004c0061006e00640031003e003c005a006c007300630068003e0044003c002f005a006c007300630068003e003c00540065007800740031003e004
40065006200690074002000640069007200650063007400200050006f0073007400660069006e0061006e006300650020002800420
04100440029003c002f00540065007800740031003e003c002f005300610070005a0073006400740054006100620065006c00610073005a0073006400730054003000340032007a0030
00300030003e003c005300610070005a0073006400740054006100620065006c00610073005a0073006400730054003000340032007a003000300030003e003c004d0061006e00640074003e003100340030003c002f004d0061006e0
0640074003e003c004c0061006e00640031003e00430048003c002f004c0061006e00640031003e003c005a006c007300630068003e00
45003c002f005a006c007300630068003e003c00540065007800740031003e0044005400410020004500530052002d0
0560065007200660061006800720065006e0020002800420061006e006b0029003c002f0054006500780074003100
3e003c002f005300610070005a0073006400740054006100620065006c00610073005a0073006400
730054003000340032007a003000300030003e003c005300610070005a007300640074005400610062
0065006c00610073005a0073006400730054003000340032007a003000300030003e003c004d0061006e00640074003
e003100340030003c002f004d0061006e00640074003e003c004c0061006e
|
Any ideas guys ?
We're kind of lost here 
Any other info i can provide ?
[moderator]split into multiple line for better readability[/moderator] |
|
| Back to top |
|
 |
| fjb_saper |
| Posted: Thu Apr 17, 2008 5:14 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
What char set is the source system (SAP) in?
What is the char set of the IDOC?
Did you make sure your output is in UTF-8 or Unicode?
Looks to me like you may not have a text idoc and what we see is a byte array representing the values taken by the chars and numbers in the makeup of the Idoc...
Enjoy 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| mfractal |
| Posted: Fri Apr 18, 2008 10:20 am Post subject: |
|
|
Novice
Joined: 07 Apr 2008
Posts: 14
|
We were able to fix the problem by enforcing :
charset=819
encoding=1200
SAP works in unicode.
The charset of the idoc when it arrives is empty, that was part of the problem.
That's why the default cast when sending to mqoutput failed. |
|
| Back to top |
|
|
| rakesh567 |
| Posted: Tue Apr 22, 2008 9:59 am Post subject: |
|
|
Novice
Joined: 26 Jan 2008
Posts: 18
|
We wanted to use sap adaters through v6.1
Our broker is in AIX.
when we r building we r using windows client libraries.
Since broker is in AIX do we need to use the aix client library while deploying?
What configurations required to connect to SAP.in message broker other than adapte config............. |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Tue Apr 22, 2008 10:01 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
All of the runtime libraries for the v6.1 SAP libraries are handled outside of your flow code, and by the broker administrator.
And yes, when the broker is running on a Unix platform, then you must use Unix versions of those libraries.
But not in your flow.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| rakesh567 |
| Posted: Tue Apr 22, 2008 10:09 am Post subject: |
|
|
Novice
Joined: 26 Jan 2008
Posts: 18
|
you mean to say we can use windows library file and deploy.
we need to configure aix library file in broker.and configure its jars URL. |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Tue Apr 22, 2008 10:22 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
|
| Back to top |
|
|
| akbardar |
| Posted: Wed Mar 05, 2014 8:51 am Post subject: |
|
|
Novice
Joined: 05 Apr 2006
Posts: 21
Location: New Haven, CT
|
How were you able to fix the problem by enforcing :
charset=819
encoding=1200
How do we setup the Charset code as message enters into the flow? Is there eSQL fix a or Message Broker Adapter fix? Please advise.
Regards
AkBar Dar
_________________
AkBar Dar
IT Administrator |
|
| Back to top |
|
|
|
|
