In addition to service releases, IBM Rational solution for Collaborative Lifecycle Management (CLM) and Design Management (DM) independently publish iFix releases, which are rolled into fix pack releases. The content of these fix packs cannot be predicted when a version of IBM Quick Deployer is released. To address this problem, Quick Deployer V2.0 supplies its fix pack installer in 2 parts:
- A basic script install_ifix.py that ships as part of Quick Deployer and is executed by IBM UrbanCode Deploy.
Note: should this script need to be updated, a new version will be made available and can be downloaded and installed via this extra step.
- Soon after the release of a fix pack (CLM or DM), files are made available to support the installation of the fix pack. These files include a processing engine script install_ifix_engine.py that is used by the basic script and a configuration file xxx_QDconfig.properties to control the fix pack installation. Download the processing engine script to the CLMiFix folder, and download the configuration file to the CLMiFix or DMiFix folder on the Quick Deployer media sever.
General media server information for Quick Deployer support of CLM fix packs
Place the CLM fix pack support files alongside the iFix .zip file in the CLMiFix folder. For example, to install CLM 601 iFix007, you need the files listed below. More information on the expected content of a Quick Deployer media server can be found on the
IBMQuickDeployerInstallationMedia wiki.
- CLMiFix
- CLM_601_iFix007.zip
- CLM_601_iFix007_QDconfig.properties
- install_ifix_engine.py
General media server information for Quick Deployer support of DM fix packs
Place the DM fix pack support files alongside the iFix .zip file in the DMiFix folder. For example, to install DM 601 iFix007, you need the files listed below. More information on the expected content of a Quick Deployer media server can be found on the
IBMQuickDeployerInstallationMedia wiki.
Note: to install a DM fix pack, the corresponding CLM fix pack must also be installed
- DMiFix
- DM_601_iFix_7.zip
- DM_601_iFix_7_QDconfig.properties
- Rhapsody_DM_ModelServer_601_iFix_7.zip
- Rhapsody_DM_ModelServer_601_iFix_7_QDconfig.properties
Downloads
To install an iFix, you need to download the processing engine script and the configuration file that matches the fix pack that you plan to install.
Processing engine script
All supported iFixes can be installed by the same version of the
install_ifix_engine.py script. Download the compressed file; extract the script; and place it in the CLMiFix folder on the media server.
Release specific configuration files
Download the Quick Deployer configuration file that matches the fix pack that you plan to install; place the CLM file in the CLMiFix folder; and place the DM file in the DMiFix folder on the media server.
CLM 604
CLM 603
CLM 602
CLM 601
CLM 60
DM 604
DM 603
DM 602
DM 601
Update the install_ifix.py script that ships with Quick Deployer
Currently this is the same file as included in Quick Deployer V2.0.
Follow these steps to update the
install_ifix.py script that is contained in the
Rational_QD_Application_60x UCD Component.
- In a temporary folder, download and extract the install_ifix.py script from install_ifix_20170726-1410.zip
- Navigate to the folder that contains the Quick Deployer package content. This should be the folder from which you ran the installer.
- Edit the qd.properties file so that the iFixInstallScript entry points to the location of the install_ifix.py file that you downloaded. Note: Check the rest of the value-pair settings in the qd.properties file, and check each of the other properties files to ensure that they contain the desired settings so that you do not inadvertently update settings by using an old version of a properties file. For example, after the first time that you run the installer to install the Quick Deployer application into IBM UrbanCode Deploy, you might change some parameters by running one or more of these application processes:
When you run the installer again, as shown below, it updates those application processes based on the settings in the properties files. A scenario where you might inadvertently introduce unwanted changes to an application process is as follows: When you run the installer the first time, you decide not to provide a link in the qd.properties file to the ldap.properties file. Instead, after the installer completes successfully, you provide the default LDAP paramters by running the
Change Default LDAP Parameters application process. Later, you decide to run the installer again, as shown below, after changing one setting in the qd.properties file. Because you did not provide a link to the ldap.properties file in the qd.properties file the first time that you ran the installer, you must do so now, and the ldap.properties file must contain the same settings that you previously specified when you ran the
Change Default LDAP Parameters application process. Otherwise, the installer removes your parameter settings from the
Change Default LDAP Parameters application process.
- Run the installer and specify the COMPONENT_ONLY argument, which directs the installer to update the Rational_QD_Application_60x component and the Rational_QD_SystemPre-Requisite_60x component but not perform any of the other installation tasks. For example:
C:\qd>java -jar install.jar C:\qd.properties COMPONENT_ONLY
Miscellaneous
Notes:
- Throughout the IBM Quick Deployer wiki the screen captures are for reference only.
In some cases if the functionality they display has not changed in the latest release they will be from a previous release
Related topics:
External links: