Elevating a QMF Fix pack to a fully licensed and configured version for roll out to new machines
If my organization has one hundred laptops with QMF for Workstation installed and configured, then when a QMF Fix pack comes out, I download it from IBM Fix Central and give it to my roll out team to apply it.
But what if we have merged with another organization and there are one hundred additional machines that need QMF? Do I have to do TWO installs on each machine: One with the old release and one with the new fix pack?
No, the following onetime process will elevate a fixp ack to a fully licensed version and allow the installer software to configure the new system.
Step 1)
Download the latest fix pack from IBM Fix Central and unzip it into a directory:
Step 2)
Choose one machine that has QMF for Workstation already installed and configured. Go to the directory into which QMF for Workstation was installed and copy the license key:
Put that license key in the directory with the setupwinXX.exe
If you stop here, then the setupwin64.exe (in this case) will pick up the license key and allow you to do a single install on the new machines. However, these new installs will NOT be configured to connect to any repositories or databases.
Step 3) On the pre-configured machine, go to the user home directory , typically in
C:\Users\<userid>\AppData\Roaming\IBM\QMF for Workstation
And collect the following three files:
The repoistories.xml has the connection strings to the Repository Storage.
The .storage is OPTIONAL, it has all the user interface config settings like GLOBAL Variables, buttons, menus etc. ONLY include this if you have a standard setup that you wish to rollout.
.bi.jdbc.drivers has the locations of all the JDBC drivers on the master machine. NOTE that these drivers need to be in the SAME location for the target clean machines. That is, if they are in a directory called C:\QMF\Drivers on the master machine then that folder, populated with the same drivers must be on the target machine. The rollout team can most likely make the process create an populate such a folder.
If the drivers are on a shared driver like \\serverx\QMF\Drivers or Z:\QMF\Drivers then there is no need to have the roll out team deliver drivers.
With these files in place, this folder can be delivered to the roll out team to deploy to the new machines.
Step 4) Optionally, you may set up a silent install for the roll out.
To do this you, run the install one more time on the Master machine, but you run it from a Windows Command line with the parameter -r followed by the file name installer.properties
This will walk you through the normal install wizard, but it will record your choices in a file called installer.properties.
Put installer.properties in the same folder as the setupwinXX.exe and the other files.
Now, on a target machine, if the command
Setupwin64.exe -i silent is given from a command line in the folder with all the files above,
The product will install silently and take the choices recorded in the installer.properties file.
This is a good way to limit which components end-users get on their machines. There may be no point in rolling out the QMF for Workstation Administrator functionality or the QMF Data Service Data Studio to everyone.
There is a Help topic in QMF for Workstation that gives further details on the silent install.
#Db2Toolsforz/OS#Db2QMF#QMF