on 09-30-2015 8:49 PM
Hi Experts,
We have a JMS to IDOC scenario.
We are receiving special characters in PI which are giving below error message in SXMB_MONI. When I am putting the payload in ESR in my message mapping I am not seeing any error (as i think they are skipping parsing step there.)
The special characters are some weird non-English characters and symbols.
The same characters are processed without any issue in another interface in which we are receiving messages through REST adapter.
Can you please tell me how to pass these character to target without failure during parsing ?
P.S. I have gone through nearly 50 other articles on SCN regarding similar issues but am not finding anything similar to what I am facing.
Saurabh,
Please download payload from SXMB_MONI and attach it here. We can see which character is creating the issue.
Right click on payload and select download, save it as payload.txt.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Saurabh --
Have you already tried "iso-8859-1" encoding rather than UTF-8 ?
just check below if it helps --
If you have already tried this and doesn't favored you; most likely the architecture need to be changed rather than using JMS think of shifting to SOAP if possible.
Regards,
Anudeep
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
refer thread - Problem in JMS-Adapter with CharacterSet Websph... | SCN
what type of JMS transport proctocol used? is it MQ series?
are you able to see the spl characters in Payload??
can you try set the character set id CCSID in sender channel as the required format..
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 | |
10 | |
10 | |
9 | |
7 | |
7 | |
6 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.