RunningTheUpgradeManually < Deployment

Engineering Lifecycle Management Wiki - Deployment

Community information and contribution guidelines

TWiki > Deployment Web > DeploymentTroubleshooting > UpgradeTroubleshooting > CLMUpgradeTroubleshooting > RunningTheUpgradeManually

Revision 8 - 2015-05-27 - 17:04:10 - Main.sbagot

<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%">
---+!! <img src="" alt="" width="50" height="50" align="right"/> Running the upgrade manually
%DKGRAY% Authors: [[UpgradeTroubleshootingTeam][UpgradeTroubleshootingTeam]] <br>
Build basis: CLM 4.x and later
%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>

This page will discuss issues that arise when completing the upgrade process manually instead of running the upgrade scripts.

---++ Upgrade steps
|It is strongly recommended that you complete the CLM upgrade by using the Interactive Upgrade Guide and the upgrade scripts.|

---++ Manually running the upgrade
If you decide to bypass using the upgrade script, you will be running the repotools commands manually. The upgrade script runs the following commands:
<verbatim> repotools-<app> -migration_<app>_updateConfigurationFiles </verbatim>
<verbatim> repotools-<app> -addTables </verbatim>

As well as performs the following file merges:
   * Updates the teamserver.proprties files based on the information from the previous version
   * With the RM application, the old version friendsconfig.rdf file is merged, which contains the list of servers set up for cross-repository integration with the new version
   * In a Tomcat environment, merges the content of server.xml and web.xml files with the new version and copies the old version tomcat-users.xml file
   * The JTS upgrade script will also upgrade the Data Warehouse

---+++ Updating the configuration files
Navigate to [[https://jazz.net/wiki/bin/view/Deployment/UpdateConfigurationFiles][Updating the Configuration Files]] for information on known issues which may occur at this step.

---+++ Adding the database tables
Navigate to [[AddDatabaseTables][Adding the Database Tables]] for information on known issues which may occur at this step.

---+++ Upgrading the data warehouse
Navigate to [[UpgradeDwSchema][Upgrading the DW Schema]] for information known issues which may occur at this step.

---+++++!! Related topics:

   * For more upgrade troubleshooting topics, refer to [[UpgradeTroubleshooting][Upgrade Troubleshooting]].
     
---+++++!! External links:          
   
   * None

---+++++!! Additional contributors: Main.StephanieBagot


<sticky></div></sticky>

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.