Upgrading to version 3.0.1 fix pack releases

Use this topic to upgrade your existing Rational® solution for CLM products to version 3.0.1 fix pack releases.

Before you begin

Important:
  • In the examples below, 3.0.1 refers to the directory where the version 3.0.1 server is installed and 3.0.1.x refers to the directory where the new version 3.0.1 fix pack (3.0.1.1 or higher) server is installed.
  • All examples are for Linux. You must modify accordingly for Windows or other operating systems.
  • The upgrade process for 3.0.1 to 3.0.1 fix pack release uses the existing CLM database. The addTables and createWarehouse commands will update these databases to the 3.0.1.x formats.
  • If you have installed all Jazz™ applications on the same application server, then you must upgrade all applications to 3.0.1 fix pack at the same time. If you have deployed each application into a separate application server, then the applications can be upgraded independently.
  • Do not run jts/setup. Everything is already setup. Use jts/admin to view or change the setup.
  • Both instructions to use the upgrade wrapper script, and to perform the upgrade manually are provided.

Upgrading from version 2

About this task

Instructions for upgrading from version 2 to 3.0.1 fix pack releases are the same as upgrading from version 2 to 3.0.1. For detailed information, see Upgrading to the Rational solution for CLM.

Upgrading from version 3.0.1 using Tomcat

