Installing and Configuring DB2 Clients

Installing DB2 Remotely Using SMS

With Microsoft Systems Management Server (SMS), you can install DB2 across a network onto remote Windows NT systems, setting up the installation from a central location.

You can also use SMS to remove all DB2 products from a target workstation. Simply follow the instructions below, but when creating the SMS package, select Uninstall DB2 Products instead of selecting the packages to be installed.

To install DB2 using SMS, perform the steps in the following sections:

• Step 1. Make DB2 Files Available for Installation

• Step 2. Create a Response File for Unattended Installation

• Step 3. Import the DB2 Install Files into SMS

• Step 4. Distribute the DB2 Installation Package Using SMS

• Step 5. Run the Installation on the SMS Client

Before You Begin

Read and perform the steps in this section before you begin the installation to ensure that you have the required items and information you will need.

Creating Usernames for DB2 Installation and Operation

This section describes usernames required to install DB2 and its components.

Creating a Username for Installing DB2

Windows 95 and Windows 98

The username must be a valid DB2 username.

A valid DB2 username is eight characters or less, and complies with DB2's naming rules. For more information on DB2's naming rules, see Appendix C. Naming Rules.

Windows NT

You need to have a username that will be used to install DB2. The username may belong to the Domain or local Administrators group.

On clients, this username will be removed from the system when the installation is complete.

SMS Requirements

You must already have SMS installed and configured on your network. Refer to Microsoft's Systems Management Server for Windows NT Administrator's Guide for information on how to:

• Set up SMS (including setting up primary and secondary sites).
• Add clients to the SMS system.
• Set up inventory collection for clients.

To create an SMS package that copies the required files directly from the CD-ROM, insert the appropriate CD-ROM into the drive and go to Step 2. Create a Response File for Unattended Installation.

Step 1. Make DB2 Files Available for Installation

To make the DB2 install files accessible to the machine where DB2 will be installed:

• If performing remote installs directly from the CD-ROM:

  1. Insert the appropriate CD-ROM into the drive.

  2. Ensure that the CD-ROM remains in the drive for as long as the installation requires it. If the drive is often used for other tasks as well, consider installing from the hard disk instead.

• If installing from a code server, you must copy the required files from the CD-ROM directories to the hard disk:

  1. Insert the appropriate CD-ROM into the drive.

  2. Create a directory on the code server, for example, q:\db2prods.

  3. At the command prompt, use the cpysetup.bat command to copy the files necessary for a particular language install to a code server.

     The command syntax is:

     • x:\db2\winnt95\common\cpysetup.bat q:\db2prods language

       for:

       • DB2 Client Application Enabler
       • DB2 Software Developer's Kit

     where:

     • x: represents your CD-ROM drive
     • q: represents the code server's disk.
     • language is the two-character country code that represents your language (for example, EN for English). Table 23

If performing a remote installation, you must enable your network clients to access the DB2 install files.

Grant shared access to the directory that you just created, or to the CD-ROM drive.

To set up a share:

1. Click on Start and select Programs->Windows Explorer.

2. Select the directory that you want to share, for example q:\db2prods.

3. Select Files->Properties from the menu bar. The properties window for the directory will open. Click on the Sharing tab.

4. Select the Shared As radio button.

5. In the Share Name field type a share name. For example, type db2nt.

6. To specify read access for everyone on Windows NT:

   1. Select the Permissions push button. The Access Through Share Permissions window opens.

   2. In the Name box, make sure that Everyone is selected.

   3. In the Type of Access box, select Read.

   4. Click on OK.

   On Windows 95 and Windows 98, you do not need to specify type of access when you set up a share. By default, everyone is allowed read access.

In our example scenario, q:\db2prods uses a share name of db2nt. We will use this value in the examples that follow.

Step 2. Create a Response File for Unattended Installation

During an interactive installation, you interact with the install program, filling in a series of panels to set up and configure DB2. During an unattended installation, you supply the setup and configuration data in a response file you create before running the installation. DB2's install package includes a number of ready-to-use sample response files, with default entries already in place.

The sample response files are located in:

• x:\db2\winnt95\common

  for:

  • DB2 Client Application Enabler
  • DB2 Software Developer's Kit

where x is the letter that designates the CD-ROM drive. There is a different response file for each product on the CD, so that the user has a valid list of parameters for each product.

If you intend to use the sample response file provided, without making any changes to its values, you can skip this step and go to Step 4. Distribute the DB2 Installation Package Using SMS.

Edit the sample response file. For example, you can use Notepad or WordPad.

1. Open the sample response file for the package you want to install.

   • db2cae.rsp for DB2 Client Application Enabler

   • db2sdk.rsp for DB2 Software Developer's Kit

2. The response file contains:

   • Keywords unique to installation

   • Registry value/environment variable settings

   • Database manager configuration parameter settings.
   
   

   For more information on: DB2 environment variables and registry values, see DB2 Registry Values and Environment Variables, or refer to the Administration Guide. Database manager configuration parameters, refer to the Administration Guide.

