EditAttachPrintable
r4 - 2015-11-18 - 15:01:47 - AndreeaJurjYou are here: TWiki >  Deployment Web > DeploymentInstallingUpgradingAndMigrating > IoTContinuousEngineeringSolutionUpgrading

Upgrading the IBM Internet of Things Continuous Engineering Solution under construction

Authors: AndreeaJurj
Build basis: Version 6.0.1

To upgrade the IBM Internet of Things (IoT) Continuous Engineering Solution, install the new application versions, update configuration files, add, or update tables in existing database repositories, and upgrade the data warehouse.

Supported upgrade paths

If you upgrade multiple products that are running on multiple application servers, those applications continue to run on separate application servers after the upgrade. You cannot merge multiple applications into a single application server. However, you can register multiple applications with the same Jazz™ Team Server.

Planning checklist

Use this planning checklist to ensure that you are ready to upgrade:

  1. Use the software product compatibility reports: On the Software product compatibility reports page, you can search and generate reports for a specific product. The reports help you determine prerequisites, national language support, end of service, server virtualization environments, and more.
    Use the Software product compatibility report generator.
  2. Gather required information: Before starting the upgrade process, you must gather and record specific data that is required during the upgrade process, such as URLs, user IDs and passwords, database locations, name of databases installed, and so on.
  3. Verify that your hardware and software meet the minimum system requirements: To learn about new requirements, and to see whether your current system meets the minimum requirements, read the Detailed system requirements for the IoT Continuous Engineering Solution.
  4. Get the product installation media: For local repository download, you need approximately 5 GB of hard disk space to download and extract your product installation media for each product.
  5. Plan for your applications to be unavailable: Your applications are unavailable for a brief period while you back up your data, and update your applications. All applications that are connected to the Jazz Team Server are offline while the Jazz Team Server is offline. Be sure to provide time to completely back up your existing applications.
  6. Learn about licensing: You might have to obtain new licenses for the new versions of the products. The new licenses are compatible with previous application versions, but new application versions do not work with old licenses.
    The licensing scheme for most products is role-based. When you purchase a role-based license for an application, you have read, write, and comment access to some or all of the capabilities of that application. Read about licensing.
  7. Meet your database prerequisites:
    • DB2:
      • Ensure that you have the correct user name and password. On UNIX systems, get the password for the DB2® instance owner, which is typically the db2inst1 user.
      • Back up your database before you start the upgrade process.
      • Before you start the upgrade process, verify the integrity of the database by running the -verify repotools command.
      • More information: Backing up and restoring a DB2 database, [[http://www.ibm.com/support/knowledgecenter/SSYMRC_6.0.1/com.ibm.jazz.install.doc/topics/r_repotools_verify.html][Repository tools command to verify the integrity of a database]
    • Derby: Ensure that you can access the previous release database and copy the derby/repositoryDB directory.
    • Oracle:
      • You have the correct user name and password.
      • Before you start the upgrade process, verify the integrity of the database by running the -verify repotools command.
      • You backed up your database before you started the upgrade process. For more information about backing up databases, see your database vendor documentation.
      • You are using JRE version 6.0 or 7.0, and you are using the ojdbc6.jar driver.
      • You created an environment variable named ORACLE_JDBC_DRIVER_FILE and pointed to the C:\app\user\product\11.2.0\dbhome_1\jdbc\lib\ojdbc6.jar JDBC driver.
      • More information: Setting up an Oracle database
    • MySQL:
      • You have the correct user name and password.
      • Before you start the upgrade process, verify the integrity of the database by running the -verify repotools command.
      • You backed up your database before you started the upgrade process. For information about backing up databases, see your database vendor documentation.
      • You ensured that the Java™ Database Connectivity (JDBC) driver is installed, and you are using sqljdbc4.jar.
      • You created an environment variable named SQLSERVER_JDBC_DRIVER_FILE and pointed to the C:\MSSQL\jdbc\sqljdbc4.jar JDBC driver.
      • The SQL service is started.
      • More information: Setting up an SQL Server database
  8. Understand the upgrade process: Learn about the upgrade process, and how the upgrade affects your deployment.

Upgrade constraints

  • Each Jazz Team Server must be at the same level as the highest version of the product that is registered to it.
  • If you install the Jazz Team Server and an application using the 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.

Upgrade path overview

Upgrade your applications in this order:

  1. Jazz Team Server version 6.0.1 (if on the same application server as other applications)
  2. Rational solution for Collaborative Lifecycle Management version 6.0.1: Rational Team Concert, Rational DOORS® Next Generation, Rational Quality Manager, Jazz Reporting Service (Report Builder and Lifecycle Query Engine), Global Configuration, Rational Engineering Lifecycle Manager, and Design Management
  3. Rational DOORS and DOORS Web Access version 9.6.1.4
  4. Rational Rhapsody version 8.1.4

It is not necessary to upgrade all the products and components. Ensure that you meet the requirements that are listed under Upgrade constrains.

Upgrading applications by using the CLM Interactive Upgrade Guide

Follow the instructions in the Rational solution for Collaborative Lifecycle Management documentation to upgrade the following applications: Jazz Team Server, Rational Team Concert, Rational DOORS Next Generation, Rational Quality Manager, Jazz Reporting Service (Report Builder and Lifecycle Query Engine), Global Configuration, Rational Engineering Lifecycle Manager, and Design Management.

Install the new version of the product, update configuration files, add or update tables in existing database repositories, and upgrading the data warehouse.

For an overview of the upgrade process, read Upgrading the Rational solution for CLM.

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

To learn the step by step procedure, see the Rational solution for Collaborative Lifecycle Management Interactive Upgrade Guide.

Upgrading Rational Engineering Lifecycle Manager queries

To upgrade Rational Engineering Lifecycle Manager queries, see Migrating queries to version 6.0.1.

Upgrading Rational DOORS and DOORS Web Access

To upgrade Rational DOORS, back up all DOORS data, and then install Rational DOORS to a new directory while the previous version is removed. Instructions for upgrading Rational DOORS are available in the Rational DOORS documentation in the section titled: Upgrading from a previous version.

Upgrading Rational Rhapsody

To upgrade Rational Rhapsody, back up your data, uninstall the existing version of Rational Rhapsody, and install the new version. Instructions for upgrading Rational Rhapsody are available in the Rational Rhapsody documentation.

Related topics:

External links:

Edit | Attach | Printable | Raw View | Backlinks: Web, All Webs | History: r8 | r6 < r5 < r4 < r3 | More topic actions...
 
This site is powered by the TWiki collaboration platformCopyright © by the 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.
Ideas, requests, problems regarding the Deployment wiki? Create a new task in the RTC Deployment wiki project