Procedure

  1. Install CLM 3.0.1.x. Do not run setup. For distributed configurations, install the CLM 3.0.1.x application corresponding to the 3.0.1 application you already have installed.
    Note: You must always upgrade the Jazz Team Server first.
  2. Stop the 3.0.1 server.
  3. If using Derby, move the Derby DB from 3.0.1 to 3.0.1.x:
    cp -R <3.0.1_install_dir>/server/conf/jts/derby/repositoryDB  <3.0.1.x_install_dir>/server/conf/jts/derby
    cp -R <3.0.1_install_dir>/server/conf/ccm/derby/repositoryDB  <3.0.1.x_install_dir>/server/conf/ccm/derby
    cp -R <3.0.1_install_dir>/server/conf/qm/derby/repositoryDB  <3.0.1.x_install_dir>/server/conf/qm/derby
  4. If using DB2®, Oracle, or SQL Server, backup the database.
  5. If using the upgrade wrapper scripts, skip to step 11
  6. Preserve your 3.0.1 user registry files.
    1. If using the Tomcat user registry, preserve your 3.0.1 tomcat-users.xml and server.xml files:
      cp <3.0.1_install_dir>/server/tomcat/conf/tomcat-users.xml  <3.0.1.x_install_dir>/server/tomcat/conf/tomcat-users.xml
      cp <3.0.1_install_dir>/server/tomcat/conf/server.xml <3.0.1.x_install_dir>/server/tomcat/conf/server.xml
    2. If using an LDAP user registry, preserve your 3.0.1 server.xml and web.xml files on the appropriate application servers:
      cp <3.0.1_install_dir>/server/tomcat/conf/server.xml <3.0.1.x_install_dir>/server/tomcat/conf/server.xml
      cp <3.0.1_install_dir>/server/tomcat/webapps/admin/WEB-INF/web.xml <3.0.1.x_install_dir>/server/tomcat/webapps/admin/WEB-INF/web.xml
      cp <3.0.1_install_dir>/server/tomcat/webapps/jts/WEB-INF/web.xml <3.0.1.x_install_dir>/server/tomcat/webapps/jts/WEB-INF/web.xml
      cp <3.0.1_install_dir>/server/tomcat/webapps/ccm/WEB-INF/web.xml <3.0.1.x_install_dir>/server/tomcat/webapps/ccm/WEB-INF/web.xml
      cp <3.0.1_install_dir>/server/tomcat/webapps/qm/WEB-INF/web.xml <3.0.1.x_install_dir>/server/tomcat/webapps/qm/WEB-INF/web.xml
      cp <3.0.1_install_dir>/server/tomcat/webapps/rm/WEB-INF/web.xml <3.0.1.x_install_dir>/server/tomcat/webapps/rm/WEB-INF/web.xml
  7. Copy your JFS/text indices from 3.0.1 to 3.0.1.x. (For distributed systems, got to the appropriate server to copy the files.)
    cp -R <3.0.1_install_dir>/server/conf/jts/indices <3.0.1.x_install_dir>/server/conf/jts
    cp -R <3.0.1_install_dir>/server/conf/ccm/indices <3.0.1.x_install_dir>/server/conf/ccm
    cp -R <3.0.1_install_dir>/server/conf/qm/indices <3.0.1.x_install_dir>/server/conf/qm
  8. Copy your application configuration files from 3.0.1 to 3.0.1.x. (For distributed systems, go to the appropriate server to copy the files.)
    cp <3.0.1_install_dir>/server/conf/jts/teamserver*.properties  <3.0.1.x_install_dir>/server/conf/jts
    cp <3.0.1_install_dir>/server/conf/ccm/teamserver*.properties  <3.0.1.x_install_dir>/server/conf/ccm
    cp <3.0.1_install_dir>/server/conf/qm/teamserver*.properties  <3.0.1.x_install_dir>/server/conf/qm
    cp <3.0.1_install_dir>/server/conf/admin/admin.properties*  <3.0.1.x_install_dir>/server/conf/admin
    cp <3.0.1_install_dir>/server/conf/admin/friends.rdf*  <3.0.1.x_install_dir>/server/conf/admin
    cp <3.0.1_install_dir>/server/conf/rm/fronting.properties  <3.0.1.x_install_dir>/server/conf/rm
    cp <3.0.1_install_dir>/server/conf/rm/friendsconfig.rdf  <3.0.1.x_install_dir>/server/conf/rm
  9. Run the repotools -addTables command to ensure the database has the correct tables. (For distributed systems, go the appropriate server and run the repotools command.)
    cd <3.0.1.x_install_dir>/server
    ./repotools-jts.sh -addTables noPrompt
    ./repotools-ccm.sh -addTables noPrompt
    ./repotools-qm.sh -addTables noPrompt
  10. If you have a data warehouse configured, run the repotools-jts -createWarehouse command to update the data warehouse schema to 3.0.1.x.
    cd <3.0.1.x_install_dir>/server
    ./reportools-jts.sh -createWarehouse
  11. If using the upgrade wrapper scripts, cd to the <3.0.1.x_install_dir>/server directory.
    upgrade/jts_upgrade.sh -oldJTSHome <3.0.1_install_dir>/server/conf
    upgrade/ccm_upgrade.sh -oldApplicationHome <3.0.1_install_dir>/server/conf
    upgrade/qm_upgrade.sh -oldApplicationHome <3.0.1_install_dir>/server/conf
    upgrade/rm_upgrade.sh -oldApplicationHome <3.0.1_install_dir>/server/conf
  12. Start the servers.
  13. Activate the 3.0.1.x licenses if necessary. For example, with milestone releases, you must activate the Early Access Licenses shipped with the milestone. For the 3.0.1.x final release, you can continue to use your 3.0.1 licenses.
    1. Login as an Administrator to the 3.0.1.x Jazz Team Server.
    2. Navigate to the Server Administration > License Key Management page and activate the licenses.
    Note: You do not need to run setup on the 3.0.1.x system since everything is already setup.

Upgrading from version 3.0.1 using WebSphere Application Server

Procedure

