encoding issue

[Former Member]

In a HTTP to RFC scenario

From http client following message is sent

öäöSovelluksessamme (with ISO-8859-1 enconding)

But on reaching XI its like this

öäöSovelluksessamme

Will the data be proper when it reaches SAP system? Because even SAP system doesn't support ISO encoding .

Can anyone help to resolve this.

Edited by: savita shukla on Jul 17, 2008 7:14 AM

[Former Member]

Hi Progirl,

The approach you suggested cannot be implemented because in our scenario

the sender is HTTP adapter ,so module cannot be added.

Any other solution ?

[former_member190389]

what you can do is ..once the request is received you can create a java mapping to change the encoding by parsing the document... see that the plain http adapter changes specila char to hexadecimals..

http://help.sap.com/saphelp_nw04/helpdata/en/44/79973cc73af456e10000000a114084/frameset.htm

*Enhancing the Payload

Some external systems, for example, Web servers in marketplaces, can only process data if it is sent as an HTML form using HTTP.

A typical HTML form comprises named fields. When transferring a completed form to the server or a CGI program, the data must be transferred in such a way that the CGI script can recognize the fields that make up the form, and which data was entered in which field.

The plain HTTP adapter constructs this format using a prolog and an epilog. Therefore, there is a particular code method that separates form fields and their data from each other. This code method uses the following rules:

● Individual form elements, including their data, are separated from each other by an ampersand (&).

● The name and data of a form element are separated from each other by an equals sign (=).

● Blanks in the entered data (for example, in multiple words) are replaced by a plus sign (+).

● All characters with the (enhanced) ASCII values 128 to 255 (hexadecimal 80 to FF) are transcribed using a hexadecimal sequence, beginning with a percentage sign (%) followed by the hexadecimal value of the character (for example, the German umlaut ö in the character set ISO-8859-1 is transcribed as %F6).

● All characters that occur in these rules as control characters (&, +, =, and %) are also transcribed hexadecimally in the same way as high value ASCII characters.

*

[stefan_grube]

The RFC adapter transfers the document to the codepage which is installed on the SAP system.

So you should not need to do this transformation be your own.

Could it be the case that the original document is not ISO-8859-1, but UFT-8 instead?

Please open the original document with a hex editor, the same you do for the document which you download from SXMB_MONI. Checj which codepage they have.

In ISO-8859-1 the ä is represented by 1 character, in UTF-8 by 2 characters.

Regards

Stefan

[Former Member]

Hi ,

I did end to end testing as well, the data "öäöSovelluksessamme" is getting inserted in the SAP table as this : öäöSovelluksessamme.

That means the RFC adapter isn't performing the conversion ?

And this is the data coming from the client side so cant limit it to basic English.

Is there any other alternative to transform this data to right form??

[former_member190389]

Hi

You can use the XMLAnonymizerBean

see

http://help.sap.com/saphelp_nw04/helpdata/en/45/d169186a29570ae10000000a114a6b/frameset.htm

Entries in the Module Configuration

● anonymizer.acceptNamespaces

Enter a list of namespaces and their prefixes that are to be kept in the XML document as follows: namespace1 n1 namespace2 n2 u2026

To enter a namespace without a prefix, enter '' (two single quotation marks).

Any namespaces you do not specify are removed from the XML document.

● anonymizer.quote

Specify the character to be used to enclose the attribute values.

The default value is '. The parameter is optional.

● anonymizer.encoding

To use a code page other than UTF-8, enter it. The parameter is optional.

For example, enter ISO-8859-1.

[stefan_grube]

But on reaching XI its like this

öäöSovelluksessamme

This is UTF-8- It is display wrong, but the encoding is correct.

Will the data be proper when it reaches SAP system? Because even SAP system doesn't support ISO encoding .

The encoding willbe adopted to the system encoding of the SAP system.

The RFC adapter will do the conversion od the encoding automatically.

Regards

Stefan

[Former Member]

Well my guess is that it should work.

You read the file specifying ISO encoding.

Once the message is inside XI, it gets converted into UTF-8.

Do an end-to-end testing and see if it is as expected.

Regards.

[Former Member]

Hi Savitha,

The web services checker is not supporting special encoding.

Only basic as english is supported.

This is due to limitation to IDE text fields.

thanx

Sampath