E
dit
A
ttach
P
rintable
r13 - 2017-12-11 - 19:33:27 - Main.ktessier
You are here:
TWiki
>
Deployment Web
>
DeploymentInstallingUpgradingAndMigrating
>
IBMQuickDeployer
>
IBMQuickDeployerSetupAndRunV20
>
IBMQuickDeployerIFixSupportV20
<div id="header-title" style="padding: 10px 15px; border-width:1px; border-style:solid; border-color:#FFD28C; background-image: url(<nop>https://jazz.net/wiki/pub/Deployment/WebPreferences/TLASE.jpg); background-size: cover; font-size:120%"> ---+!! IBM Quick Deployer CLM and DM iFix Support Portal <img src="https://jazz.net/wiki/pub/Deployment/WebPreferences/updated.png" alt="updated.png" width="50" height="50" align="right"> %DKGRAY% %INCLUDE{"IBMQuickDeployerInsertAuthorBuildBasis"}% %ENDCOLOR%</div></sticky> <!-- Page contents top of page on right hand side in box --> <sticky><div style="float:right; border-width:1px; border-style:solid; border-color:#DFDFDF; background-color:#F6F6F6; margin:0 0 15px 15px; padding: 0 15px 0 15px;"> %TOC{title="Page contents"}% </div></sticky> <sticky><div style="margin:15px;"></sticky> 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.<br><i>Note: should this script need to be updated, a new version will be made available and can be downloaded and installed via [[IBMQuickDeployerIFixSupportV20#Update_the_install_ifix_py_scrip][this extra step]].</i> * 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. </br> ---++ 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 </br> ---++ 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 </br> ---++ !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. * [[%ATTACHURL%/install_ifix_engine_20170726-1410.zip][install_ifix_engine_20170726-1410.zip]] ---++++ 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 * [[%ATTACHURL%/CLM_604_iFix001_QDconfig.properties][CLM_604_iFix001_QDconfig.properties]] ---++++++ CLM 603 * [[%ATTACHURL%/CLM_603_iFix006_QDconfig.properties][CLM_603_iFix006_QDconfig.properties]] ---++++++ CLM 602 * [[%ATTACHURL%/CLM_602_iFix011_QDconfig.properties][CLM_602_iFix011_QDconfig.properties]] ---++++++ CLM 601 * [[%ATTACHURL%/CLM_601_iFix013_QDconfig.properties][CLM_601_iFix013_QDconfig.properties]] * [[%ATTACHURL%/CLM_601_iFix007_QDconfig.properties][CLM_601_iFix007_QDconfig.properties]] ---++++++ CLM 60 * [[%ATTACHURL%/CLM_60_iFix012_QDconfig.properties][CLM_60_iFix012_QDconfig.properties]] ---++++++ DM 604 * [[%ATTACHURL%/DM_604_iFix_1_QDconfig.properties][DM_604_iFix_1_QDconfig.properties]] * [[%ATTACHURL%/Rhapsody_DM_ModelServer_604_iFix_1_QDconfig.properties][Rhapsody_DM_ModelServer_604_iFix_1_QDconfig.properties]] ---++++++ DM 603 * [[%ATTACHURL%/DM_603_iFix_6_QDconfig.properties][DM_603_iFix_6_QDconfig.properties]] * [[%ATTACHURL%/Rhapsody_DM_ModelServer_603_iFix_6_QDconfig.properties][Rhapsody_DM_ModelServer_603_iFix_6_QDconfig.properties]] ---++++++ DM 602 * [[%ATTACHURL%/DM_602_iFix_11_QDconfig.properties][DM_602_iFix_11_QDconfig.properties]] * [[%ATTACHURL%/Rhapsody_DM_ModelServer_602_iFix_11_QDconfig.properties][Rhapsody_DM_ModelServer_602_iFix_11_QDconfig.properties]] ---++++++ DM 601 * [[%ATTACHURL%/DM_601_iFix_7_QDconfig.properties][DM_601_iFix_7_QDconfig.properties]] * [[%ATTACHURL%/Rhapsody_DM_ModelServer_601_iFix_7_QDconfig.properties][Rhapsody_DM_ModelServer_601_iFix_7_QDconfig.properties]] </br> ---++ Update the *install_ifix.py* script that ships with Quick Deployer <font color=red>Currently this is the same file as included in Quick Deployer V2.0.</font><br><br> Follow these steps to update the *install_ifix.py* script that is contained in the *Rational_QD_Application_60x* UCD Component. 1. In a temporary folder, download and extract the *install_ifix.py* script from [[%ATTACHURL%/install_ifix_20170726-1410.zip][install_ifix_20170726-1410.zip]] 1. Navigate to the folder that contains the Quick Deployer package content. This should be the folder from which you ran the [[IBMQuickDeployerInstallingIntoUCD][installer]]. 1. 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: * *Change Default LDAP Parameters* application process - [[IBMQuickDeployerChangeDefaultLDAPParameters][Change the default LDAP parameters]] * *Change Default User Parameters* application process - [[IBMQuickDeployerChangeDefaultUserParameters][Change the default user parameters]] * *Change Default DB2 Database Parameters* application process - [[IBMQuickDeployerChangeDefaultDB2Parameters][Change default DB2 database parameters]] * *Change Default Oracle Database Parameters* application process - [[IBMQuickDeployerChangeDefaultOracleParameters][Change default Oracle database parameters]] 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. 1. Run the [[IBMQuickDeployerInstallingIntoUCD][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: <verbatim> C:\qd>java -jar install.jar C:\qd.properties COMPONENT_ONLY </verbatim> </br> <!-- THE END --> %INCLUDE{"IBMQuickDeployerInsertMiscellaneous"}% <sticky></div></sticky>
E
dit
|
A
ttach
|
P
rintable
|
V
iew topic
|
Backlinks:
We
b
,
A
l
l Webs
|
H
istory
: r13
<
r12
<
r11
<
r10
<
r9
|
M
ore topic actions
Deployment.IBMQuickDeployerIFixSupportV20 moved from Deployment.IBMQuickDeployerIFixSupport on 2017-12-11 - 19:06 by Main.ktessier
-
Deployment
Deployment web
Planning and design
Installing and upgrading
Migrating and evolving
Integrating
Administering
Monitoring
Troubleshooting
Community information and contribution guidelines
Create new topic
Topic list
Search
Advanced search
Notify
RSS
Atom
Changes
Statistics
Web preferences
NOTE: Please use the Sandbox web for testing
Status icon key:
To do
Under construction
New
Updated
Constant change
None - stable page
Smaller versions of status icons for inline text:
Copyright © by IBM and non-IBM contributing authors. All material on this collaboration platform is the property of the contributing authors.
Contributions are governed by our
Terms of Use.
Please read the following
disclaimer
.
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more
here
.