Special Characters issue---u00FA ,u00A3---- in Reciver SOAP Adapter

[ravi_teja14]

Hi ,

I am facing issues with Spceial Characters ú ,£ at the reciver SOAP adapter ,the messages was stuk in XI with to the following error :An invalid character was found in text content. Error processing resource

I tried in several ways buy using XMBWS.XMLEncoding=iso-8859-1,

but it was not resloved still I am getting the same error,

Any one plz suggest me how to resolve this issue....

Regards,

Teja.

[former_member472138]

Use this UDF

Here a is the input value.

String b = "";

b = a.replaceAll("ú", "0");

b = a.replaceAll("£", "0");

Like all the special characters you can take and replace with zero.

...........

return b;

Thanx

Pothana

[Former Member]

Why you don't put conversion in sender channel?

[ravi_teja14]

Hi ,

But the messages is successfully proccessed at sender adapter, the issue is at the receiver Soap Adapter ,

[Former Member]

Hi,

You may configure the module tab as below:

module key = soap

name = XMBWS.XMLEncoding

value = UTF-8

it will be working.

Thanks

[ravi_teja14]

Hi ,

I have done the changes as the bleow

Processig sequence:

Module Name =localejbs/sap.com/com.sap.aii.af.soapadapter/XISOAPAdapterBean

Type=Local Enterprise Bean

Module Key=soap

Module Configuration:

module key = soap

name = XMBWS.XMLEncoding

value = UTF-8

but the error is similar specails characters error(Invalid Character) ,

I am getting Error in the audit log

Error: HTTP 400 Bad Request

Regards,

Teja.

[former_member472138]

Why don't you request the Target system admin to setup the encoding to UTF-8.

Say that the problem is with the receiver system whether it is webserver or else.

Regards

Pothana

[ravi_teja14]

Hi ,

the issue is not at the Target end ...

I tried by using ISO-88559-1 in the source payload, it was successfully processed so no need to change at the target end,

The issue is in XI , if we can change the encoding utf-8 to iso-8859-1 then it will works,

The reciver soap adapter is also working for the modified source payload...

Now I want to change utf-8 to iso-8859-1.

Regards,

Teja.

[stefan_grube]

It seems that your XML payload is not correct, when entering PI.

So you have to fix the issue at sender site. That menas you have to adjust the web service client to provide a correct XML.

The encoding of the XML must correlate to the XML declaration. If there is no encoding declaration in the XML document, then the default is UTF-8.

As you already found, the scenario works, when the XML header has encoding ISO-88559-1 instead of UTF-8.

So you see that the issue is in sender system.

[ravi_teja14]

Hi ,

My scenario is RFC--SOAP ,the messages was successfully rached to RFC adapter and I am facing the issue at the receiver SOAP Adapter ......

I am getting error messages such as :

1) 400 Bad Request

2) In the XML Payload ......It is showing as Invalid Character found ....

For this I tried ...

1) In the source payload XML I done the chages in the encodding part

encoding part as iso-8859-1instead of utf-8.

2) I have triggered the message from Integration Engine ....then it was successfully processed through SOAP Adapter

3) with special characters...means there is no issue at target end.

4) the issue lies in XI so we have to resolve it.

I tried by using Adapter paramters which was provided by SAP but the result is same..

so the paramters which was provided by SAP are incorrect(for encoding)

Please help me in resolving this issue .........

Regards,

Teja.

[stefan_grube]

Once again, the issue is neither in PI, nor in receiver SOAP adapter.

The issue is in your RFC adapter.

When your RFC adapter settings are correct, then the RFC adapter translates your XML payload to UTF-8

But: I have no idea, how the message looks like, when you send it from sender system. so I cannot tell you exactly what is wrong.

But I am quite sure, that you have to investigate, why the RFC adapter does not provide an XML document according to XML standards.

There could a a lot of reasons, for example the ABAP code calling the RFC is wrong or the connection settings for the RFC channel are wrong.

[ravi_teja14]

Hi All,

I have resloved it myself(own) ,

Thanks for quick response

Regards,

Teja.