When you compared the times, was it how long it took your MQPUT to complete, or was it how long it took before the message was actually available on the destination queue? Don't forget to include the time it takes for a message to leave the XMITQ and traverse the channel to the destination queue when you are comparing times between an MQClient app and one that puts to a local def of a remote queue in bindings mode.
-----Original Message----- From: MQSeries List [mailto:[EMAIL PROTECTED] Behalf Of Bruce Baxter Sent: Wednesday, October 20, 2004 12:05 PM To: [EMAIL PROTECTED] Subject: Re: AIX Blade Servers Our applications have been shown to run much better with a local queue manager and Java Bindings rather than client access. That's why we'd be leaning towards local queue managers on each blade. Christopher Warneke <[EMAIL PROTECTED]> Christopher Warneke <[EMAIL PROTECTED]> Sent by: MQSeries List <[EMAIL PROTECTED]> 10/20/2004 11:57 AM Please respond to MQSeries List <[EMAIL PROTECTED]> To [EMAIL PROTECTED] cc Subject Re: AIX Blade Servers Are you sure that you need MQ servers on the blades? Make sure that you can't use a client first - they're both generic and free. You'll need the CAF (Client Attachment Facility) installed if the backend is a z/os mainframe. --- Bruce Baxter <[EMAIL PROTECTED]> wrote: > > We're giving some consideration to moving in the > direction of implementing > pSeries Blade Servers to host our Web Applications > which get their data > from our back end systems using MQ Series. What are > the practical ins and > outs of administering this sort of configuration? > > I'm wondering specifically, what mechanisms can be > put into place so that > each blade has its own unique queue manager. When > you bring a new blade > online, does it take a copy of the base image, or > run from a common copy > with all the other blades? How does it get its own > uniquely named queue > manager? > Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com <http://www.lsoft.com> Archive: http://vm.akh-wien.ac.at/MQSeries.archive <http://vm.akh-wien.ac.at/MQSeries.archive> This communication, including attachments, is for the exclusive use of addressee and may contain proprietary, confidential or privileged information. If you are not the intended recipient, any use, copying, disclosure, dissemination or distribution is strictly prohibited. If you are not the intended recipient, please notify the sender immediately by return email and delete this communication and destroy all copies. Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive
