Anonymizer.encode

I need to resolve a problem of encoding in a scenario IDOC->JMS. I'm receiving Idoc from R/3 ->XI -with special characters that are not recognized in the target system (WebMethod).
I saw some recommendations on the forum to use anonymizer.encode to switch from UTF-8 to ISO-8859-1 to handle this special characters problem.
In the JMS Adapter (Receiver) I did the following set up :
Module Name : AF_Modules/XMLAnonymizer
Module type - Local Enterprise Bean
Module key - 0
Module configuration:
Module key - 0
Parameter name - anonymizer.encoding
Parameter Value - iso-8859-1
As results, I still see the default encoding and the special characters remain a problem.
<?xml version="1.0" encoding="UTF-8" ?>
Am I missing something on this ? Your help is appreciated.
Regards,
Charles

Hi,
Please try to use this pice of xslt as a last step in mapping.
<xsl:stylesheet version="1.0"
xmlns:xsl="http://www.w3.org/1999/XSL/Transform">
<xsl:output method="xml" encoding="ISO-8859-1"/>
<xsl:template match="/">
<xsl:copy-of select="*" />
</xsl:template>
</xsl:stylesheet>
Best regards,
Wojciech

Similar Messages

Anonymizer encoding

Hi guys,
Relating to Anonymizer enconding I'm having some trouble in using the ISO-8859-1 encoding.
On the JMS channel I've the CCSID set to 00819 and the anonymizer.encoding property set to ISO-8859-1. Nevertheless I'm getting on the message monitoring the following exception:
Anonimizer: failed to anonymized due to java.io.IOException: com.sap.engine.lib.xml.parser.NestedSAXParserException: Fatal Error: com.sap.engine.lib.xml.parser.ParserException: Unsupported character: 41(:main:, row:23, col:33)(:main:, row=23, col=33) -> com.sap.engine.lib.xml.parser.ParserException: Unsupported character: 41(:main:, row:23, col:33)
This exception is related to a special character which appears on row 23, col 33, namely 'Ç' .
Can you guys help me or have any suggestions?

Hi,
As in above post its mentaioned that the Anonymizer encoding can not be used in sender adapter and this possible to use with XI3.0 SP16 or above and PI7.0 or above.
Starting from SAP NetWeaver Exchange Infrastructure 3.0 SP16 you can use this module to change the encoding of an XML document.
The parameter for this purpose is:
anonymizer.encoding = <charset>
You have to define all namespaces and prefixes of the XML document in the
parameter anonymizer.acceptNamespaces to prevent them from being
removed.
More information: SAP Note 880173 - XI 3.0 Adapter Framework XML Anonymizer
Module
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/502991a2-45d9-2910-d99f-8aba5d79fb42
Please I kindly request you to confirm about it.
It is not possible to use this module in the sender JMS or SOAP adapter as this adapter type does not support any additional modules.
Can I request you to once again confirm about the the parameters of the XMLAnonymizerBean
anonymizer.acceptNamespaces
Enter an alternating list of all allowed namespaces and the corresponding prefixes devided by space. If you want a namespace without prefix, enter '' (two single quotes) as prefix. All namespaces which are not in this list are removed from the XML message.
Example: http://namespace1 '' http://namespace2 ns
anonymizer.quote
Enter the character that should be used for attribute quotes, usually ' or "
anonymizer.encoding
Enter the encoding that should be used in the XML declaration, if you want to change the default UTF-8. The XML file is changed to this encoding
Please refer below link to varify the parameters for module XMLAnonymizerBean
/people/stefan.grube/blog/2007/02/02/remove-namespace-prefix-or-change-xml-encoding-with-the-xmlanonymizerbean
Note : the link is for SOAP adapter , but for JMS also you will have same parameters.
Thanks
Swarup
Edited by: Swarup Sawant on Jan 26, 2008 7:37 PM

STRANS encoding in UTF-8

I do a simple transformation of some data and receive an XML. The encoding of this XML is
<?xml version="1.0" encoding="ISO-8859-1"?>
The client wants encoding UTF-8 however.
How can I transform with this encoding?
regards, Léon Hoeneveld

Hi,
by using of Standard xml anonymizer bean
Receiver communication channel --> Module tab --> enter the following data
Module Name = AF_Modules/XMLAnonymizerBean
Module Type = Local Enterprise Bean
Module key = 0
Module Configuration
anonymizer.acceptNamespaces = ABC.interface if
anonymizer.encoding = UTF-8
anonymizer.quote = '
please refre below blog,
http://wiki.sdn.sap.com/wiki/display/XI/ChangingNamespacesandtheencodingformatof+XML
regards,
ganesh.

