on 09-14-2011 3:52 PM
Hi,
I have this scenario JMS --> PI --> JMS
The message coming into PI has encoding ISO-8859-1 but PI doesn't allow some characters since it is expecting UTF=8.
I am using Transport Protocol = JMS Provider.
Can anyone suggest what I should put in my module tab in order to handle these unusual characters?
I have read a lot of links and notes and understood that these two functions should be used...but how?
localejbs/AF_Modules/MessageTransformBean
AF_Modules/XMLAnonymizerBean
BR
Hi,
Please see this
<Removed By Moderator>
http://help.sap.com/saphelp_nw04/helpdata/en/45/d169186a29570ae10000000a114a6b/content.htm
Edited by: Aashish Sinha on Sep 15, 2011 12:24 PM
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
in module tab write module name as AF_Modules/XMLAnonymizerBean
Type as Local Enterprise bean
Module Key say 0.
in Module configuration choose Module key defined above ( Here 0).
Parameter name anonymizer.encoding
Parameter Value ISO-8859-1.
P.S. you have to declare all namespaces inside your XML anyway, otherwise they will be removed
Regards
Raj
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
Thanks!
I have used AF_Modules/XMLAnonymizerBean and gave the right namespaces, but I have the same problem?
Nothing have changes in the payload regarding the symbols.
My parameters are:
module name: AF_Modules/XMLAnonymizerBean
Type: Local Enterprise bean
Module Key: 0.
Module key: 0.
Parameter name: anonymizer.encoding
Parameter Value: ISO-8859-1
Module key: 0.
Parameter name: anonymizer.acceptNamespaces
Parameter Value: ww.w3.org/2001/XMLSchema-instance''
Should this solve the problem? Or are there any other suggestions?
Can you check your audit log
if this is written "Audit log of the message 'Anonimizer: failed to anonymize due to..." then you may need to check SAP Notes # 1467423 and apply mentioned patches.
One more obsevation
Parameter name: anonymizer.acceptNamespaces
Parameter Value: ww.w3.org/2001/XMLSchema-instance''
Her you are required to maintain Namespace of your interface / message which you need to populate in output payload.
Regards
Raj
Hi,
First please check with the MQ system that is they are using any character set encoding at their end.
also please check the inbound XML message header is it with ISO-8859_1 or UTF-8?
if it is using ISO-8859-1 then you need to use anonymizer bean to convert the code page.
By default PI is using UTF-8 .
please also try to use CCSID-1252 or 1208 With Code Page-UTF-8.
We had similar problem where we asked the MQ people to write the message using CCSID-1252 using UTF-encoding and it worked.
Regards,
Navneet
HI,
The XML message header is it with ISO-8859-1.
I don't have any CCID option since I use JMS provider and not WebsphereMQ .
And I also already used anonymizer without any luck. Please look at my previous posts to see the module settings with anonymizer.
could localejbs/AF_Modules/MessageTransformBean be any help?
Hi Sonny,
You were able to resolve this case ?
I'm having this exact situation. Where we use JMS provider to transfer xml to PI and the XML has encoding header to be ISO-8859-1. But still the special characters doesn't get seen as it is actually but in weird character shapes.
We have tried XSLT character encoding, But it doesn't work. Even after encoding from ISO-8859-1 to UTF-8 in PI, The XML are still seen with symbols instead of å, ä, ö.
Hope this reaches you.
Kind Regards
Rajesh.S
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
88 | |
23 | |
11 | |
9 | |
8 | |
5 | |
5 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.