Mailing-List: contact users-help@camel.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@camel.apache.org
Received-SPF: softfail (athena.apache.org: transitioning domain of
 clint.petty@ionep.com does not designate 162.253.133.43 as permitted sender)
Date: Tue, 2 Dec 2014 09:56:27 -0700 (MST)
From: clinton <clint.petty@ionep.com>
To: users@camel.apache.org
Message-ID: <1417539387750-5759965.post@n5.nabble.com>
In-Reply-To: <1417539078130-5759964.post@n5.nabble.com>
References: <1417469450728-5759882.post@n5.nabble.com>
 <1417539078130-5759964.post@n5.nabble.com>
Subject: Re: JMS Put to WebsphereMQ destionation using a Qmgr name - how to
 specify?
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

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.