How to change the Message ID's format from hex to string in MQMD when using TIBCO ActiveMatrix Adapter for WebSphere MQ.
Article ID: KB0093058
Updated On:
| Products | Versions |
|---|---|
| TIBCO ActiveMatrix Adapter for Websphere MQ | - |
| Not Applicable | - |
Description
Description:
If we directly set hex string for the Message ID field of MQMD, the Message ID in MQ Queue is not different from what is set in the BW process.
If we directly set hex string for the Message ID field of MQMD, the Message ID in MQ Queue is not different from what is set in the BW process.
Issue/Introduction
How to change the Message ID's format from hex to string in MQMD when using TIBCO ActiveMatrix Adapter for WebSphere MQ.
Environment
Product: TIBCO Adapter for MQSeries
Version: 6.2.x
OS: All
--------------------
Resolution
Make sure that you can see the Message ID field in the BW process. To do that, you need to make sure the schema includes the MQSeriesHeader schema. Second, if the type of Message ID is string, you could use the function tib:hex-to-string("HEX STRING", "ENCODING")
For example, your TIBCO project encoding is ISO8859-1, your HEX string is 414D5120414D535944393120202020204D7AE1A02121640B, the result for message id field should be
tib:hex-to-string("414D5120414D535944393120202020204D7AE1A02121640B", "ISO8859-1"). Note that the hex string should be 48 characters.
For example, your TIBCO project encoding is ISO8859-1, your HEX string is 414D5120414D535944393120202020204D7AE1A02121640B, the result for message id field should be
tib:hex-to-string("414D5120414D535944393120202020204D7AE1A02121640B", "ISO8859-1"). Note that the hex string should be 48 characters.
Feedback
Yes
No
Powered by
