One of the issue I got recently while publishing data from OSB 11g to MQ Queue which always publishes message in Byte format.
Using HermesJMS Queue Browser for MQ queue basically was able to see messages in byte format.
Though My BusinessService(Messaging Service>>Request Message Type (Text)) for publishing the messages on the MQ queue always publishes the messages in bytes and not in Text. Even when I tried to change it to text i still get the messages in the bytes format.
Reason:-
mq transport is not able to parse JMS headers . if u sending message from any jms client like Hermes it would have jms headers with the message and mq transport would fail to validate the payload
Workaround:-
I added the below RFH2 Headers as part of mq Transport Header using Transport Header activity in OSB,so basically Hermes JMS was able to intercept the RFH2 headers and display the payload in text format in Queue Browser.
'<RFH2Header>
<mcd><Msd>jms_text</Msd></mcd>
</RFH2Header>'
Using HermesJMS Queue Browser for MQ queue basically was able to see messages in byte format.
Though My BusinessService(Messaging Service>>Request Message Type (Text)) for publishing the messages on the MQ queue always publishes the messages in bytes and not in Text. Even when I tried to change it to text i still get the messages in the bytes format.
Reason:-
mq transport is not able to parse JMS headers . if u sending message from any jms client like Hermes it would have jms headers with the message and mq transport would fail to validate the payload
Workaround:-
I added the below RFH2 Headers as part of mq Transport Header using Transport Header activity in OSB,so basically Hermes JMS was able to intercept the RFH2 headers and display the payload in text format in Queue Browser.
'<RFH2Header>
<mcd><Msd>jms_text</Msd></mcd>
</RFH2Header>'
No comments:
Post a Comment