Installing and Configuring DB2 Clients

Installing Thin Clients using SMS

To set up a code server, and use Microsoft Systems Management Server (SMS) to install one or more thin clients which will access it, perform the steps in the following sections:

• "Step 1. Install DB2 Client Application Enabler on the Code Server"
• "Step 2. Create a Response File for Thin Client Installation"
• "Step 3. Import the Thin Client PDF File into SMS"
• "Step 4. Distribute the Thin Client Installation Package Using SMS"
• "Step 5. Run the Installation on the SMS Clients"

If you plan to install multiple thin clients in a row, perform all the steps for the first thin client, then perform only "Step 4. Distribute the Thin Client Installation Package Using SMS" and "Step 5. Run the Installation on the SMS Clients" for each subsequent thin client on that code server.

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 a Username for Installing DB2 Products

Windows 95

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 must belong to the Administrators group, and also be a valid DB2 username or have the "Act as part of the operating system" advanced user right.

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".

If this username does not comply with DB2's naming rules, but has the "Act as part of the operating system" advanced user right, the setup program will create the username DB2ADMIN to perform the installation.

This username will be removed from the system when the installation is complete.

SMS Requirements

SMS must already be 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.

Step 1. Install DB2 Client Application Enabler on the Code Server

See Chapter 4. "Installing DB2 Clients on Windows 95 or Windows NT Workstations" for complete instructions on installing DB2 Client Application Enabler on the code server machine. For the thin client feature, keep the following considerations in mind:

• You must install DB2 Client Application Enabler in a location which can be accessed in READ mode by the thin client workstations. Use Windows Explorer to set up a share for the entire drive, or just for the directory where DB2 Client Application Enabler is installed. For example, you can install the DB2 Client Application Enabler to c:\codesrv\sqllib, then a share can be set up for the directory c:\codesrv.

  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 c:\codesrv.

  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, enter a share name. For example, db2nt.

  6. To specify the type of access on Windows NT:

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

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

     On Windows 95 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, c:\codesrv uses a share name of db2nt. We will use this value in the examples that follow.

• We recommend that you install all components of DB2 Client Application Enabler. You can specify which components are installed on each client by means of the response file (see "Step 2. Create a Response File for Thin Client Installation").

In this example, we will assume that you are installing DB2 Client Application Enabler on the code server where SMS is installed. If you are installing to a different location, you must NET USE to this share in order to make the thnsetup install accessible to SMS.

Step 2. Create a Response File for Thin Client Installation

When you are done installing DB2 Client Application Enabler, the code server will contain a directory c:\codesrv\sqllib\thnsetup which will contain all files needed for the thin client setup, including the sample response file, db2thin.rsp.

During an interactive installation, you provide the information needed to install DB2 and configure its environment. During an unattended installation, this information is provided in the form of keywords and values in a response file. DB2 Client Application Enabler installed on the code server includes a ready-to-use sample response file for the thin client install, with default entries already in place. This information will be applied when you install a thin client.

You can create a different response file, and therefore a different configuration, for each thin client installation. You can also edit and resave the response file to create one or two or more "standard" configurations, using the same ones as templates for multiple thin client installations.

Edit the sample response file using your favorite editor. For example, you can use Notepad or WordPad.

1. The sample response file, db2thin.rsp, is located in c:\codesrv\sqllib\thnsetup directory on the code server in our example.

2. The response file contains:

   • Keywords unique to installation

   • Environment variable settings

   • Configuration parameter settings.
   
   

   For more information on DB2 environment variables, see "DB2 Registry Values and Environment Variables", or refer to the Administration Guide. Configuration parameters, refer to the Administration Guide .

   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.

