How to send data in ASCII (instead of Unicode) from XI using JMS adapter

[Former Member]

Hi

The scenario is R/3 > XI >MQ > Third party SW. Inside XI, we have an ABAP mapping as well.

The receiving third party software needs data in ASCII. Currently we are achieving this in MQ, but would like to move this conversion to XI.

Any thoughts on that are welcomed.

Thanks in advance.

Cheers

danus

Message was edited by:

Chidambaram Danus

[stefan_grube · Accepted solution]

When you have only the 95 ASCII characters in the message, then you do not need anything to do, besides changing the XML declaration. That can be done with the XMLAnonymizerBean

/people/stefan.grube/blog/2007/02/02/remove-namespace-prefix-or-change-xml-encoding-with-the-xmlanonymizerbean

For a plain text there nothing to do.

Regards

Stefan

[Former Member · Accepted solution]

Well it has Hungarian characters !

[stefan_grube · Accepted solution]

In that case, you cannot convert it to ASCII, as ASCII does not provide these characters. http://en.wikipedia.org/wiki/ASCII

What should happen with these characters?

[manish_bhalla2 · Accepted solution]

If it has Hungarian Characters, then you probably want the ISO 8859-2 Codepage

http://en.wikipedia.org/wiki/ISO_8859

Cheers

Manish

[Former Member · Accepted solution]

Yeah I realize my mistake, it should be ISO 8859-2 encoding. Could you tell me how to convert the data to this encoding before the data is send to MQ through the JMS adapter.

[stefan_grube · Accepted solution]

You can use the Text Codepage Conversion Module.

See SAP Note 960663 for details.

[Former Member · Accepted solution]

HI,

see

Character Set ID (CCSID) for non-ASCII Names

Specifies the character set for the above-specified name. This entry does not affect the character set of the transferred messages

In the below link

http://help.sap.com/saphelp_nw2004s/helpdata/en/c1/739c4186c2a409e10000000a155106/content.htm

Regards

Chilla

[Former Member · Accepted solution]

Hi Chilla,

I did see that help, but did not understand what they mean by "This entry does not affect the character set of the transferred messages"... any idea what that means ?

[stefan_grube · Accepted solution]

That means: This is just a declaration. The message itself is not transferred to another codepage. In standard you have to choose the CCSID corresponding to UTF-8.

When you want to choose another codepage, you have to do the code conversion with an adapter module or an XSLT/Java mapping.

Regards

Stefan

[SD78 · Accepted solution]

Hello Stefan,

I have the same problem with data conversion to utf-8.

The mainframe application sends us the data in the codepage iso-8859-1, but the jms sender adapter transfers this in utf-8.

Can I stop this?

You have proposal a oss note 960663, but on which position must be setup this in the module sequence? At first?

What are the other options of the parameter conversion.charset ?

Is there one possibility without mapping?

Bye

Stefan

[stefan_grube · Accepted solution]

Every message is transfered to UTF-8, otherwise the mapping would fail.

The receiver adapter has to tranform the message back to the codepage you want.

Regards

Stefan

[manish_bhalla2]

Hi,

If you use the File Adapter, you can specify the following parameters:

File type = text

File encoding = US-ASCII

This will then use the US-ASCII codepage.

(Refer SAP Help http://help.sap.com/saphelp_nw04/helpdata/en/bc/bb79d6061007419a081e58cbeaaf28/frameset.htm)

Regards

Manish

[Former Member]

In our case, it is a JMS adapter, though !

[manish_bhalla2]

Hmm.. then I am not confident of this, but SAP Note 859548 may be able to help you. More info is available on SAP Help at this location:

http://help.sap.com/saphelp_nw04/helpdata/en/c1/739c4186c2a409e10000000a155106/frameset.htm

Hope this helps

Manish