Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

Encoding issue while sending message to MQ server



We have requirement to connect to external MQ Server using Connect-JMS rule of Pega. The Request and Response message sent to the MQ server should be encoded with Thai Character set "TIS-620". By default Pega uses "UTF-8 without BOM" encoding while sending out Request message in Connect-JMS rule. How do we encode the request message to "TIS-620" format before sending message to MQ Server using Connect-JMS?

Error Messages

1. Sample Request Message constructed in Pega containing Thai Characters <APPL_REF_NO>S20150114/111111111111111 /2222222222222|ยินดีต้อนรับาย|ยินดีต้อนรับ|ยินดีต้อนรับอรี่|S11111|0249|N|1980-02-14|15.21.49</APPL_REF_NO> 2. Sample Request Message received by MQ Server after calling Connect-JMS rule <APPL_REF_NO>S20150114/111111111111111 /2222222222222|เธยินดีต้อนรับ|เธžยินดีต้อนรับˆยินดีต้อนรับ|เธเธยินดีต้อนรับ|S11111|0249|N|1980-02-14|15.21.49</APPL_REF_NO> In the above message the Thai characters received by the MQ server were corrupted. The message should be sent to MQ in TIS-620 encoding only.

Steps to Reproduce

1. Create Connector Activity 2. Create a Request message 3. Call Connect-JMS rule by passing the request message

Root Cause

The root cause of this issue was due to invalid message Properties set to the JMS Queue. Character Set identifier not set with any values.


Set the Message properties - Character Set identifier in MQ understandable format i.e. “874” in message properties.

Published January 31, 2016 - Updated October 8, 2020

Was this useful?

0% found this useful

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us