Encoding issue with " " Less than sign

Hello Experts,
I am working on Receiver Webservice scenario where I am facing issue with "<" less than sign. SAP XI system automatically replace it with "<" sign. I can see the changed value in Audit log of communication channel.
Web service is not able to accept the data and I can see error message in audit log
SOAP: response message contains an error XIAdapter/PARSING/ADAPTER.SOAPEXCEPTION - soap fault: Server was unable to read request. ---> There is an error in XML document (1, 573). ---> The specified node cannot be inserted as the valid child of this node, because the specified node is the wrong type._
When I check the payload in audit log I can see the XML structure properly but as I open it in Notepad I can see character code "<" instead of u201Cless than <u201D symbol.
Audit log XML file is as given below
<?xml version="1.0" encoding="utf-8" ?>
- <ns1:TurnaroundDetail xmlns:ns1="http://isotrak.com/webservices">
<ns1:sessionid>3f2f2592-39d5-456e-8cf2-5d7ee81402c8</ns1:sessionid>
<ns1:data><Request xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"><TurnaroundDetail><PlannedJobDepartureDatesFrom="2011-03-01T12:01:23.00" To="2011-03-01T12:07:10.00"/><DepotReference DepotReference="EASTLEIGH"/><DepotReference DepotReference="CHANDLERS"/></TurnaroundDetail></Request></ns1:data>
</ns1:TurnaroundDetail>
When I open it in notepad I can see converted value
<?xml version='1.0' encoding='utf-8'?>
<TurnaroundDetail xmlns='http://isotrak.com/webservices'><sessionid>dcc4adcd-ce8f-403d-a1cf-01fcc5aab066</sessionid><data><Request xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"><TurnaroundDetail><PlannedJobDepartureDatesFrom="2011-03-02T08:28:29.00" To="2011-03-02T08:38:09.00"/><DepotReference DepotReference="EASTLEIGH"/><DepotReference DepotReference="CHANDLERS"/></TurnaroundDetail></Request></data></TurnaroundDetail>
I hope this is not caused due to AnonymizerBean configured in receiver SOAP comm channel.
anonymizer.acceptNamespaces http://isotrak.com/webservices ''
anonymizer.encoding ISO-8859-1 (also tried utf-8)
anonymizer.quote ''
Could you please suggest if I can get rid of "<" character and get < less than sign? Or it is obvious behaviour by SAP XI system w.r.t Encoding and Receiver end needs to decode this character?
Note: As per Web service requirement whole XML data to be processed by webservice is populated in single Data field. As here we are populating whole XML data file in one field named data
Thanks in advance.
Vinit.

Simply typing "Test <test> test" into a frame and exporting that yields
<ParaStyle:Body>Test \<test\> test
and reading it back into ID gives the expected result.

Adding Encoding in XML header without mapping

Hi Gurus,
I am stuck in a situation where in a pass through scenario, I need to add encoding type in XML header.
Below is example -
Current Situation - <?xml version="1.0"?>
Expected result - <?xml version="1.0" encoding="UTF-8"?>
Can anybody help me in this regard? how to achieve this?
Regards
Vidhi S

Hi Vidhi
Use it in the below way in the receiver adapter.
Module name: AF_Modules/XMLAnonymizerBean
Parameter name: anonymizer.encoding
This will work. I have tested already.

Convert the signed message into base64 code in file receiver adapter

