I was trying to send a PDF file to Receiver JMS adapter without using Integration Repository development in same manner as explined in the blog.

So I did the configuration part and started testing my scenario but it didn’t turn well. The scenario in terms of communication was successful but MQ team wasn’t able to receive the payload properly. They were always getting the XI message paylod as “JMS String”.

Finally, after doing some research we found the solution. Actually the the default value of MQ is MQSTR and because that it was causing to convert the payload into JMS String and because of that MQ team was not able to receive the payload properly. MQ team asked us to send the paylod as bytes and that did the trick. 🙂

So, here are the configuration steps done in Receiver JMS Adapter to solve the problem.

Basically there are two things which we done to prevent the paylod to convert into JMS String.