DB2 Version 9.7 for Linux, UNIX, and Windows

Installing DB2 products using Microsoft Systems Management Server (SMS)

You must have at least SMS Version 2.0 installed and configured on your network for both your SMS server and SMS workstation. Refer to Microsoft's Systems Management Server Administrator's Guide for your platform for more details 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.

When you are using SMS, you have control over which response file you will use. You can have several different installation options, resulting in several different response files. When you configure the SMS install package, you can specify which response file to use.

To install DB2 products using SMS:

1. Import the DB2 install file into SMS
2. Create the SMS package on the SMS server
3. Distribute the DB2 installation package across your network

Importing the DB2 install file into SMS

To set up a package through SMS, use the sample SMS package definition file and your customized response file and instance profile. The sample SMS file name is db2<product_abbreviation>.pdf. For example db2ese.pdf.

To import the DB2 installation files into SMS:

1. Insert the DB2 product DVD into the drive.
2. Start the Microsoft SMS Administrator. The Microsoft SMS Administrator Logon window opens.
3. Enter your logon ID and password, and click OK. The Open SMS window opens.
4. Select the Packages window type and click OK. The Packages window opens
5. Select File-->New from the menu bar. The Package Properties window opens.
6. Click the Import push button. The File Browser opens. Find the SMS package definition file located in x:\db2\Windows\samples, where x: represents the DVD drive. Typically, the pdf file needs to be customized before being used. You can copy the sample file from x:\db2\Windows\samples to local a local drive, modified the file, and import the updated file.
7. Click OK.

Creating the SMS package on the SMS server

Creating the SMS package on the SMS server is part of the larger task of Installing DB2 products using SMS.

An SMS package is a bundle of information that you send from the SMS server to an SMS client. The package consists of a set of commands that can be run on the client workstation. These commands are for system maintenance, changing client configuration parameters, or installing software.

To create an SMS package:

1. From the Package Properties window, click the Workstations push button. The Setup Package For Workstations window opens, with the imported response file and instance profile ready to use.
2. In the Source Directory field, enter the name of the parent directory where you put the copied DB2 files. For example, x:\db2prods, where x: represents your DVD drive.
3. Select the name of the product to install from the Workstation Command Lines window.
4. If you changed and renamed the sample response file, click the Properties push button. The Command Line Properties window opens. Change the value of the Command Line parameter to match the new response file name and path. If you are using a response file that was created using the response file generator, ensure that all the instance profiles are located in the same drive and directory as the response file that you specify.
5. Click OK.
6. Click the Close push button.
7. Click OK to close the opened windows. The Packages window shows the name of the new SMS package.

Distributing the DB2 installation package across your network

Now that you have created the package, you have three options:

• You can distribute your SMS package and then log on locally on the client workstation to run the package. This option requires that the user account used to perform the installation belongs to the local Administrators group where the account is defined.
• You can distribute your SMS package and then log on remotely on the client workstation to run the package. This option requires that the user account used to perform the installation belongs to the Domain Admins group.
• You can set up your SMS package with an auto-install feature.

Options 1 and 2 are available to you, but for a large number of installations option 3 is recommended, which will be the focus for this step.

Once sent to the client workstation, the SMS package will tell the client workstation what code to execute, and the location, on the SMS server, of that code.

• To send the code to a client workstation:
  1. Open the Sites window.
  2. Open the Packages window.
  3. In the Packages window, select the appropriate package and drag it onto the target client in the Sites window. The Job Details window opens. This window lists the package that will be sent to the client machine (Machine Path) and the command that will be executed at the workstation.
  4. Select the Run Workstation Command check box and select the installation package that you want to use.
  5. In the Run Phase box of the Job Details window, select the Mandatory After check box. A default mandatory date is set one week from the current date. Adjust the date as required.
  6. Deselect the Not Mandatory over Slow Link check box. This feature is critical if you are installing across a large number of workstations. It is recommended that you stagger the installation to avoid overloading your server. For example, if you are considering an overnight install, then spread out the install time for a manageable amount of client workstation. For more information about completing the Job Details window, refer to Microsoft's Systems Management Server Administrator's Guide for your platform.
  7. When the job specifications are complete, click OK. You are returned to the Job Properties window.
  8. Add a comment that explains what the job will do. For example, Install IBM® Data Server Client.
  9. Click the Schedule push button and the Job Schedule window opens. This window will arrange a priority for this job. By default, the job is low priority and all other jobs will be executed first. It is recommended that you select medium or high priority. You can also select a time to start the job.
  10. Click OK to close the Job Schedule window.
  11. Click OK.
  The job is created and the package is sent to the SMS client workstation.
• To run the installation on the SMS client, perform the following steps:
  1. On the target SMS client workstation, log on to the workstation with a user account that belongs to the local Administrators group where the account is defined. This level of authority is required because a system program install is being performed instead of a user program install.
  2. Start the Package Command Manager. The Package Command Manager window opens.
  3. When the SMS client workstation receives the packages from the SMS server, it is listed in the Package Name section of the window. Select the package and click the Execute push button. The installation runs automatically.
  4. Following installation, you must reboot the SMS client workstation before using DB2. Important: If you specified REBOOT = YES in your response file, the SMS client will reboot automatically.
  5. Click Start and select Programs-->SMS Client-->Package Command Manager. The Package Command Manager window opens.
  6. Click the Executed Commands folder and verify the execution of the package. Similarly, you can verify completion on the SMS server by checking the status of the job and ensuring that it has been changed to complete from pending or active.
  On the SMS client, open the Package Command Manager again. When the package, which you created and sent to the client, appears under the Executed Commands folder, the installation has completed.

