r17 - 2017-07-28 - 21:38:18 - Main.ktessierYou are here: TWiki >  Deployment Web > DeploymentInstallingUpgradingAndMigrating > IBMQuickDeployerOld > IBMQuickDeployerUpdatingSystemPreReqParametersOld

IBM Quick Deployer updating Rational_QD_SystemPre-Requisite_60x* component parameters updated.png

Authors: ThomasPiccoli, KennethThomson, JenniferLiu, KenTessier, ClareCarty
Build basis: CLM 6.0, CLM 6.0.x, CE 6.0.x

Prior to running the UCD Install Applications application process, the out of the box installation of Quick Deployer requires you to run the following application processes

  • Change Default LDAP Parameters application process
  • Change the default user parameters application process
  • Change the default database parameters application process

Following the steps outlined below will allow you to permanently store your LDAP, user and database parameters in an updated version of the the UCD Rational_QD_SystemPre-Requisite_60x component. Once the component is updated the UCD Install Applications process can be run without first running the three Change Parameters processes.

Create UCD environment

By following these steps you can create the environment for this process
More information on creating an environment can be found in this topic - UCD environment construction
  1. Install a UCD agent on a single dummy Linux machine.
  2. Create a dummy application environment
    • Create a UCD resource
    • Create a UCD environment
    • Add the dummy agent to the environment
    • Map the Rational_QD_SystemPre-Requisite_60x component to the agent

Run UCD processes

  1. Run the Change Default LDAP Parameters process - Change the default LDAP parameters
  2. Run the Change Default User Parameters process - Change the default user parameters
  3. Optionally run the change default DB2 database parameters process - change default DB2 database parameters
  4. Optionally run the change default Oracle database parameters process - change default Oracle database parameters
  5. If you are going to use the Quick Deployer installed DB2 or Oracle database then you should have your database administrator review the configuration to make sure it conforms to internal security and reliability policies.

Update UCD Rational_QD_SystemPre-Requisite_60x component

  1. On the dummy linux machine confirm the following property files have been created
    • /IBMQD/UCDComponents/AutomationPrep/DatabaseParameters/DBParameter.properties
    • /IBMQD/UCDComponents/AutomationPrep/DatabaseParameters/oracleParameter.properties
    • /IBMQD/UCDComponents/AutomationPrep/UserParameters/userCreds.properties
    • /IBMQD/UCDComponents/AutomationPrep/CustomLDAP/Custom_LDAPSecurity.properties
  2. Copy the four files to a temporary folder (e.g. /tmp/defaultFolder)
  3. Expand the IBM Quick Deployer installation package into a temporary folder (e.g. /media/QD)
  4. Ensure the following files are present
    • versionUpdate.sh
    • componentVersionDownload.sh
    • componentVersionImport.sh
  5. Assign execute permission to the {agent install dir}/agent/opt/udclient/udclient script
  6. Assign execute permission to the versionUpdate.sh, componentVersionDownload.sh and componentVersionImport.sh scripts
  7. ensure JAVA_HOME is set. If not export JAVA_HOME={location of your jre} (e.g. /usr/lib/jvm/jre)
  8. ensure UCDCLIEXE is set. If not export UCDCLIEXE={location of your udclient exe} (e.g. /opt/ibm-ucd/agent/opt/udclient/udclient)
  9. Execute the versionUpdate.sh script
    The script expects 7 arguments:
    • USERNAME =UCDAdminUserName
    • USERPASSWORD =UCDAdminUserPassword
    • UCDSERVER =UCDURL (e.g. https://UCDHostName:8443)
    • COMPONENTNAME =the name of the component that will be updated, it has to be set Rational_QD_SystemPre-Requisite_60x
    • COMPONENTOLDVERSION =the existing version name of the target component being updated (e.g.
    • COMPONENTNEWVERSION =the new version name of the target component (e.g.
    • DEFAULTFILESOURCEFOLDER =the folder containing the updated properties files (e.g. /tmp/defaultFolder)

          cd /media/QD
          chmod 755 {agent install dir}/agent/opt/udclient/udclient
          chmod 755 versionUpdate.sh
          chmod 755 componentVersionDownload.sh
          chmod 755 componentVersionImport.sh
          export JAVA_HOME={location of your jre}
          export UCDCLIEXE={agent install dir}/agent/opt/udclient/udclient
          sh versionUpdate.sh USERNAME=adminuser USERPASSWORD=adminpassword UCDSERVER=https://UCDHostName:8443 COMPONENTNAME=Rational_QD_SystemPre-Requisite_602 COMPONENTOLDVERSION= COMPONENTNEWVERSION= DEFAULTFILESOURCEFOLDER=/tmp/defaultFolder | tee console_versionUpdate.log
          >> deleted console text <<
          SUCCESS [versionUpdate.sh]: component scripts updated and a new version added to UCD

Confirm the update happened

  1. Open the component version after the script is executed successfully, you should see the newer version is added to the component

    version list

  2. Click the Compare button to see the differences between the two versions

    version compare

Update fixed component versions

Be aware that if you have previously fixed the Rational_QD_SystemPre-Requisite_60x component version used by the Install Applications application process you should go back and update it to this new version. You do this using - Set fixed component versions



  • 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:

Additional contributors: MichelleCrane, NathanBak, ChristianLopez

Edit | Attach | Printable | Raw View | Backlinks: Web, All Webs | History: r17 < r16 < r15 < r14 < r13 | More topic actions
Deployment.IBMQuickDeployerUpdatingSystemPreReqParametersOld moved from Deployment.IBMQuickDeployerUpdatingSystemPreReqParameters on 2017-07-28 - 19:44 by Main.ktessier -
This site is powered by the TWiki collaboration platformCopyright © by the 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.