Online migration upgrade steps

This topic describes how to perform the upgrading steps for online migration of the project contents from IBM Rational® Requirements Composer version 2 to version 3.0.1.

Before you begin

Follow the steps in the topic Upgrading offline to 3.0.1 using the upgrade script before you begin these steps. While performing the online migration, these conditions apply:

Note: If your online migration fails, restore the Jazz Team Server version 3.0.1 server, database and server/conf directory that you backed up after completing the offline upgrade, and run the online migration again.

Procedure

  1. Start all version 3.0.1 servers. Ensure that you have started the server by following the instructions in Deploying and starting the server.
  2. Open your browser, clear the browser cache, and navigate to the RM web client. Specify the server name and port in the following URL: https://server:port/rdm/web/projects/migration. The default port is 9443. This page detects that a migration is in progress and starts the Migration wizard.
  3. Accept the Rational Requirements Composer - Analyst Client Access license.
  4. Click Open Migration Service Panel and click to use the Migration wizard to start the Rational Requirements Composer migration. Status is reported to the administrator on the migration web page about which storage area is being processed and when it has begun indexing while the migration is in progress.
    Important: After the migration begins, you cannot cancel this operation until the migration is complete.
  5. After the migration is complete, the Rational Requirements Composer data is reindexed.
  6. After the reindexing is complete, the application performs validation and consistency checks on the migrated data and provides feedback to the administrator. The message "The Migration is complete" is displayed. Click Next. You can review the contents of the migrated projects by clicking the link on the Review Migration results panel. Otherwise, click Next.
  7. At this point, you can update any project links that point to your database.
    Note: To update the links later, click Close. You can update the links anytime by selecting Update Project Links from the Administration menu item.
  8. Status is reported to the administrator as the projects are updated. You might be prompted for login details for remote servers. Click Close when complete.
    Note: If there were errors, you can try to update the links again by selecting Update Project Links from the Administration menu item.
  9. After the migration is complete, if you have not already installed Jazz Team Server version 3.0.1, then run the Jazz Team Server setup wizard to ensure that the data warehouse database is configured for the new Jazz Team Server and RM is registered correctly with the Lifecycle Project Administration application. For more information, see the topics in Running the setup wizard and Configuring the server.
  10. Update your reports. If you used Rational Publishing Engine custom report templates in Rational Requirements Composer version 2, you must migrate the reports to use the Rational Requirements Composer version 3.0.1 schema. For details, see https://jazz.net/wiki/bin/view/Main/RRC3MigrationOfRRC2CustomReports.
  11. After the migration has been finalized, verify the following items in your configuration files.
    • The RM application is registered with the Jazz Team Server. (You can view this from the server admin page by clicking on the Registered Applications link from the left navigation panel.)
    • The RDM dashboard is available. (Click the link at the end of the migration to access the dashboard.)
    • The imported content is available.

      For details, see Verifying the upgrade.

  12. If you begin with integrations of version 2 applications, and you only upgrade Rational Requirements Composer and the Jazz Team Server to version 3.0.1, you must manually edit the friendsconfig.rdf file on the version 2 Rational Team Concert and Rational Quality Manager servers to ensure that dashboard viewlets (widgets) function correctly in those applications:
    Note: If you upgrade the version 2 Change and Configuration Management (CCM) and Quality Management (QM) applications to version 3.0.1, the following fix is performed automatically. In that case, the following edits are not required.
    1. In a text editor, open the following file on the version 2 CCM and QM application servers: InstallDir/server/conf/jazz/friendsconfig.rdf.
    2. Revise the oauthDomain URI to point to /jts/rootservices on the Rational Requirements Composer server (replacing the value from version 2: /jazz/rootservices):
      <jfs:oauthDomain>http://rrc_hostname:9445/rdm/rootservices,http://jts_hostname:9445/jts/rootservices" />
    3. Save and close the friendsconfig.rdf files, and restart the version 2 application servers.
  13. If you plan to create PDFs of your reports, you must configure the com.ibm.rdm.fronting.server.publish.PDFFont property, in the fronting.properties file, to use a font that contains the Unicode characters of your locale if the default fonts do not support them. For example, Arial Unicode MS, included with Microsoft Office, is a font that you can use for optimal PDF report generation. A font name that contains the required characters must be configured in an operating system different than Microsoft Windows.

What to do next


Feedback