I'm working on a project where the app team is using a vendor product to interface with JMS to get to IBM MQ (in this case). Everything is configured thru the vendor product's GUI config panels. On the output "node" they have a field for the Message Queue name. The app team is successfully able to populate this field with the Reply To Queue from the request and use it on the output of the Reply message.
But they cannot get the product to respect the queue manager name. We are using the following link to determine how a JMS app can provide the destination queue manager name.
Creating destinations in a JMS applicationSo far every combination of the following that we have tried:
queue://[ qMgrName ]/qName
Is taken quite literally by the vendor product as the name of the destination queue. I can tell this based on the Local Events being captured by the queue manager they are connecting to.
If this vendor product truly does not allow for a destination queue manager name to be used on its iteration of MQOPEN to MQPUT
A. Does this product have a defect working with IBM MQ but not necessarily other JMS compliant messaging systems?
B. Or does this product have a defect with basic JMS 2.0 requirements?
------------------------------
Peter Potkay
------------------------------