With Microsoft Systems Management Server (SMS), you can install DB2 across a network, and set up the installation from a central location. An SMS install will minimize the amount of work the users will have to perform. This installation method is ideal if you wish to roll out an installation on a large number of clients all based on the same setup.
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.
You must have at least SMS Version 1.2 installed and configured on your network for both your SMS server and SMS workstation. Refer to Microsoft's Systems Management Server for Windows NT Administrator's Guide for information on how to:
To set up a package through SMS, you will use the sample
SMS package description (db2.pdf) file and your customized
response file and instance profile.
|
| If you are using a response file that was created using the response file generator, you must ensure that all the instance profiles are located in the same drive and directory as the response file that you specify. |
To import the DB2 install files into SMS, perform the following steps:
step 1. | Insert the appropriate CD-ROM into the drive. |
step 2. | Click on Start and select Programs->Systems Management Server->SMS Administrator. |
step 3. | The Microsoft SMS Administrator Logon window opens, enter your logon ID and password, and click on OK. The Open SMS Window window opens. |
step 4. | Select the Packages window type and click on OK. The Packages window opens |
step 5. | Select File->New from the menu bar. The Package Properties window opens. |
step 6. | Click on the Import push button. The File Browser opens. Find the db2.pdf file located in x:\db2\winnt95\common\, where x: represents the CD-ROM drive. |
step 7. | Click on OK.
|
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 could be for system maintenance, changing client configuration parameters, or installing software.
To create an SMS package, perform the following steps:
step 1. | From the Package Properties window, click on the Workstations push button. The Setup Package For Workstations window opens, with the imported response file and instance profile ready to use. | ||
step 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 CD-ROM drive. | ||
step 3. | Select the name of the product to install from the Workstation Command Lines window. | ||
step 4. | If you changed and renamed the sample response file, click on 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.
| ||
step 5. | Click on OK. | ||
step 6. | Click on the Close push button. | ||
step 7. | Click on OK to close the opened windows. The Packages window shows the name of the new SMS package.
|
Now that you have created the package, you have three options:
Options 1 and 2 are available to you, but for a large number of installations we recommend option 3, which will be our 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, perform the following steps:
step 1. | Open the Sites window. | ||
step 2. | Open the Packages window. | ||
step 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. | ||
step 4. | Select the Run Workstation Command check box and select the installation package that you want to use. | ||
step 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. | ||
step 6. | Deselect the Not Mandatory over Slow Link check box .
For more information about completing the Job Details window, refer to Microsoft's Systems Management Server for Windows NT Administrator's Guide. | ||
step 7. | When the job specifications are complete, click on OK. You are returned to the Job Properties window. | ||
step 8. | Add a comment that explains what the job will do. For example, Install DB2 Run-Time Client. | ||
step 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. | ||
step 10. | Click on OK to close the Job Schedule window. | ||
step 11. | Click on 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:
step 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. | ||
step 2. | Click on Start and select Programs->SMS Client->Package Command Manager. The Package Command Manager window opens. | ||
step 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 on the Execute push button. The installation runs automatically. | ||
step 4. | Following installation, you must reboot the SMS client workstation before using DB2.
| ||
step 5. | Click on Start and select Programs->SMS Client->Package Command Manager. The Package Command Manager window opens. | ||
step 6. | Click on 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.