3. You can edit the keywords unique to installation contained within the response file. These are as follows:

   *REBOOT            = Yes, No
   *TYPE              = 0,1,2 (0=compact,1=typical,2=custom)
   *COMP              = Graphical Tools
   *COMP              = Client Configuration Assistant
   *COMP              = Control Center
   *COMP              = Visual Explain
   *COMP              = Performance Monitor
   *COMP              = IBM DB2 ODBC Driver
   *COMP              = Installing and Configuring DB2 Clients
   *COMP              = Messages Reference
   *USERNAME          = (userid that the security service will run under)
   *PASSWORD          = (password for the security service id)
    
   

   
   

   You will need to reboot the target workstation after installing. To have this done automatically, activate the REBOOT keyword.

   The TYPE keyword specifies the type of install that you want.

   • Install type 0 specifies a compact install. This option provides you with access to the client code, but none of the other components are accessible from the client workstation.

   • Install type 1 specifies a typical install, and is the default setting. With this option, all components defined on the code server are accessed from the client workstation.

   • Install type 2 specifies a custom install. This option allows you to install only selected components. Set the TYPE keyword to 2 (Custom Install) and activate the COMP keyword for each component you want to access.
   
   

   The only environment variable setting that must be specified within the response file is DB2INSTPROF. To set up a separate client configuration for each thin client, set the DB2INSTPROF value to a directory on the thin client workstation. To maintain one client configuration on the code server, set DB2INSTPROF to a directory on the code server workstation.

4. Edit the environment variables contained within the response file.

   The following is a sample section of the environment variables contained within a response file:

   *DB2BQTIME         = 1 -
   *DB2BQTRY          = 0 -
   *DB2CHKPTR         = ON, OFF
   *DB2CODEPAGE       =
   *DB2DBDFT          =
   DB2INSTPROF        = C:\CFG
   *DB2IQTIME         = 1 -
   *DB2OPTIONS        =
   ...
   

5. Edit the configuration parameters contained within the response file.

   The following is a sample section of the configuration parameters contained within a response file:

   *DB2.DIAGLEVEL      = 0 - 4
   *DB2.DIAGPATH       =
   *DB2.DIR_CACHE      = YES, NO
   *DB2.DIR_OBJNAME    =
   *DB2.DIR_PATH_NAME  =
   *DB2.DISCOVER       = DISABLE, KNOWN or SEARCH
   ...
   

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

Step 3. Import the Thin Client PDF File into SMS

To import the thin client PDF files into SMS:

1. Double-click on the Systems Management Server group.

2. Double-click on the SMS Administrator icon. The SMS Administrator window opens.

3. Select the Packages window.

4. Select File->New from the menu bar. The Package Properties window opens.

5. Click on the Import push button. The File Browser appears.

6. In the File Name field, select the db2thin.pdf file from the c:\codesrv\sqllib\thnsetup directory on the code server.

7. Click on OK to return to the Package Properties window.

Step 4. Distribute the Thin Client Installation Package Using SMS

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

To create the SMS package:

1. 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 location of the thin client install files, c:\codesrv\sqllib\thnsetup.

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

4. Click on the Properties push button and update the command line for the thnsetup program. Thnsetup accepts the following command line arguments:
   
   

   Specify the relative filepath to invoke the program. For example:

     thnsetup.exe /U db2thin.rsp /P x:\sqllib /M \\db2server /S db2nt
    
   

   where:

   /P

   Specifies the path to the location where the client is installed on the code server. If you specify the sharename, then the install program will implicitly perform a NET USE for you. It will take the drive letter specified on this argument, the machine specified, and the sharename, and issue the NET USE.

   /U

   Specifies the relative path to the response file.

   /M

   Specifies the machine name of the code server.

   /S

   Specifies the share name of the code server drive/directory where DB2 Client Application Enabler is installed.

   If this share requires a username and/or password, specify the share name as: sharename,userid,password.

   If there is no password, type: sharename,userid.

   If a username is not required, type: sharename only.

5. Click on OK to return to the Setup Package For Workstations window.

6. Click on the Close push button to return to the Package Properties window.

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

8. To 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 Clients

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 a Username for Installing DB2 Products" for more information.

2. Double-click on the SMS Client group.

3. Double-click on the Package Command Manager icon. The Package Command Manager window opens.

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

5. After the installation, reboot the SMS client before using the thin client.

To configure the thin clients to access servers, go to Chapter 9. "Configuring Client to DB2 Server Communications Using the CCA".

[ DB2 List of Books | Search the DB2 Books ]