triniti.com

  • Increase font size
  • Default font size
  • Decrease font size

Upgrade packs

 

Download Upgrade packs, copy them to $TRINITI_HOME/MigBuild folder and run the following commands for upgrade software:

$ cd $TRINITI_HOME/MigBuild
$ sh upgrade.sh for Linux environment (or) upgrade.bat for Windows environment
  1. TDM Framework Upgrade packs
  2. CDM Upgrade packs
  3. TRI2 Upgrade packs
  4. DQD Upgrade packs
  5. PPM Upgrade packs
  6. UIRnR Upgrade packs

Mandatory activity before upgrading any Instance:

i) Make sure to maintain all the required properties in BuildPatch.properties ($TRINITI_HOME/BuildPatch.properties) file of target instance.

Please use Application Object Migration>>Reports>>Migration Tokens For Target Instance eWorksheet in TRI2 PROD instance to check the configured migration tokens for reference(select target instance as HLTRI2DV)

ii) Download and copy latest UpgradePackExecutor.class to $TRINITI_HOME/MigBuild path and download the Prerequisite Upgrade pack and execute in the target instance before executing any other Upgrade pack

Use java UpgradePackExecutor PrerequisiteUpgradePack.zip command to execute.

Please follow below steps to upgrade deployment:

i) $TRINITI_HOME/MigBuild folder should not contain any old Upgrade packs.

NOTE: If shellscript file or bat file is opening directly in the browser, please save the respective file using Ctrl+S with respective extension.

If any old Upgrade packs exist, please download Shellscript to create one folder and move all old Upgrade packs into it file for Linux environment (or) Bat file to create one folder and move all old Upgrade packs into it file for windows environment, copy it to $TRINITI_HOME/MigBuild path and execute it. It will create one folder with AllZipsInsideMigBuildFolder name in MigBuild folder and moves all existing older Upgrade packs into it.

ii) There should be one shell script file(upgrade.sh) (or) bat file(upgrade.bat) and one class file(UpgradePackExecutor.class) in $TRINITI_HOME/MigBuild path of deployment.

If those files do not exist, please download the following files and copy to $TRINITI_HOME/MigBuild folder

NOTE: If upgrade.sh file or upgrade.bat file is opening directly in the browser, please save the respective file using Ctrl+S with respective extension.

  1. upgrade.sh for Linux environment (or) upgrade.bat for Windows environment.
  2. UpgradePackExecutor.class
iii) Copy the downloaded upgrade packs to $TRINITI_HOME/MigBuild folder and execute $TRINITI_HOME/MigBuild/upgrade.sh file to upgrade deployment.

Note: Upgrade packs should be applied in proper sequence - For example, 2016 Q4 UpgradePack should be applied only after 2016 Q3 UpgradePack(in case of manual up-gradation) or use upgrade.sh shell script to upgrade deployment, so that it will only take care about applying of Upgrade packs in proper sequence.

iv) In case if any individual Upgrade pack has to be executed, please keep that Upgrade pack in $TRINITI_HOME/MigBuild/ path(Eg: Upgrade pack downloaded for particular migration using Migration Requests eWorksheet) and execute by using below command after navigating to $TRINITI_HOME/MigBuild path in putty.

java UpgradePackExecutor <Upgrade pack name>
You are here: Upgrade packs