If you are planning to install multiple DB2 Query Patroller Servers across your network, you may want to consider using a network-based distributed installation. With a network-based installation, you can roll out multiple copies of DB2 products, with a minimal amount of effort. You can also take advantage of the DB2 Response File Generator to create a response file for an installed and configured DB2 Query Patroller Server, and then roll-out identical copies of this product across your network. This method is often referred to as a "cookie-cutter" installation.
Since you can use this installation method for any DB2 product, we also recommend that you use this method to roll-out DB2 clients across your enterprise. For example, you could install a DB2 Administration Client on a workstation with only the DB2 Query Patroller Client component, then run the response file generator. The response file generated would only install a DB2 Administration Client with this component. You would not have to deselect the other components associated with a DB2 Administration Client for every installation.
You can push or pull a distributed installation. You can push an installation across your network using a system management tool, such as Microsoft Systems Management Server (SMS). SMS is fully integrated with DB2 product installations. You can pull an installation from a shared drive using the setup /U command or an install script at each target workstation.
There is a sample response file, called db2qp.rsp, which you can use for a DB2 Query Patroller Server distributed installation. This sample response file is located in the x:\db2\common directory on your DB2 Query Patroller CD-ROM (where x: is your CD-ROM drive).
For more information and instructions on how to perform a distributed installation, refer to the Installation and Configuration Supplement.