Distributing DB2 installation packages using Microsoft Systems Management Server (SMS)

To distribute the DB2 installation package using SMS, ensure that:

• your SMS environment has already been set up.
• your DB2 install media is copied to a location where the contents of the install media can be edited.

To distribute the DB2 installation package using SMS, perform the following:

1. Prepare the sample response file located on your DB2 install media for the type of DB2 installation that you want to perform. The sample response file is db2*.rsp and is located in the db2\windows\samples directory on your DB2 install media.
2. On an SMS Distribution Point computer in your SMS environment, open the SMS Administrator Console. Click the Site Database drop down menu and right click Packages.
3. Select New --> Package From Definition. The Create Package from Definition wizard opens.
4. Click Next. The Package Definition window opens. Browse for the desired package file from the db2\windows\samples directory located on your DB2 install media. The name of this file is in the form db2*.pdf. Click Open.
5. Select the appropriate package definition from the list displayed. Click Next. The Source Files window opens.
6. Select the Create a compressed version of the source radio button, and click Next. The Source Directory window opens.
7. Select the location type and directory of the DB2 install media, and click Next.
8. Click Finish to complete the creation of the SMS package.
9. From inside the SMS Administrator Console, open the Site Database drop down menu and select Packages --> All Tasks --> Distribute Software. The Distribute Software wizard opens.
10. Click Next. The Package window opens.
11. Select the Distribute an existing package radio button, and select the appropriate package from the list of packages shown. Click Next. The Distribute Points window opens. Select one or more distribution points for the package that you are planning to distribute.
12. Click Next. The Advertise a Program window opens.
13. Select the radio button indicating that you want to advertise the program to a collection, and select the program that you want to run from the list shown. Click Next. The Advertisement Target window opens.
14. Select either an existing collection of computers or a choose to create a new collection of computers where you want to advertise and install the selected program. Click Next. The Advertisement Name window opens.
15. Type in a name for the new advertisement and any comments that you want to add. Click Next. The Advertise to Subcollections window opens.
16. Specify where you want the relevant DB2 program to be run relative to the hierarchical setup of the SMS computers in your SMS environment. Click Next. The Advertisement Schedule window opens.
17. Select a date and time after which you want the DB2 program to be run on the collection of computers specified. You might also want to select a expiration time for the advertisement of the program. Click Next. The Assign Program window opens.
18. If you want the DB2 program to be a mandatory requirement on the computers in the specified collection, specify a date and time after which the program will automatically run. Click Next.
19. Click Finish to complete the Distribute Software wizard.

Configuring remote access to a server database

About this task

DB2 uses the CATALOG command to catalog remote database access information:

• The CATALOG NODE command specifies the protocol information about how to connect to the host or to the server.
• The CATALOG DATABASE command catalogs the remote database name and assigns it a local alias.
• The CATALOG DCS command specifies that the remote database is a host or OS/400® database. (This command is only required for DB2® Connect™ Personal or Enterprise Editions).
• The CATALOG ODBC DATA SOURCE command registers the DB2 database with the ODBC driver manager as a data source.

If you plan to roll out multiple copies of IBM data server clients with identical configurations, then you can create a batch file that will run your customized script. For example, consider the following sample batch file, myscript.bat, used to run the script file:

   @echo off
   cls
   db2cmd catmvs.bat

The DB2CMD command initializes the DB2 database environment and the catmvs.bat file calls the batch job of the same name. Here is a sample catalog script file, catmvs.bat, that could be used to add databases to a DB2 Connect Personal Edition workstation:

   db2 catalog tcpip node tcptst1 remote mvshost server 446
   db2 catalog database mvsdb at node tcptst1 authentication server
   db2 catalog dcs database mvsdb as mvs_locator
   db2 catalog system odbc data source mvsdb
   db2 terminate
   exit

You can either send these files to your client workstations manually or use SMS and have the script run automatically after the installation and reboot have completed.

Procedure

To create another SMS package with the catalog script, perform the following steps:

1. Start the SMS Administrator. The Open SMS window opens.
2. Select the Packages window type and click OK. The Packages window opens.
3. Select File -> New from the menu bar. The Package Properties window opens.
4. Enter a name for your new package. For example, batchpack.
5. Enter a comment about the package. For example, Package for batch file.
6. Click the Workstations push button. The Setup Package for Workstations window opens.
7. Enter the source directory. Ensure that the source directory is a location that both the server and the client have access to, and that contains the batch file that is to be run from the client workstation.
8. Under the Workstation Command Lines section, click New. The Command Line Properties window opens.
9. Enter a command name.
10. Enter the command line.
11. Click the check box for the platforms that should be supported, under the Supported Platforms section.
12. Click OK.
13. Click Close.
14. Click OK.

What to do next

Distribute this package in the same way as an installation package.

Configuring db2cli.ini for a response file installation

The db2cli.ini file is an ASCII file which initializes the DB2 CLI configuration. This file is included to help you get started and can be found in:

• On the Windows® XP and Windows 2003 operating systems: Documents and Settings\All Users\Application Data\IBM\DB2\Copy Name
• On the Windows 2008 and Windows Vista (and later) operating system: ProgramData\IBM\DB2\Copy Name

where Copy Name represents the DB2 copy name.

If you use any specific CLI optimization values or CLI parameters, you can use your customized db2cli.ini file for your IBM data server client workstations. To do so, copy your db2cli.ini file to the DB2 installation directory (for example c:\Program Files\IBM\SQLLIB) on each IBM data server client workstation.