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?

Reply via email to