Handing special characters in JMS Channels

Dear Experts,
In a specific scenario(JMS - IDOC), we are getting the below characters in th source XML.
XML message is being uploaded to a MQ queue, from where JMS channel of XI extracts the message and moves it forward to the mapping.
The characters are
²&é "'(§è !çà)-²1234567890°_
!¿§$%&/()=?´1234567890ß`¿@²³{[]}^°
When we try to view the message data in the source JMS channels,
It says, XML contains a invalid character. Because of which it is not able to display the source msg.
But when we process the same XML using a file channel.Everything gets translated properly.
Is this the problem with MQ/JMS settings etc...???
Kindly share your experience and comments on this issue.
Thanks in advance,
Younus

Hi,
Check if the solution mentioned in this thread helps you:
Re: Problem with special character like u00E5,u00E4 u00F6 in Sender JMS Adapter
Re: Special Characters not showing correctly in XI from JMS Adapter.
Regards,
Abhishek.

Similar Messages

Problems with charset encoding using sender JMS channel

Hi all,
We are connecting an AS400/WebSphere, with SAP via XI (PI7.0), by means of JMS adapter.
Situation: we are sending a message through a JMS sender channel from WebSphere to XI.
The problem occurs if the message has special characters (like client name). The contents of the XI message became wrong on those characters (they are replaced by '#'), sending invalid information to SAP.
The character set CCSID of the WebSphere is 00037.
Can anyone help me on overcoming this problem?
thanks in advance.

thanks Stefan,
>> What kind of mapping do you use?
We are using a graphical mapping that maps the incoming message to an IDOC message definiton.
>> Is the payload wrong after the mapping?
The mapping ends with success and the payload is well formated, but the content of the final message is wrong (just on the special chars) (ex: the ã is replaced by #).
>> Where do you send that message to?
The message is an IDoc that is send to SAP:
best regards.

SSRS and data from SharePoint lists - special characters in HTML

Hi All,
This may not actually fit into this forum, but here goes anyway...
We're using SSRS to report on data stored in Project Server workspaces (so SharePoint lists). Prior to upgrading to 2013, we could pull this data in and set the "Placeholder properties" of the text box to interpret HTML tags as styles and it would
format everything as it appeared in the SharePoint list. Now that we have upgraded to 2013, this works with a few notable exceptions - some special characters are rendered as their escaped/encoded (whatever the term is) - so a colon which is within the text
field in SharePoint, rather than appearing in the SSRS report as ":" appears as ":".
These are multiline, rich text formatted columns in the SharePoint list. Using =Replace(Fields!Description.Value,":",":") in the report makes the appropriate replacement, but given that this occurs with a handful of other special
characters as well, this solution becomes very unruley very quickly. Has anyone else encountered this, or does anyone have any other suggestions for a work around?
If not now, when?

Facing same issue but having no solution, please suggest..

Mapping error because of special characters

Hello,
We are extracting data from SAP system and sending it thru XI to 3rd party system (writing xml files on to file server).
Now, because of presence of few special characters in the data, there is a mapping exception error in XI.
The data which is causing the issue is "ABRANCENTRO MEDIAÇÃO IMOBILIÁRIA".
In SXMB_MONI, i see that this is failing is Request Message mapping step.
We can not remove special characters as this is master data. How can i fix this issue?
DO i need to use any modules in communication channel for this purpose?
Any leads are highly appreciated.
Thanks,
Chandra

Hi Chandra,
an UDF cant help you assumedly coz that characters lead to "not wellformed" XML. Any parser would complain about that. So the PI parser would throw an error before executing the UDF.
The question is: what does the receiver expect? You wrote you like to write xml files to a server. But if the XML is not wellformed, the receiver would not be able to parse them, and therefore usually not able to process them.
If you really want to create such a file (not wellformed XML) you can create that with a not parsing mapping (ABAP or Java). So you map the message just with string operations. This is not very recommentable and only possible for very simple mapping cases.
Regards,
Udo

Special Characters problem in PI 7.1

Hi,
We have simple integration from R3 to JMS. from R3, idocs contain special characters, and they are getting converted in to different chanracters in integration engine. So making the output data currupted.
I tested the same message in mapping test tool and the target message contains actual special charcters. Below is the example,
Input:
i was thinking of using XMLAnonymizer, but the problem is in integration engine itself. I can see invalid output in SXMB_MONI.
so could some one help me how can i fix this issue?
Many thanks in advance.
Regards,
Prasad..

Hello,
Please check this document to sort out your issue:
How to Work with Character Encodings in Process Integration (NW7.0):
http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/502991a2-45d9-2910-d99f-8aba5d79fb42
Br,
Dzmitry

Special characters in XML built using the DOM object

I am using the DOM object to build xml but I am having problems with special characters. I have a Element object that I create attributes in. Most special characters like the &, ", or ' are translated for me (amp; quot;, acute; put a & in front of those, if I do it here the browser will translate them into the logical character) but I am having a problem with the � character. The DOM object does not translate this. If I do it my self to(eacute; same here add a & in front) before adding the string to the attribute then the DOM object translates it to (amp;eacute; add a & in front of the amp; not in front of the eacute;). As you can see the DOM object translates the & instead of recognizing that it is a HTML character. Can anyone give me a hand?

I am building this XML in a servlet so ,right, DOM does process XML (even though a valid HTML file can be loaded into a DOM object) but if you build XML using DOM then write the XML out using PrintWriter and Transformer objects this will cause the XML to print out in your browser. If you view source on this XML you will see that the DOM object has translated all special characters to there &xxxx; equivalent. For a example: when the string (I know "cool" java) gets loaded into a attribute using the DOM object then wrote back out it looks like (I know &xxx;cool&xxx; java) if you view the source in your browser. This is what it should do, but the DOM object is not change the � to the "&xxxxx;". This servlet is acting as a gateway between a Java API and a windows asp. The asp will call the servlet expecting to get XML back and load it directly into a DOM object. When the windows DOM object gets the xml that I am returning in this servlet is throws a exception "invalid character" because the � was not translated to &xxxx; like the other characters were. According to the book HTML 4 in 24 hours (and other references) the eacute; or #233; are how you say "�" in HTML or XML. How do you say it?

Special Characters in imported HTML

I've got a Flash piece where the user fills out a
questionnaire, and based on their responses, they are shown a
handful of recommendations. These recommendations are all separate
HTML files that load into a scrolling text field as HTML text.
There is an English version and a Spanish version. The
English version works fine.
In the Spanish version, on the other hand, we've got special
characters such as accents over e's, tildes over n's, and so forth.
In the HTML, I've used codes for special characters, such as
ñ for ñ. That didn't work. In the resulting
recommendations, this code appears, not the ñ.
Then I tried just putting the special characters into the
HTML, without the special code. That looks fine on my computer (Mac
G5 running Firefox), but on Windows IE instead of the special
characters, we get one of those diamond shapes with a "?" in the
middle of it.
In my recommendations field, I have it set to embed all
characters. The font is Verdana, which should include the special
characters. Does anyone know if the display of special characters
in Flash is possible, and how I would do it?

add <?xml version="1.0" encoding="UTF-8"?> tag to 1st
line of your xml, AND
save your xml file encoding as utf-8, if you are using
notepad, try this:
- save as, change the encoding (the bottom field) to UTF-8
no worry about your file extension.
UTF-8 (8-bit Unicode Transformation Format) supports multiple
languages.
good luck

Special Characters in the payload

Hi,
We are receiving Payload from Source Service Provider with some special characters â€œ and â€? as shown below:
â€œMaintenance Documentation Libraryâ€? under â€œTransformer Bushings Surveyâ€?
Those Special Characters are actually double quotes.
“Maintenance Documentation Library” under “Transformer Bushings Survey” .
PI While reading the payload is taking it as a special character. JMS is the sender adapter we are using.
Is there any way to handle this without writing any module or Java Mapping??
Regards
Srilatha

Hi Srilatha,
You can try to change the character encoding with the standard modules like this document point out: http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/502991a2-45d9-2910-d99f-8aba5d79fb42?overridelayout=t…
From my own experience it is more useful to have a general java mapping to avoid this problem and to use it in all the required scenarios-
Regards.

Multi languages and Special Characters in PI

Hi gurus
Different languages data will be coming from the source xml file and PI has to handle that data and send it to ECC system throguh IDoc Receiver Adapter.
.our scenario is MDM to R/3. Pi file adapter is picking the xml file from source directory path.
the file encoding we have used is "ISo-8859" file type as "TEXT", we have also tried checking by giving the file name as"Binary", but we are still facing the issue.
The special characters which are showing up are Å#Ã³
i was trying to look at the below mentoined blog , but that blog was not availiale in sdn.
http://www.sdn.sap.com/irj/scn/weblogs?blog=/pub/wlg/9420 [original link is broken]
thanx in advance

> i tiried as you suggested, but i do not have the access for the RFC destination in R/3 server.
I mean the RFC destination in PI, not in R/3
> i have a doubt here
> In the xml file received by PI, the entire data will be in English, only for two particular fields the data will be in Foreign Languages(russian,greek or any other langauge).The fields are maintained under International Version Segement.
You have to split the XML, create different IDocs by language and choose an IDoc receiver channel with tied RFC logon language
see SAP note 745030
The customer should consider to use a unicode R/3 system when he wants to use different language descriptions.
In a non-unicode system the texts from other languages cannot be read, for example the greek characters cannot be displayed when logging on in russian. In a unicode system there is no restriction.

Problems with special characters in InputStream or XPath

Hello everyone,
I am having problems with special characters such as ", ', - and so on, everything becomes ? (questionmark). (Not with special nordic characthers (å,æ,ø) though.)
The encoding of the XML is UTF-8, and the server that holds the webservice is setting encoding to UTF-8 also, so no conflict there.
What I have done is something like this:
{code}
String url = "http://www.formula1.com/rss/news/latest.rss"; // This is not the feed I use, it is a custom XML document
InputSource is = new InputSource(url);
DocumentBuilderFactory fct = DocumentBuilderFactory.newInstance();
DocumentBuilder builder = fct.newDocumentBuilder();
Document doc = builder.parse(is);
Element rootElement = doc.getDocumentElement();
XPathFactory factory = XPathFactory.newInstance();
XPath xPath = factory.newXPath();
out.print(xPath.evaluate("/rss/channel/title", rootElement)); // The xml is not a RSS feed, this is just an example.
{code}
Please let me know what I am doing wrong, or give me a hint of how to solve this in another way.
Best regards,
G.Hansen
Edited by: G.Hansen on Mar 24, 2009 2:39 AM

Hello, thanks for you reply. I had to rewrite your code a little, and I think that your code would not really compile, if you tried yourself :-)
I ended up with something like this:
our environment is running in 1.4 mode, so I could not use the for-each loop :-(
public String printEntities(String s) {
     char[] sArray = s.toCharArray();
     StringBuffer sb = new StringBuffer();
       for (int i = 0; i < sArray.length; i++) {
         if (sArray[i] > 256)
              sb.append("&#x" + Integer.toHexString(sArray) + ";");
     } else
          sb.append(sArray[i]);
     return sb.toString();

Metadata special characters problem

You would be forgiven for thinking it easy to add a caption for each image to identify the photographer and her credentials. Metadata is there for that purpose and the IPTC "Author" field seems an obvious choice.
However, most letters-after-your-name will contain special characters eg.
Gordon Bennett FRPS; MPAGB; EFIAP/b.
and these cause huge problems to the Adobe products that seem to have gone un guided.
If these are entered into the Metadata in the File Info panel in say Photoshop or Bridge they are recorded correctly. When reading the Metadata from file in Lightroom (Vista version) however, only the text up to the first semicolon in the above example is transferred. The same problem occurs with the slash. Thus all the Lightroom modules work on incomplete data.
(I have neither special character set as a keyword seperator in Preferences).
Is there some coding tag that can be wrapped round this text to ensure it is published correctly by the web module ?

Hi Kenneth,
Thanks very much for your comments.
In Preferences>File Handing I have de-selected the option to have Lightroom use forward slash as a keyword seperator. My understanding is that therefore it should not do so.
Do you mean that Vista overrides this? or is it simply the Vista version of Lightroom that is doing it.
I had noticed that if a comma is used to seperate keywords that both Bridge and Photoshop replaces them with semicolons and it seems that you cannot prevent this.
Do you know something about how this mechanism works and if it can be varied?
As for an answer to your question of "what shows up in the fileds" I don't think you can tell. Although you can in Bridge/Photoshop by examining the File Info panel, in Lightroom it just disappears into the "catalogue" and cannot be examined. It is displayed of course in the Lr metadata panel but that is where we started, with truncated fields !! However if you save the apparently truncated metadata xmp in Lr then force a read again in Bridge, the full data seems to still be there. Thus it would seem this is a problem specific to Lr and the way it displays metadata containing special characters.
Any further info on the Vista issue would be very welcome.

File Content Conversion (receiver) and special characters

Hi all,
I have a scenario that has a file receiver channel with content conversion. The record structure in the flat file is field-width delimited (hence no field separator) and the parameter 'fieldLengthTooShortHandling' has the value 'Cut' because the receiving system needs only specific widths for the fields. Hence if the field value exceeds the length permitted, the extra characters are clipped.
I observed that some characters are not handled properly while creating the text file. For example, one of the fields contained a "minus" character (not the hyphen). The flat file was created successfully. I opened the file in notepad and found that the "minus" character has appeared correctly and the column count in that record was as expected. However when the same file was opened in Textpad, the minus character was displayed as â | | ('a' with caret, bar, bar) So, all the fields after this field were shifted ahead by 2 characters and hence the total column count of the record had gone beyond the actual one.
All this started due to the error reported by the receiver system which processes the flat file. Due to shift of characters in the flat file, the processing failed. Moreover that system cannot process the special characters (like minus or non-Latin accented characters etc.) So although there is no issue in XI interface as such, I just want to know if anyone has more informtion on why the characters are displayed differently as mentioned above.
Regards,
Shankar

Define data type like
order_recordset
order_row 1..unbound
f1
f2
All are same except communication channel configuration,
Message Protcol : File content select, then below you got additional parameters.
there you fill
Document name : Your sender message type.
Document namespace : Give your scenario namespace
Recordset name : order_recordset ( mentioned in the data type)
Recordset structure : order_row, *
Name Value
order_recordset.fieldSeparator : 'nl'
order_row.fieldSeparator : ,
order_row.endSeparator : 'nl'
based on your text file you fill the above parameter values.

How can I put non-English characters onto JMS queues?

Hi
I am posting XML documents onto a JMS queue configured in a WLS domain. The XML doc is UTF-8 but WebLogic does not seem able to handle the advanced characters and shows them as 2 chars each (such as umlauts). How can I configure WebLogic to handle such special characters?
Any help greatly appreciated,
Craig

In order to send an XML message we need to use Interface XMLMessage and send the message by setDocument(Document document) .
In the document set the content of the message to the DOM document. If we follow this procedure I guess there should not be any issue.
Regards,
hy

Special characters in UTF-8 UNIX file

We have a program which downloads data from certain info-types in to the UNIX file, Fields are written to the specific position in the UNIX file. Some of the fields contains "Special Characters" in them.
When we download the file in UTF-8 mode (encoding default) then the file display special characters correctly but the all the characters in that record gets shifted to left.
When we download the file in ANSI mode then the file display doesn't special characters correctly but the all the characters in that record do not get shifted from their place.
How can i find the special character in the field and accordingly i will shift the field right so that in the final UNIX file field won't shift their positions.

Hi Ramnivas.
Have you tried to read the characters with class: CL_ABAP_CHAR_UTILITIES (transaction SE24, label Attributes)
For example you can see # in ABAP but in the file will be a new line or a carriage return, you can detect that an adapt it with:
CL_ABAP_CHAR_UTILITIES=>NEWLINE or CL_ABAP_CHAR_UTILITIES=>CR_LF
Other hand, if you are using OPEN DATASET to download the file, look at the options of encoding
See F1 of OPEN DATASET and then encoding..
OPEN DATASET - encoding
Syntax
... ENCODING { DEFAULT
| {UTF-8 [SKIPPING|WITH BYTE-ORDER MARK]}
| NON-UNICODE } ... .
Hope it helps
Regards.
Alfonso.

Special characters & picture frames do not appear when site is loaded

When I publish my "new" site to a folder and open it everything looks fine; however, when I upload the site to my server, all special characters (bullets, apostrophes, quotes, tabs, etc. along with picture frames show up as ??? or squares. Checked in Foxfire and Safari; no difference between browsers. Note: used iWeb SEO.
Any ideas what's going wrong and how to fix it?

What's the URL of your site so we can examine it first hand? I've no experience with either of those apps. I use Web Site Maestro for optimizing and uploading my sites. It works very well.
Roddy, iWeb for Musicians, uses the sitemap automator. He has a page or two on tips at SEO.

Handing special characters in JMS Channels

Similar Messages

Maybe you are looking for