Extra characters appended to messageId mqproperties
Article ID: KB0079845
Updated On:
| Products | Versions |
|---|---|
| TIBCO ActiveMatrix BusinessWorks Plug-in for IBM MQ | - |
Description
User wants to put a message on an MQ queue with a MessageID using the function tib:string-to-base64() through the WebSphere MQ Put Activity of the MQ Plugin. On receiving it in another BW process using WebSphere MQ Listener Start activity/Get activity, the field's values receives extra "A" characters that are appended at the end of the MessageID.
Sample Scenario :-
String: 1234567890
Input Binary value: 31323334353637383930
Output of other BW processes using the WebSphere MQ Listener Start activity/Get activity, the field's values received are as follows.
Output binary: 31323334353637383930AAAAAAAAAAAA
The extra "A" characters are appended at the end of the MessageID.
Environment
Business Works, MQ Plugin.
Resolution
As per TIBCO's product documentation, users have to use base64 when giving a MessageID. Users can use the following function in the mapper activity to cut off the string in the MessageID starting with the "A" characters.
substring-before($[Activity]/InteractionOutput/mqproperties/messageId, "A")
FIle (Filename: Sample project.zip ) is attached for reference.
substring-before($[Activity]/InteractionOutput/mqproperties/messageId, "A")
FIle (Filename: Sample project.zip ) is attached for reference.
Issue/Introduction
Extra characters appended to MessageID mqproperties .
Was this article helpful?
Yes
No
Powered by