3. To activate an item in the response file, remove the asterisk (*) to the left of the keyword/environment variable, erase the current setting to the right of the value and type in a new setting. The possible settings are listed to the right of the current setting.

   An example section of a response file appears below:

   ...
   FILE               = c:\sqllib
   REBOOT             = No
   *COMP              = Control Center
   ...
   

   Keywords unique to installation are parameters that are only specified in a response file during an unattended installation. The following is a list of keywords unique to installation for Windows 32-bit operating systems unattended installation:

   • FILE

     Specifies the destination directory for DB2.

     Note:

     Check the value for the FILE keyword. FILE specifies where to install the product. If you do not change this value, it defaults to x:\sqllib where x: is the drive on which your operating system is installed.

   • REBOOT

     Specifies whether to reboot the system following installation.

   • TYPE

     Specifies the type of install. The options are:

     0=Compact

     1=Typical (default)

     2=Custom

     For 0 and 1 (compact and typical), any Custom Keywords (COMP) value will be ignored.

     For all types, default communication values will be used where applicable, as follows:

     1. DB2.DB2COMM will be set for the protocols detected on your system.

     2. If a protocol is detected on the system, or if you have specified values for DB2.DB2COMM, values for its parameters will be generated so that the protocol will be enabled for DB2's use at the end of the install. Checks are made to ensure that the generated values are not duplicates, and that they conform to the protocols set up on your system. Default values will be generated for the following:

        • For NetBIOS:

             DB2.DB2NBADAPTERS     
             DB2.NNAME             
           
          

        • For TCP/IP:

             DB2.PORT_NUMBER        
             DB2.SVCENAME            
          

        • For IPX/SPX:

             DB2.FILESERVER        
             DB2.OBJECTNAME        
             DB2.IPX_SOCKET        
           
          

        • For APPC:

             DB2.TPNAME            
           
          

        Note:

        You may override these values; however, if the associated protocol has not been detected or specified, the values will not be used.

   • PROD

     Specifies the product you want installed. The options are:

     • DB2_CAE for DB2 Client Application Enabler

     • DB2_SDK for DB2 Software Developer's Kit

     Note:

     You can use this parameter more than once.

   • COMP

     Specifies the components you want installed. The installation program automatically installs components that are required for a product, and ignores requested components that are not available.

     Note:

     Component selections have no effect unless you specify a custom installation.

     Table 22 lists COMP keywords and the components they represent.

   • AUTO_CTRL_CENTER

     Specifies whether or not to automatically start the Control Center each time the system is rebooted.

     Note:

     By default, the Control Center starts automatically unless this parameter is set to NO.

   • AUTOSTART_CCA

     Specifies whether or not to automatically start the Client Configuration Assistant each time the system is rebooted.

     Note:

     By default, the Client Configuration Assistant starts automatically unless this parameter is set to NO.

   
   

   Install DB2 only on a drive that is local to the target workstation. Installing on a non-local drive can cause performance and availability problems. By default, the name of the response file will be used to determine the products to be installed. You can override this setting by providing one or more PROD parameter values in the response file.

4. Exit the file. If you have made any changes, save the file under a new file name to preserve the original sample response file.

   If you are installing directly from the CD-ROM, you must store the renamed response file on another drive.

Step 3. Import the DB2 Install Files into SMS

To import the DB2 install files into SMS:

1. Insert the appropriate CD-ROM into the drive.

2. From the Start button select Programs, then Systems Management Server, and then SMS Administrator. The SMS Administrator window opens.

3. Open the Package Properties window. The first time you start the SMS Administrator program you will see a dialog box prompting you to open an SMS Window. You can select the Packages option from there. Otherwise, select File->New from the menu bar.

4. Click on the Import push button. The File Browser opens.

5. In the File Name field, select the db2.pdf file.

   The server db2.pdf file for DB2 Universal Database is located in the

      x:\db2\common directory (for DB2 Server)
      x:\db2\winnt95\common directory (for DB2 CAE or DB2 SDK)
    
   

   where x: designates your CD-ROM drive

Step 4. Distribute the DB2 Installation Package Using SMS

In this step, you create an SMS package and send it to the SMS client where you want to install DB2.

To create the SMS package:

1. From the Package Properties window, click on the Workstations push button. The Setup Package For Workstations window opens, showing a list of predefined DB2 installation packages that you can use.

2. In the Source Directory field, type the name of the parent directory where you put the copied DB2 files (for example, q:\db2prods).

3. Select the name of the product to install from the Workstation Command Lines list.

4. If you changed and renamed the sample response file, click on the Properties push button and change the value of the parameter to match the new response file name.

   If you do not specify the language, setup will determine the system language, and launch the appropriate DB2 install for that language. If you want to install a different language, use the /I parameter to specifies the two-character code that represents your language (for example, EN for English). Table 23 lists the code for each available language.

5. Click on the Close push button.

6. Click on OK to close the opened windows.

   The Packages window shows the name of the new SMS package.

7. Specify where to run the package:

   1. Open the Sites and Packages windows.

   2. In the Packages window, select the appropriate package and drag it onto the target client in the Sites window. The Job Details window opens.

   3. Select the Run Workstation Command check box and select the installation package that you want to use for the Run Command on Workstation job. For more information about completing the Job Details window, refer to Microsoft's Systems Management Server for Windows NT Administrator's Guide.

   4. When the job specifications are complete, click on OK to close the opened windows.

   The job is created and sent to the SMS client.

Step 5. Run the Installation on the SMS Client

Now that the remote installation package has been prepared and sent, the SMS client on the target machine can run the installation.

1. On the SMS client where DB2 will be installed, logon as a username that meets the requirements for installing DB2. See Creating Usernames for DB2 Installation and Operation for more information.

2. Select Start->Programs -> Systems Management Client and then click on Package Command Manager. The Package Command Manager window opens.

3. When packages are sent from the SMS server, they are listed in the window. Select the DB2 package, then click on the Execute push button. The installation runs automatically.

4. Following installation, you must reboot the SMS client before using DB2.

   Note:

   If you specified REBOOT=yes in your response file the SMS client will reboot automatically.

To configure your DB2 software to access remote DB2 servers, go to Chapter 9. "Configuring Client-to-Server Communications Using the Client Configuration Assistant".

[ DB2 List of Books | Search the DB2 Books ]