Hi,
I have 2 sequence steps in my scenario.
Step1
I want to convert the message with signed certifcates and send the file with base 64 code format.
Solu:
1.I deployed the certificate in file adapter (The corresponding key/certificate pair must previously be saved in a keystore view of the J2EE server by using the Visual Administrator)
2.for to change the File type content to base 64 code format .
solu:
File type in receiver communication channel is Binary.
please suggest what value i need to provide below
anonymizer.encoding = ?(using the XMLAnonymizerBean in the module tab giving the value
Step2.
after that i wantt to pick up the file with base 64 code format (Which was created in step 1) and place the content to field with xsd type base64 Binary .
for this we can pick up using file adapte or we need to use any module in the sender file module tab of the communication channel?
Please suggest.

HI Hyma,
As Stefan specifyed already as per my knowledge we dont have any standard procedure for all the requirements you specified.....we need to go for module in the adapter.
Cheers!!!
Naveen.

Problem Using XMLAnonymizerBean module in Reciever File adapter.

Hi All,
I am trying to use the XMLAnonymizerBean in orer to convert the encoding of my xml document from UTF8 to ISO. However when I configure the module the message goes into waiting status with an exception saying.
Exception caught by adapter framework: Object not found in lookup of XMLAnonymizerBean..
I have configured the Module in the below manner...
Module Name = AF_Modules/XMLAnonymizerBean
Module Type = Local Enterprise Bean
Under Configuration i Mention
anonymizer.encoding = ISO-8859-1.
is there any thing i am missing, I am on Xi 7.0 SP 08.
Please help...

Thaks for the pointer. Now I dont get any error however i am not getting the desired o/p.
I am trying to change the header of an xml file which I am trying to write from <?xml version="1.0" encoding="utf-8"?> to <?xml version="1.0" encoding="iso-8859-1"?> , as per the help doc this could be changed using the xmlAnonymizerBean.
My output still shows utf-8, Any pointers on thiswould be really appreciated.
Thank you.

IDoc to File - Russian Characters not in UTF-8 format - File Receiver

Hello,
My scenario is Idoc to File. My SAP sender system is a Unicode system and my RFC connection to XI is also set to a unicode connection. My idoc is sent to XI OK and whenever I look at the payload in SXMB_MONI, I see the Russian characters OK, but the problem is when the file gets created.
My receiver system wants the file in UTF-8 format. When the file gets created, the Russian characters are not in UTF-8 encoding format. For example, the Russian chars look like (but without the spaces inbetween): Ð # Ð µ Ñ # Ð ¶ Ð ° Ñ # Ð µ Ð » Ñ ...
Instead, the chars should look like: Держатель
My file type in my file receiver comm channel is binary and I am also using the AF_Modules/XMLAnonymizerBean with anonymizer.encoding of utf-8.
Can someone please help me determine the problem?
Thank you,
Rhonda

Hi Rhonda,
Hope you have set the following for your file receiver adapter :
1. Transfer Mode is set to Binary,
2. File Type Text,
3. Encoding ISO-8859-1( for Western European Latin ).
Inorder to recognize russian Character, try as follows :
Your sender idoc after coming into Pi has XML encoding declaration 'UTF-8'.
Write a simple XSLT mapping to change the value of the attribute "encoding" to "ISO-8859-1" in the output XML of message mapping . Include this XSLT map as the second mapping step in your interface mapping.
First step in your interface mapping will be your already existing message mapping.
An example of the XSL code :
<?xml version='1.0'?>
<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform">
<xsl:output method='xml' encoding='ISO-8859-1' />
<xsl:template match="/">
<xsl:copy-of select="*" />
</xsl:template>
</xsl:stylesheet>
Iam not sure whether Russian language encoding has ISO-8859-2 (Eastern European Latin) or
ISO-8859-1( for Western European Latin )...pls check out !
or you can also do java mapping instead of above mentioned xslt mapping if you are comfortable with java code !
Cheers,
Ram.

Russian Characters not in UTF-8 format - File Receiver

Hello,
My scenario is Idoc to File. My SAP sender system is a Unicode system and my RFC connection to XI is also set to a unicode connection. My idoc is sent to XI ok and whenever I look at the payload in sxmb_moni, I see the Russian characters ok, but the problem is when the file gets created. When the file gets created, the Russian characters are in unicode html encoding representation and not in UTF-8 encoding format. For example, the Russian chars look like (but without the spaces inbetween): & # x 4 1 2 ; & # x 4 2 b ; & # x 4 2 5 ; & # x 4 1 e ; & # x 4 1 4 ; & # x 4 1 d ; & # x 4 1 e ;
My file type in my file receiver comm channel is binary and I am also using the AF_Modules/XMLAnonymizerBean with anonymizer.encoding of utf-8.
Can someone please help me determine the problem?
Thank you,
Rhonda
Edited by: Rhonda Wilcox on Feb 18, 2009 3:14 PM

A simple copy XSLT would help, as XSLT deescapes automatically:
<xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform">
<xsl:output method="xml" omit-xml-declaration="yes"/>

<xsl:template match="*">
<xsl:copy-of select="." />
</xsl:template>
</xsl:stylesheet>
But try to solve the issue in the IDoc sender first.
Regards
Stefan

SOAP RECEIVER: Possible to change the soap header request

Hi
Is it possible to change what is included in the soap header like namespaces (.. xmlns:ns="http://what.com"
Specifically I need to have the "http://Strange.org/thisis.xsd" (see below) included in the header and the <ns:pi-create> included in SOAP-ENV
<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:ns="http://Strange.org/thisis.xsd">
<SOAP-ENV:Body>
<ns:pi-create>
<request>
<request-data>...
</request-data>
</request>
</ns:pi-create>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>
Hope somebody can help
Cheers

Hi Bowie,
1.You can change the Namespace. condition is no obj's under the namesapce then only it's possible otherwise u can't.
2.create a new namesapce what ever u want and copy all the obj's under that namesapce.finally delete the previous one.
XMLAnonymizerBean
Use
You use this module to anonymize XML elements and attributes by removing namespaces or namespace prefixes from the XML document of the main payload.
You can define a particular namespace prefix for each namespace. You can also change the encoding attribute of the XML declaration.
Integration
You can use the module in adapters that can be extended in the module processor.
Activities
Entries in the Processing Sequence
●      Insert the module before the adapter module.
If the adapter comprises multiple modules, for information about the position of the module, see: Extending the Module Chain in the Module Processor
●      Enter the module name AF_Modules/XMLAnonymizerBean.
●      Select the Module Type Local Enterprise Bean.
●      The system proposes a module key.
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.
Example
The anonymizer.acceptNamespaces parameter has the following value:
urn:sap-com:document:sap:rfc:functions rfc urn:sap-com:document:sap:soap:functions:mc-style rfc
●      Payload before using the XMLAnonymizerBean:
<Z_PAYMITEM_GET_LIST
xmlns="urn:sap-com:document:sap:rfc:functions"
xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<I_ACCOUNTIDENT xmlns="">
    <ACCOUNT_NUMBER>0080000094</ACCOUNT_NUMBER>
    <BANK_COUNTRY>DE</BANK_COUNTRY>
    <BANK_COUNTRY_ISO>DE</BANK_COUNTRY_ISO>
</I_ACCOUNTIDENT>
</Z_PAYMITEM_GET_LIST>
●      Payload after using the XMLAnonymizerBean:
<?xml version='1.0' encoding='utf-8'?>
<rfc:Z_PAYMITEM_GET_LIST
xmlns:rfc='urn:sap-com:document:sap:rfc:functions'>
<I_ACCOUNTIDENT>
    <ACCOUNT_NUMBER>0080000094</ACCOUNT_NUMBER>
    <BANK_COUNTRY>DE</BANK_COUNTRY>
    <BANK_COUNTRY_ISO>DE</BANK_COUNTRY_ISO>
</I_ACCOUNTIDENT>
</rfc:Z_PAYMITEM_GET_LIST>
with rgds,
MFH

JDBC adapter , problem in inserting Korean Charaters in MS SQL

Hi ,
We are facing a problem when we are inserting "Koren Charaters" in DB of type MS SQL using JDBC adapter.
What we tryed is:
We found that there is a problem in Code Page Conversion. We tried adding a Modules in Receiver Adapter of type JDBC.
Processing Sequence:
AF_Modules/XMLAnonymizer--Bean Local Enterprise Bean 1
AF_Modules/TextCodepageConversionBean-Bean Local Enterprise Bean-- 2
CallSapAdapter----
Local Enterprise Bean -- 0
Module Configuration:
1 anonymizer.encoding UTF-16
2 Conversion.charset UTF-16.
But we are getting the error in CC as:
"Message processing failed. Cause: com.sap.aii.af.ra.ms.api.RecoverableException: ERROR occured parsing request:com.sap.engine.lib.xml.parser.NestedSAXParserException: Fatal Error: com.sap.engine.lib.xml.parser.ParserException: XMLParser: No data allowed here: (hex) feff, 3c, feff(:main:, row:2, col:6)(:main:, row=2, col=6) -> com.sap.engine.lib.xml.parser.ParserException: XMLParser: No data allowed here: (hex) feff, 3c, feff(:main:, row:2, col:6)"
also should I have to check any patches related to JDBC driver from MS SQL which supports korean Code Page?
Any one who had face this problem pls give us inputs:
Thanks
Shankar

Hi
In the XML sent to the channel you will have to use a special quoting
for any Unicode strings, which the JDBC Adapter will not produce on its
own. Instead, you need to add an attribute 'hasQuot="no"' to those
elements (most likely in the mapping where you produce the XML) and
explicitly enclose the data in single quotes prefixed with the letter N.
For clarity, one example:
If your original "INSERT" operation looks like this:
<StatementName2>
<dbTableName action="INSERT">
<table>realDbTableName</table>
<access>
<col1>val1</col1>
<col2>val2</col2>
</access>
</dbTableName>
</StatementName2>
and "col1" contains Unicode data, change the document as follows:
<StatementName2>
<dbTableName action="INSERT">
<table>realDbTableName</table>
<access>
<col1 hasQuot="no">N'val1'</col1>
<col2>val2</col2>
</access>
</dbTableName>
</StatementName2>
Regards
Shankar

Enclosing characters for namespace in XI

Hi,
I have a file (FCC) to file (XML) scenario. The output that I am getting is a .xml file. When I open the output file in Notepad (text editor) I got the following
<?xml version='1.0' encoding='ISO-8859-1'?>
<if:product xmlns:if='data.interface' xmlns:xsi='http://www.w3.org/2001/XMLSchema-instance' xsi:schemaLocation='data.interface product.xsd'>u2026
but my requirement is as following
<?xml version="1.0" encoding="ISO-8859-1"?>
<if:product xmlns:if="data.interface" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="data.interface product.xsd">u2026
When I open the output file in XML editor then the character " is coming but when I open the same file in text editor character ' is coming.
Please provide some solution to get the enclosing character " always (in both xml editor and text editor) .
PS: I have also used the XML anonymizer for
anonymizer.encoding = ISO-8859-1
anonymizer.quote = "
Regards,
Madan Agrawal

The way you are looking at the file is always depends on how the editor is showing it on the screen. Though both the editors are showing different characters, the character might be the same internally. At the command prompt, use the command type <file name with full path>. You will see exactly what is in the file. Best thing would be to give the file to you end point people and ask them if it is what they wanted.
VJ

XML file header Section

Hi XI Experts ,
Scenario : RFC (SAP ) - >XI -> HTTPS connection to a EXternal Server .
Csutomer wants the : The XML version and character set should be described as: version 1.0, character set GBK.
Sample: <?xml version="1.0" encoding="GBK"?>
BUt the usual xml format generated is : <?xml version="1.0" encoding="UTF-8"?>
How do we cahnge the xml standard format to : <?xml version="1.0" encoding="GBK " in XI ?
Kindly suggest .
Thank you ,
Varalakshmi

Hi,
You can use SOAP adapter with do not use SOAP envelope option.
And in Receiver adapter use standard module XMLAnnomizer Bean to chenge the encoding
refer
anonymizer.encoding
To use a code page other than UTF-8, enter it. The parameter is optional.
For example, enter ISO-8859-1.
http://help.sap.com/saphelp_nw04/helpdata/en/45/d169186a29570ae10000000a114a6b/content.htm
/people/stefan.grube/blog/2007/02/02/remove-namespace-prefix-or-change-xml-encoding-with-the-xmlanonymizerbean

How the XmlAnonymizerBean work??

Hello experts,
Can somebody help me understand how XmlAnonymizerBean work.
Does it simply replace the characterset/encoding type of the XML message with the one specified in the anonymizer.encoding parametes.Or can it read the payload to identify the encoding type and then replace the xml encoding attribute??
It woudl be great if somebody can explain me this senario with reference to JMS adapter.
- Rajan

Hello Stefan.
Thanks for the useful information!!
Could you please help me with the scenario where I want to overwrite the encoding type of the message based on the payload contents OR at the minimum based on the sender/receiver attribute in the message. Is there any standard adapter module available or can this logic be put in a custom module?
Thanks once again for all your help.
- Rajan

Anonymizer Bean is not working XML file -- ABAP Proxy scenario.

Hi Experts,
Can anybody please help, How can add this line <ns0:ROOT xmlns:ns0="urn:XXX:snc:productactivedata"> to my input xml file?
</ns0:ROOT> to the end of the input xml file. One more thing please, how to remove "standalone="yes" " from this line <?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
I have tried with Anonymizer bean settings, I can't able to achieve this, with XSLT mapping could, but I don't know XSLT mapping, can any one help me in this?
Many Thanks
Regards
San

Hi Prateek,
If do, like remove namespace in the message type then i get this error.
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>XIServer</SAP:Category>
<SAP:Code area="MAPPING">GENERIC</SAP:Code>
<SAP:P1>com/sap/xi/tf/_MM_EDI_ProAct_One_N_</SAP:P1>
<SAP:P2>com.sap.aii.utilxi.misc.api.BaseRuntimeException:</SAP:P2>
<SAP:P3>The element type "D01_PO4" must be terminated by t</SAP:P3>
<SAP:P4>he matching end-tag "</D01_PO4>".</SAP:P4>
<SAP:AdditionalText />
<SAP:Stack>com/sap/xi/tf/_MM_EDI_ProAct_One_N_com.sap.aii.utilxi.misc.api.BaseRuntimeException:The element type "D01_PO4" must be terminated by the matching end-tag "</D01_PO4>".</SAP:Stack>
I have checked the message, xml message format fine. Any help in this please?
Thanks & Regards
San

Anonymizer.encode

Similar Messages

Maybe you are looking for