Thank you for responding edhansen42 and Henrique ed, if a "remote q def" is setup on the local qmgr, you are right that I would not need to reference the remote queue manager name. However, that requires admin activity on the local qmgr to keep it in sync with the remote one, and worse, usually these queue names (for reply-to type process) are dynamic, so an admin action isn't feasible. WMQ will route anything it doesn't see a home for locally, to the "transmit" queue that carries a name matching the Qmgr I indicate. This transmit queue is the staging for the connection to the target qmgr, which will actually enqueue the msg to the queue I name. thanks again.
-- View this message in context: http://camel.465427.n5.nabble.com/JMS-Put-to-WebsphereMQ-destionation-using-a-Qmgr-name-how-to-specify-tp5759882p5759965.html Sent from the Camel - Users mailing list archive at Nabble.com.
