Migrating the solution for systems and software engineering

Supported migration paths

The upgrade process is a side-by-side installation. Each product must be upgraded by installing the new version of the product and updating configuration files, adding or updating tables in existing database repositories, and upgrading the Data warehouse.

If you upgrade multiple products that were on multiple application servers, those applications will continue to run on separate application servers after the upgrade. It is not supported to merge multiple products into a single application server. However, you can still register multiple applications with the same Jazz™ Team Server application.

Before you begin

Before you migrate your products, go through the following checklist:
Table 1. Pre-update planning checklist
Planning task More information
Use the software product compatibility reports: On this page, you can search and generate reports for a specific product. The information includes prerequisites, product translation into a specific language, end of service, server virtualization environments, and more. Use the Software product compatibility report generator: http://publib.boulder.ibm.com/infocenter/prodguid/v1r0/clarity/index.html
Create an upgrade data sheet: On the upgrade data sheet, you can gather and record specific data that is required during the upgrade process, such as URLs and user IDs. To see a sample data sheet, refer to the Collaborative Lifecycle Management template: https://jazz.net/wiki/bin/view/Main/UpgradeDatasheet
Verify that your hardware and software meet the minimum system requirements: To learn about new requirements and to see if your current system meets the minimum requirements, click the System requirements link. Detailed System Requirements for Rational® Engineering Lifecycle Manager
Get the product installation media: For local repository download, you need approximately 5 GB of hard drive space to download and extract your product installation media for each product.  
Plan for your applications to be unavailable: Your applications will be unavailable for a brief period while you back up everything and update your applications. All of the applications that are connected to Jazz Team Server will be offline while Jazz Team Server is offline. Be sure to provide time to completely back up your existing applications.  
Learn about licensing: You may need to obtain new licenses for the upgraded versions of the products. The new licenses will be compatible with previous version applications, but updated applications do not work with previous licenses.

The licensing scheme for most products is role-based. When you purchase a role-based license, you will have read, write, and comment access to some or all of the capabilities of that application.

 
Meet your database prerequisites:
  • You have the correct user name and password. In the UNIX systems, get the password for the DB2® instance owner, which is typically the db2inst1 user.
  • You backed up your database before you started the upgrade process.
  • Jazz Team Server products (such as Rational Team Concert™) use the teamserver.properties file to record database connections, user names and passwords. The user in the teamserver.properties must have system administrator authority over the database.
  • If you are planning to create all databases on the same database server, verify that the Max number of concurrently active databases is set to a number greater than the actual number of active databases. If this value is lower than the number of active databases, you will get the SQL Code 1041 error.
 
Understand the upgrade process: Learn about the upgrade process and how the upgrade might affect your deployment.  

Upgrade constraints

The following guidelines will improve the success rate of your migration:
  • Each Jazz Team Server used must be at the same level as the highest version of the product registered to it.
  • If you install Jazz Team Server and an application using Jazz Team Server (such as Rational Team Concert) on the same WebSphere® Application Server, you must apply any future service releases to both at the same time.

Migration path overview

The upgrade order to be followed should be:
  1. Jazz Team Server version 4.0.6 (if on the same application server as other applications)
  2. Configuration Application component
  3. Rational Team Concert and Rational Quality Manager version 4.0.6
  4. Rational DOORS® and DOORS Web Access version 9.5.2.1
  5. Rational Rhapsody® version 8.0.5
  6. Rational Rhapsody Design Manager version 4.0.6
  7. Rational Engineering Lifecycle Manager 4.0.6
It is not necessary to upgrade all of the products and components, so long as you meet the restrictions listed in the "Upgrade Constraints" section above.

Upgrading Rational Team Concert and Rational Quality Manager

Rational Team Concert and Rational Quality Manager should be upgraded following the directions in the Rational solution for Collaborative Lifecycle Management information center. The upgrade process is a side-by-side installation. Each product must be upgraded by installing the new version of the product and updating configuration files, adding or updating tables in existing database repositories, and upgrading the Data warehouse.

The following section of the information center provides an overview of the upgrade process, and the Interactive upgrade guide allows you to select the options applicable to your installation and determine the best upgrade path. Upgrading the Rational solution for CLM

Of particular importance is the topic: Understanding the deployment and upgrade process

Additional guidance can be found in the Rational solution for Collaborative Lifecycle Management 2012 Upgrade Guide.

Upgrading Rational DOORS and DOORS Web Access

Rational DOORS is not upgraded with a side-by-side install, but rather by backing up all DOORS data and then installing DOORS to a new directory while the previous version is removed.

Instructions for upgrading Rational DOORS can be found in the Rational DOORS Information Center in the section titled: Upgrading from a previous version

Upgrading Rational Rhapsody

Rational Rhapsody is upgraded by backing up your data, uninstalling the previous version of Rhapsody, and then installing the new version.

Instructions for upgrading Rhapsody can be found in the Rational Rhapsody Information Center in the section titled: Upgrading Rational Rhapsody

Upgrading Rational Rhapsody Design Manager

The Rhapsody Design Manager upgrade process is a side-by-side installation. It must be upgraded by installing the new version of the product and updating configuration files, and adding or updating tables in existing database repositories.

The instructions for upgrading Rhapsody Design Manager can be found in the following article: https://jazz.net/library/article/1138

Upgrading Rational Engineering Lifecycle Manager

The Rational Engineering Lifecycle Manager upgrade process is a side-by-side installation. It must be upgraded by installing the new version of the product and updating configuration files, and adding or updating tables in existing database repositories.

The instructions for upgrading Rational Engineering Lifecycle Manager can be found in the following article: Upgrading Rational Engineering Lifecycle Manager


Feedback