- Installing DB2 UDB Servers
- Prerequisites
- Before You Begin
- Installing DB2 UDB
- Installed Directory Structure
- Considerations in an NIS Environment
- Distributed Installation
- Sample Response Files
- Creating a Response File
- Distributed Installation with a Response File
- Installing DB2 with db2_install
- DB2 UDB Environment Definitions
- DB2 Profile Registry
- Managing the DB2 Profile Registry
- The db2set Command
- Environment Variables
- Hierarchy of the DB2 UDB Environment
- DB2 Administration Server (DAS)
- DAS Process
- DB2 Instances
- Creating the Sample Database
- Using the Command Line Processor (CLP)
- Uninstalling DB2 Products
- Stopping the DAS Instance
- Stopping All DB2 Instances
- Removing the DAS Instance
- Removing DB2 Instances
- Removing DB2 Products
Creating a Response File
The DB2 instance setup GUI (db2isetup) can create a response file from an existing installed and configured DB2 UDB product. You can use the generated response file to re-create the exact setup on other machines. You can also generate a response file during DB2 installation, with the db2setup installation tool. In Figure 2.12, you had a choice of creating a response file in the example installation, and in Figure 2.22 the confirmation dialogue allowed you to define the location and name of the response file being generated (the default displayed is /tmp/db2ese.rsp). This method captures the definitions of the DB2 you install on a machine for use on other machines, or as a sample file you can then tailor for systems that may need a slightly different configuration if you are creating a response file only, and not installing DB2. You can also execute db2setup without installing the binaries (DB2) and generate a response file in that fashion.
As clients are frequently Windows-based, a separate response file generation tool is provided specifically for Windows (db2rspgn). For example, you could install and configure a DB2 Run-Time Client to connect to various databases across your network. Once this client is installed and configured to access all the database that your users must have access to, you can run the response file generator to create a response file and profile for each instance.
To generate a response file on Windows, execute the following command:
db2rspgn -d path
A response file is generated in the path you specify with the -d option. The final name is fixed, depending on which product has been installed. For example, a db2admcl.rsp file is generated for the Administration Client. Besides the response file, instance profiles are generated in the same path for all instances on a machine. Each instance profile has the settings for DB2 registry variables, database manager configuration parameters, node directory, database directory, and so on. If you are planning to set up and configure identical DB2 UDB products, you only need to specify the installation response file when you perform the installation. The installation response file that was created by the response file generator will automatically call each instance profile. You only need to ensure that the instance profiles are located in the same drive and directory as the installation response file.