on 05-23-2016 8:30 AM
Hello Experts,
Greetings for the day!!!!
I have scenario from ECC to Legacy system with PI as a middle ware. The data structure would be IDoc--> PI-->JMS(Queue). Unfortunately, during testing special characters are added with flat data. I have added the setting in the communication channel with 819 as CCSID and ISO-8859-1 parameter in the additional parameters section but ended in the same situation.Here are the below screen shots of the same.
CCSID setting:
ISO-8859-1Setting:
Output received in the Legacy system after flat data with special characters:
Would request you to kindly help on the same so that i can proceed further with same.
Thanks in advance!!!
Many Thanks,
Best Regards,
Prashanth Bharadwaj Ch.
Hi Vila/Hi Harish/Hello All,
I have tried all the above settings as per your earlier blog but ended in error situation of Unsupported encoding Exception.Here are the below screenshots for your reference.
Trial 1 without adding call sap adapter:
Error in PI with Unsupported encoding exception:
Trial 2 adding call sap adapter:
Error in PI with Unsupported encoding exception:
Trial 3 with parameter JMS.XIMessage.charset:
PI result after the above trial 3:
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Prashanth,
your module configuration has the following issues
1. you need to define two module key for Message transform bean
a. One for Code page
b. One for XML2Plain conversion
The codepage module should be before the code page conversion bean.
Number | Module Name | Type | Module Key |
---|---|---|---|
1 | AF_Modules/MessageTransformBean | Local Enterprise Bean | Codepage |
2 | AF_Modules/TextCodepageConversionBean | Local Enterprise Bean | Convert |
3 | AF_Modules/MessageTransformBean | Local Enterprise Bean | XML2Plain |
regards,
Harish
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Vila/Hi Harish,
Thank you so much for your replies. I will try it and update as soon as possible.
Thanks alot again.
Many Thanks,
Best Regards,
Prashanth Bharadwaj Ch.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Prashanth,
Did you try with message transform bean?
Number | Module Name | Type | Module Key |
---|---|---|---|
1 | AF_Modules/MessageTransformBean | Local Enterprise Bean | Codepage |
2 | AF_Modules/TextCodepageConversionBean | Local Enterprise Bean | Convert |
3 | localejbs/CallSapAdapter | Local Enterprise Bean | entry |
Module Key | Parameter Name | Parameter Value |
---|---|---|
Codepage | Transform.ContentType | text/plain;utf-8 |
Convert | Conversion.charset | charset=ISO-8859-1 |
Please try the above module in the channel.
regards,
Harish
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Prashanth,
Have you tried with the parameter JMS.XIMessage.charset ?
Regards.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
80 | |
24 | |
11 | |
9 | |
7 | |
6 | |
5 | |
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.