Character encoding in Seeburger mapping

[Former Member]

Hello all,

In my EDI project, i use Seebruger EDI Adapter.

We have discover a problem when you use french character has é, è, à, etc... In fact, Seeburger see the "é" has A@A, it convert the letter so when we arrive in the bic mapping of seeburger it crash down because for him, the field is too long.

exemple :

Field 1 after integration engine (limit on 4 characters in bic mapping) : éert

Field 1 interpreted by seeburger : A@Aert => so we are above the authorized limit.

I know that we send message in UTF-8 but i am a little bit surprise that Seeburgerr doesn't read UTF-8.

Is someone has an idea ?

Regards,

JP

[Former Member]

Hi,

Well, you could use a JavaMapping logic to correct that, but if you want it to do it with seeburger tools for that cases you need to use the module ReplaceString in seeburger:

In the "Module" option of the channel, you have 2 parameters, "Processing Sequence" and "Module Configuration"

There you need to do the following:

-

-

---

Processing Sequence:

Module name: localejbs/Seeburger/ReplaceString

Module Type: Local Enterprise Bean

Module Key: 1 <= key for calling that sequence

-

-

---

Module Configuration:

Module Key: 1

Parameter Name: searchString

Parameter Value: "à" <= search value

Module Key: 1

Parameter Name: replaceString

Parameter Value: "a" <= replace with

-

-

---

You would need to do that for every character you have, when you save the order would probably change leaving replace first instead of search, but i'll work anyway, that doesn't affect anything

Hope you find that helpful,

Regards,

[Former Member]

Thank you for your answer !

But the problem is that they want to keep their" à, é," in output so if i replace, they won't be happy....

Edited by: PAIN Jean-Philippe on Sep 19, 2008 7:06 PM

[Former Member]

Hi,

Try out using file encoding ISO-8859-1 in sender channel..