/build/static/layout/Breadcrumb_cap_w.png

IBM DB2 Connect

Version: 9

Don't be a Stranger!

Sign up today to participate, stay informed, earn points and establish a reputation for yourself!

Sign up! or login
Views: 4.4k  |  Created: 07/08/2010

Average Rating: 0
DB2 Connect has 1 inventory records, 0 Questions, 0 Blogs and 0 links. Please help add to this by sharing more!

Deployment Tips (3)

Most Common Setup Type
Not Determined
Average Package Difficulty Rating
Rated 0 / 5 (Not Rated) based on 0 ratings
Most Commonly Reported Deployment Method
Not Determined
2
Note
Earlier versions than v9.1.9 cannot be deployed via SCCM (the install fails when running under the System context) - this has been confirmed by IBM engineering. I attempted to configure and deploy v9.1.6 and was unable to do so. We had to upgrade to v9.1.9.

Challenges:
* Deployment Environment: SCCM with multiple Distribution Points
* We needed multiple databases to be configured the same for each user
* Users without local admin rights cannot properly run the app unless they are a member of the local DB2USERS group which is created during the installation
* The app must be licensed as a post-installation procedure
* The DB2.INS file must be located in a static location as defined in the response file

Create the response file:
* Install app from setup.exe on a clean machine
* Configure your database(s) with the DB2 Configuration Assistant
* Open a command prompt and execute db2rspgn.exe from C:\Program Files\IBM\SQLLIB\Bin to create the response file.
- Db2rspgn.exe -d C:\Admin -I DB2
This generates the "db2client.rsp" and "DB2.INS" files in the C:\Admin directory
- "C:\Admin" can be replaced with whatever location you choose
* Edit the db2client.rsp with Notepad to change the following properties:
- LIC_AGEEEMENT=ACCEPT
- DB2.CLIENT_IMPORT_PROFILE=C:\WINDOWS\Temp\DB2.INS
* Copy the "db2client.rsp" and "DB2.INS" files to the project and distribution directories. The installation script will copy the DB2.INS file to the Temp folder on the local machine.

I created a VBScript to do the following and deployed it via SCCM:
* Identify the installation source directory
- strScriptPath = objfso.getabsolutepathname("")
* Copy the DB2.ins file from strScriptPath to "C:\WINDOWS\Temp\"
- objFSO.CopyFile strScriptPath & "\DB2.ins","C:\Windows\Temp\",True
- *This file must be located in a static path that you define in the db2client.rsp file property "DB2.CLIENT_IMPORT_PROFILE"
* Run the installation with the following command line:
- WSHShell.run ("setup.exe -u " & chr(34) & strScriptPath & "\db2client.rsp" & chr(34) ,1,True)
- (Install String: setup -u PathToResponseFile\db2client.rsp)
* Add "Everyone" to the DB2USERS group:
- WSHShell.Run ("NET localgroup DB2USERS everyone /ADD"),1,True
* License the app:
- WSHShell.Run ("C:\Program Files\IBM\SQLLIB\BIN\db2licm.exe" & chr(34) & " -a " & chr(34) & "C:\Program Files\IBM\SQLLIB\License\db2consv_zs.lic" & chr(34)),1,True
- (License String: db2licm.exe –a PathToLicenseFile\LicenseFileName.lic
Setup Information:
Setup Type: unspecified
Deployment Method Used: unspecified
Deployment Difficulty: unspecified
Platform(s): Windows
2
Note
Earlier versions than v9.1.9 cannot be deployed via SCCM (the install fails when running under the System context) - this has been confirmed by IBM engineering. I attempted to configure and deploy v9.1.6 and was unable to do so. We had to upgrade to v9.1.9.

Challenges:
* Deployment Environment: SCCM with multiple Distribution Points
* We needed multiple databases to be configured the same for each user
* Users without local admin rights cannot properly run the app unless they are a member of the local DB2USERS group which is created during the installation
* The app must be licensed as a post-installation procedure
* The DB2.INS file must be located in a static location as defined in the response file

Create the response file:
* Install app from setup.exe on a clean machine
* Configure your database(s) with the DB2 Configuration Assistant
* Open a command prompt and execute db2rspgn.exe from C:\Program Files\IBM\SQLLIB\Bin to create the response file.
- Db2rspgn.exe -d C:\Admin -I DB2
This generates the "db2client.rsp" and "DB2.INS" files in the C:\Admin directory
- "C:\Admin" can be replaced with whatever location you choose
* Edit the db2client.rsp with Notepad to change the following properties:
- LIC_AGEEEMENT=ACCEPT
- DB2.CLIENT_IMPORT_PROFILE=C:\WINDOWS\Temp\DB2.INS
* Copy the "db2client.rsp" and "DB2.INS" files to the project and distribution directories. The installation script will copy the DB2.INS file to the Temp folder on the local machine.

I created a VBScript to do the following and deployed it via SCCM:
* Identify the installation source directory
- strScriptPath = objfso.getabsolutepathname("")
* Copy the DB2.ins file from strScriptPath to "C:\WINDOWS\Temp\"
- objFSO.CopyFile strScriptPath & "\DB2.ins","C:\Windows\Temp\",True
- *This file must be located in a static path that you define in the db2client.rsp file property "DB2.CLIENT_IMPORT_PROFILE"
* Run the installation with the following command line:
- WSHShell.run ("setup.exe -u " & chr(34) & strScriptPath & "\db2client.rsp" & chr(34) ,1,True)
- (Install String: setup -u PathToResponseFile\db2client.rsp)
* Add "Everyone" to the DB2USERS group:
- WSHShell.Run ("NET localgroup DB2USERS everyone /ADD"),1,True
* License the app:
- WSHShell.Run ("C:\Program Files\IBM\SQLLIB\BIN\db2licm.exe" & chr(34) & " -a " & chr(34) & "C:\Program Files\IBM\SQLLIB\License\db2consv_zs.lic" & chr(34)),1,True
- (License String: db2licm.exe –a PathToLicenseFile\LicenseFileName.lic
Setup Information:
Setup Type: unspecified
Deployment Method Used: unspecified
Deployment Difficulty: unspecified
Platform(s): Windows
0
Command Line
Silent Uninstallation

You cannot use the MSI ProductCode for silent removals of this product. A message will be displayed during uninstall, asking you if you want to remove the DB's as well. This message cannot be disabled.

For a successful silent uninstall use this command instead:

Run: CMD => "%ProgramFiles%\IBM\SQLLIB\BIN\db2unins.bat" -f -y

The file "db2unins.bat" is created during the DB2 Connect main installation by its installer.
Setup Information:
Setup Type: unspecified
Deployment Method Used: unspecified
Deployment Difficulty: unspecified
Platform(s): Windows

Inventory Records (1)

View inventory records anonymously contributed by opt-in users of the K1000 Systems Management Appliance.

Versions

DB2 Connect

Version

9

Questions & Answers (0)

Questions & Answers related to IBM DB2 Connect

Blogs (0)

Blog posts related to IBM DB2 Connect

Reviews (0)

Reviews related to IBM DB2 Connect

 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