Note: If your environment does not support converter, for example, AIX or Solaris, you must install the 3.0.1.x version of the converter.war on the dedicated converter. For detailed information see, Rational Requirements Composer converter application installation.

  1. Install CLM 3.0.1.x. Do not run setup. For distributed configurations, install the CLM 3.0.1.x application corresponding to the 3.0.1 application you already have installed.
    Note: You must always upgrade the Jazz Team Server first.
  2. Back up the WebSphere® Application Server profile.
    1. Open a command prompt and change to the <WAS_Install>/bin directory. For example, /opt/IBM/WebSphere/AppServer/profiles/AppSrv01/bin.
    2. Run the following command:
      ./backupConfig <path to a new compressed file to create back up of profile> (for example ./backupConfig /root/was_backups/clm_301_profile.zip)
      Note: The backed up profile can be restored if needed by running the ./restoreConfig command. For example, ./restoreConfig /root/was_backups/clm_301_profile.zip.
  3. Uninstall the 3.0.1 applications from WebSphere Application Server.
    1. Log on to the WebSphere Application Server Integrated Solutions Console at https://<host name>:9043/ibm/console/logon.jsp.
    2. Click Applications > Applications Types > WebSphere enterprise applications.
    3. Write down the security roles mapping of the jts_war, ccm_war, and qm_war 3.0.1 applications to assist you with remapping them for the 3.0.1.x counterparts in step 16
    4. Stop and uninstall the following 3.0.1 applications: jts_war, admin_war, ccm_war, qm_war, rm_war, clmhelp_war, converter_war.
    5. Save the changes to the master configuration when prompted.
  4. Update JAZZ_HOME and log4j.configuration custom properties.
    1. Log on to the WebSphere Application Server Integrated Solutions Console at https://<host name>:9043/ibm/console/logon.jsp.
    2. Click Servers > Server Types > WebSphere application servers.
    3. Click the server name to open it. The default server name is server1.
    4. Under Server Infrastructure section click Java and Process Management > Process definition.
    5. Under Additional Properties click Java Virtual Machine.
    6. Under Additional Properties click Custom properties.
    7. Click JAZZ_HOME and update its value to file:///<3.0.1.x_install_dir>/server/conf. For example, file:///opt/IBM/JazzTeamServer_3.0.1.x/server/conf.
    8. Click log4j.configuration and update its value to file:///<3.0.1.x_install_dir>/server/conf/startup_log4j.properties. For example, file:///opt/IBM/JazzTeamServer_3.0.1.x/server/conf/log4j.properties.
    9. If you are connecting to Oracle or SQL Server database, ensure that ORACLE_JDBC_DRIVER_FILE or SQLSERVER_JDBC_DRIVER_FILE is pointing to the correct JDBC drive file.
    10. Save the changes to the master configuration when prompted.
      Note: For detailed information, see Setting up a WebSphere Application Server.
  5. Stop the WebSphere Application Server.
  6. Remove the CLM related contents from the wstemp and temp directories in the profile. Depending on previous installed applications, the following directories are present under profile and can be removed: jts_war, admin_war, ccm_war, qm_war, rm_war, clmhelp_war, converter_war.
    <profile directory>/wstemp (for example /opt/IBM/WebSphere/AppServer/profiles/AppSrv01/wstemp)
    <profile directory>/temp (for example /opt/IBM/WebSphere/AppServer/profiles/AppSrv01/temp)
  7. Remove the CLM related logs form the logs directory in the profile .
    <profile directory>/logs (for example /opt/IBM/WebSphere/AppServer/profiles/AppSrv01/logs)
  8. Prepare the databases for the CLM 3.0.1.x applications.
    1. If using Derby, move the Derby DB from 3.0.1 to 3.0.1.x:
      cp -R <3.0.1_install_dir>/server/conf/jts/derby/repositoryDB  <3.0.1.x_install_dir>/server/conf/jts/derby
      cp -R <3.0.1_install_dir>/server/conf/ccm/derby/repositoryDB  <3.0.1.x_install_dir>/server/conf/ccm/derby
      cp -R <3.0.1_install_dir>/server/conf/qm/derby/repositoryDB  <3.0.1.x_install_dir>/server/conf/qm/derby
    2. If using DB2, Oracle, or SQL Server, backup the database.
  9. If using the upgrade wrapper scripts, skip to step 14
  10. Copy your JFS/text indices from 3.0.1 to 3.0.1.x. (For distributed systems, got to the appropriate server to copy the files.)
    cp -R <3.0.1_install_dir>/server/conf/jts/indices <3.0.1.x_install_dir>/server/conf/jts
    cp -R <3.0.1_install_dir>/server/conf/ccm/indices <3.0.1.x_install_dir>/server/conf/ccm
    cp -R <3.0.1_install_dir>/server/conf/qm/indices <3.0.1.x_install_dir>/server/conf/qm
  11. Copy your application configuration files from 3.0.1 to 3.0.1.1. (For distributed systems, go to the appropriate server to copy the files.)
    cp <3.0.1_install_dir>/server/conf/jts/teamserver*.properties  <3.0.1.x_install_dir>/server/conf/jts
    cp <3.0.1_install_dir>/server/conf/ccm/teamserver*.properties  <3.0.1.x_install_dir>/server/conf/ccm
    cp <3.0.1_install_dir>/server/conf/qm/teamserver*.properties  <3.0.1.x_install_dir>/server/conf/qm
    cp <3.0.1_install_dir>/server/conf/admin/admin.properties*  <3.0.1.x_install_dir>/server/conf/admin
    cp <3.0.1_install_dir>/server/conf/admin/friends.rdf*  <3.0.1.x_install_dir>/server/conf/admin
    cp <3.0.1_install_dir>/server/conf/rm/fronting.properties  <3.0.1.x_install_dir>/server/conf/rm
    cp <3.0.1_install_dir>/server/conf/rm/friendsconfig.rdf  <3.0.1.x_install_dir>/server/conf/rm
  12. Run the repotools -addTables command to ensure the database has the correct tables. (For distributed systems, go the appropriate server and run the repotools command.)
    cd <3.0.1.x_install_dir>/server
    ./repotools-jts.sh -addTables noPrompt
    ./repotools-ccm.sh -addTables noPrompt
    ./repotools-qm.sh -addTables noPrompt
  13. If you have a data warehouse configured, run the repotools-jts -createWarehouse command to update the data warehouse schema to 3.0.1.x.
    cd <3.0.1.x_install_dir>/server
    ./reportools-jts.sh -createWarehouse
  14. If using the upgrade wrapper scripts, cd to the <3.0.1.x_install_dir>/server directory.
    upgrade/jts_upgrade.sh -oldJTSHome <3.0.1_install_dir>/server/conf
    upgrade/ccm_upgrade.sh -oldApplicationHome <3.0.1_install_dir>/server/conf
    upgrade/qm_upgrade.sh -oldApplicationHome <3.0.1_install_dir>/server/conf)
    upgrade/rm_upgrade.sh -oldApplicationHome <3.0.1_install_dir>/server/conf
  15. Start the WebSphere Application Server.
  16. Deploy the 3.0.1.x war files in WebSphere Application Server.
    1. Log on to the WebSphere Application Server Integrated Solutions Console at https://<host name>:9043/ibm/console/logon.jsp.
    2. Click Applications > Applications Types > WebSphere enterprise applications.
    3. Install the jts_war, admin_war, ccm_war, qm_war, rm_war, clmhelp_war, converter_war files.
    4. Map security roles appropriately for the following applications: jts_war, ccm_war, qm_war.
  17. While in the Enterprise Applications page, start the following applications: jts_war, admin_war, ccm_war, qm_war, rm_war, clmhelp_war, converter_war.
  18. Do a server reset for JTS, CCM, and QM:
    https://jts_server.mydomain.com:9443/jts/admin#action=com.ibm.team.repository.admin.serverReset
    https://ccm_server.mydomain.com:9443/ccm/admin#action=com.ibm.team.repository.admin.serverReset
    https://rqm_server.mydomain.com:9443/qm/admin#action=com.ibm.team.repository.admin.serverReset
    Note: You must restart the servers for the server reset to take effect.
  19. Activate the 3.0.1.x licenses if necessary. For example, with milestone releases, you must activate the Early Access Licenses shipped with the milestone. For the 3.0.1.x final release, you can continue to use your 3.0.1 licenses.
    1. Login as an Administrator to the 3.0.1.x Jazz Team Server.
    2. Navigate to the Server Administration > License Key Management page and activate the licenses.
    Note: You do not need to run setup on the 3.0.1.x system since everything is already setup.
    Note: For latest information about the upgrade process, see CLM Upgrading Knowledge Collection.

Feedback