Hi All,
We have a requirement where we need to read messages from a Remote MQ in OSB. We have created a MQ resource for the connection and updated the following details.
Connection Type - tcp mode
MQ Host name - <<Remote>>
MQ Port number - <<Port>>
MQ Queue Manager Name - <<QUEUE.MANAGER>>
Queue Manager CCSID -
MQ Queue Manager Channel Name - <<CHANNEL NAME>>
MQ Version - 7.0
MQ Connection Pool Size - 10
MQ Connection Timeout - 1800
MQ Connection Max Wait Time - 3000
Created proxy service with Request Message Type as Text and Response Message Type as None.
I can see that my proxy is able to read the messages from MQ successfully, but is failing with unable to parse error.
I have observed following issues when I printed the Inbound variable and body.
1. Inbound variable structure – the headers values are getting base64 transformed, even if the source system is sending the normal values. The characterset is coming is 1200, even if the source system is sending the encoding as UTF-8 (1208)
<tran:headers xsi:type="mq:MQRequestHeaders" xmlns:tran="http://www.bea.com/wli/sb/transports">
<mq:AccountingToken>FgEFFQAAABUlr0cnx/VtQxcKMuumAgAAAAAAAAAAAAs=</mq:AccountingToken>
<mq:ApplicationIdData/>
<mq:ApplicationOriginData/>
<mq:BackoutCount>545</mq:BackoutCount>
<mq:CharacterSet>1200</mq:CharacterSet>
<mq:CorrelationId>AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA</mq:CorrelationId>
<mq:Encoding>546</mq:Encoding>
<mq:Expiry>-1</mq:Expiry>
<mq:Feedback>0</mq:Feedback>
<mq:Format>MQSTR</mq:Format>
<mq:GroupId>AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA</mq:GroupId>
<mq:MessageFlags>0</mq:MessageFlags>
<mq:MessageId>MzcwMzgxOAAAAAAAAAAAAAAAAAAAAAAA</mq:MessageId>
2. Incoming body is coming in the below format. Every character is being appended by ^@.
<^@?^@x^@m^@l^@ ^@v^@e^@r^@s^@i^@o^@n^@=^@"^@1^@.^@0^@"^@ ^@e^@n^@c^@o^@d^@i^@n^@g^@=^@"^@u^@t^@f^@-^@8^@"^@?^@>^@^M^@
^@<^@t^@e^@s^@t^@>^@^M^@
^@ ^@ ^@<^@d^@a^@t^@a^@/^@>^@^M^@
^@<^@/^@t^@e^@s^@t^@>^@^M^@
Removing ^@ shows actual xml -
<?xml version="1.0" encoding="utf-8"?>^M
<test>^M
<data/>^M
</test>^M
Please let me know if something need to be configured for us to read the message properly.