Upgrading Legacy Titan - Launch day steps

« Return to Notes Listing

Author:Aaron S.
Last Updated:April 21, 2022 8:45 AM

Overview

This provides an overview of steps for launch day upgrading a legacy Titan instance to v6.9.5 and v.7. Look for the below section that matches your instance.

 

v6.9 to v6.9.5

  1. Select Advanced Actions in TPI and select Mark as Not Installed for each package installed. If there have been multiple versions of a package installed, mark each one as not installed: 
    DO NOT reset TitanBase 6.9.0.0 or TPI. 
  2. Delete files global.asax, login.aspx and ping.aspx from /display root and /wkst root if they exist. 
  3. Remove urlrewriter from /display and /wkst web.config, save these to add them back later 
  4. Restore prod database backup over host-prod-2 database
  5. Run LegacyUpgradeDB script to upgrade to 6.9.0.0 
    M:\_tpi\LegacyUpgrades\DatabaseUpgrade\UpgradeLegacyDB.ps1 to upgrade to 6.9.0.0 
    1. This is only necessary if the instance is less than 6.9.0.0
  6. Install prod package, this should have dependencies on any other necessary packages (like Social Media Bookmarks if used). Once this installs successfully, navigate to display and wkst and confirm that everything is working. 
  7. Add urlrewriter to /display and /wkst web.config. Also add any other modules that are custom.  
  8. Copy FilePile from prod. 

    1. Robocopy \\host-prod-1\Files\Sites\[ClientID]\Titan\Public\FilePile \\host-prod-2\Files\Site\[ClientID]\Titan\Public\Wkst\FilesPile

  9. Run disk refresh and dtSearch Create jobs. 
  10. Update AD that prod environment is setup and DNS can be changed. 
  11. Request that DNS for .titanclient and wkst be changed to point to host-prod-2. Brian manages .titanclient.com DNS and these need to be updated seperately. 
  12. Request AD have client update DNS to point to host-prod-2. 
  13. Confirm that DNS has been updated correctly. Clients may miss a site. This is common and can cause a lot of errors. Confirm that client has properly updated DNS. Otherwise it could point to the old site. Taking the site offline in the next few days is also a quick way to confirm that everything is updated. 
  14. Once DNS is correct, take old site offline. 

 

v6.9 to v7.0

  1. On host-prod-2 add display, wkst, service, and platform sites to v7 App Pools.
  2. Select Advanced Actions in TPI and select Mark as Not Installed for each package installed. If there have been multiple versions of a package installed, mark each one as not installed: 
    DO NOT reset TitanBase 6.9.0.0 or TPI. 
  3. Delete files global.asax, login.aspx and ping.aspx from /display root and /wkst root if they exist. 
  4. Remove urlrewriter from /display and /wkst web.config, save these to add them back later 
  5. If this upgrade is from v6.9 to v7, reset the web.config to v6.9.5 values.(this should be the last version of 6.9.5 installed, if 6.9.5.74 was last installed then replace the 7.0 references with 6.9.5.74)
    1. reset bindings to 6.9.5 in display web.config
    2. reset bindings to 6.9.5 in wkst web.config
    3. remove system.codedom element in wkst web.config
    4. reset bindings to 6.9.5 in services web.config
    5. reset bindings to 6.9.5 in Services/DisplayServices web.config
    6. reset bindings to 6.9.5 in Wkst/App_Data/Jobs/Background/BackgroundService.config.exe
  6. Display and Wkst v7 dlls should be replaced with v6.9.5 dlls. Copy these from another v6.9.5 instance. If the v7 dlls aren't removed, the display and wkst will be unavailable after the restore.
  7. Restore prod database backup over host-prod-2 database
  8. Run LegacyUpgradeDB script to upgrade to 6.9.0.0 
    M:\_tpi\LegacyUpgrades\DatabaseUpgrade\UpgradeLegacyDB.ps1 to upgrade to 6.9.0.0 
    1. This is only necessary if the instance is less than 6.9.0.0
  9. In TPI, click on Configuration and add v7 Roots. The install will complete but files will be missing if this step is missed. 
  10. Install prod package, this should have dependencies on any other necessary packages (like Social Media Bookmarks if used). Once this installs successfully, navigate to display and wkst and confirm that everything is working.
  11. Install License packages
    1. Remove current license package and install equivalent license under NWS/License
    2. Install Total Care or Standard Maintenance Package by searching for Total Care in JIRA.
  12. Add urlrewriter to /display and /wkst web.config. Also add any other modules that are custom.  
  13. Copy FilePile from prod. 

    1. Robocopy \\host-prod-1\Files\Sites\[ClientID]\Titan\Public\FilePile \\host-prod-2\Files\Site\[ClientID]\Titan\Public\Wkst\FilesPile

  14. Run disk refresh and dtSearch Create jobs. 
  15. Update AD that prod environment is setup and DNS can be changed. 
  16. Request that DNS for .titanclient and wkst be changed to point to host-prod-2. Brian manages .titanclient.com DNS and these need to be updated seperately. 
  17. Request AD have client update DNS to point to host-prod-2. 
  18. Confirm that DNS has been updated correctly. Clients may miss a site. This is common and can cause a lot of errors. Confirm that client has properly updated DNS. Otherwise it could point to the old site. Taking the site offline in the next few days is also a quick way to confirm that everything is updated. 
  19. Once DNS is correct, take old site offline. 

 

v6.9.5 to v7.0:

  1. On host-prod-2 add display, wkst, services, and platforms sites to Titan v7 app pools. Display site should be in Titan v7 Display Sites, wkst should be in Titan v7 Wkst Sites, Services should be in Titan v7 Services Sites, Platorm site should be in Titan v7 Platform Sites. If these are not properly updated it can cause issue for this site and other sites in the app pool.
  2. In TPI, click on Configration and add v7 Roots. The install will complete but files will be missing if this step is missed.
  3. If your site has the package NWS.Titan.Base.Base installed, enable Show Advanced Options and then mark all versions of the package as Not Installed.  Finally, delete all versions.
  4. Install prod package, this should have dependencies on any other necessary packages (like Social Media Bookmarks if used). Once this installs successfully, navigate to display and wkst and confirm that everything is working. 
  5. Install License packages
    1. Remove current license package and install equivalent license under NWS/License
    2. Install Total Care or Standard Maintenance Package by searching for Total Care in JIRA.
  6. Log into the workstation and refresh app variables.
  7. Run disk refresh and dtSearch Create jobs. 
  8. Update Keepass to denote that client is now on v7.
  9. Update AD that upgrade is complete. 
top