r39 - 2017-08-03 - 16:55:21 - RosaNaranjoYou are here: TWiki >  Deployment Web > DeploymentInstallingUpgradingAndMigrating > UpgradeInsider

constantchange.png Upgrade insider

Authors: RosaNaranjo
Build basis: Collaborative Lifecycle Management (CLM) 6.0, Collaborative Lifecycle Management (CLM) 5.0, The Rational solution for Collaborative Lifecycle Management 2012, Rational Team Concert 4.0.x, Rational Quality Manager 4.0.x, Rational Requirements Composer 4.0.x, Rational Reporting for Development Intelligence 2.0.x

This page has a list of concerns along with work items of interest all in the context of the Rational solution for Collaborative Lifecycle Management (CLM) 6.0.x upgrade capability.

new16.pngThis page has been updated with information for 6.0.4.

Bookmarks

Important

  • If you are planning to upgrade to the Rational solution for CLM, plan to upgrade to 6.0.4 or latest release. VERY IMPORTANT Check for the latest fix pack available at the time you begin planning to stage your upgrade. There can be fixes that help avoid serious upgrade issues and are hard to recover from.

* NOTE Do not select the Jazz Security Architecture SSO option during install of CLM 6.0 for an upgrade from 5.0.x. This feature should only be installed after the upgrade. If selected by mistake, you will not be able to logout of CLM and will have to re-install CLM 6.0 without the option.

  • Generate an interactive upgrade guide from the latest Knowledge Center so that you do not miss out on any important steps that have been added to the upgrade.

Where can I find workarounds, technotes or late-breaking updates for the 6.0.x release?

Workaround articles will be published on Jazz.net. A workaround article is a Jazz.net article that documents a single issue that is applicable to one or more GA releases. Here are some shortcuts to help you find what you need:

RTC 6.0.4 Workarounds

RQM 6.0.4 Workarounds

RDNG 6.0.4 Workarounds

Jazz Foundation 6.0.4 Workarounds

Jazz Reporting Service 6.0.4 Workarounds

RELM 6.0.4 Workarounds

Note: For v6.0.x, just replace 6.0.4 with 6.0.x in the URL to locate the workaround articles.

Updates

new16.pngRational DOORS Next Generation or Design Management upgrade to 6.0.4

If you are upgrading a version 6 release of Rational DOORS Next Generation or Design Management to version 6.0.4, the Interactive Upgrade Guide instructs you to query for whether artifacts have more than one current version, and, if so, to run the -repairMultipleVersionsMarkedAsCurrent repository tools command before the upgrade. This command addresses a known issue where concurrent changes to an artifact can cause version issues in configurations. The -repairMultipleVersionsMarkedAsCurrent repository tools command is available in the latest interim fix of each version 6 release. You must apply the latest interim fix before you can use the command. If you run the query and it detects more than one current version of an artifact, but the -repairMultipleVersionsMarkedAsCurrent repository tools command is not available, do not upgrade to version 6.0.4. Contact support.

Rational Quality Manager 5.x to 6.x upgrade

Attempts to upgrade to Rational Quality Manager 6.0 using online migration will not be possible. Support for 6.0.1 is being tracked with QM Support online migration for RQM 5.x to 6.x

Note that the upgrade guide is incorrect as well. See Workitem 361962

Reporting Upgrade 5.x to 6.0

  • In version 6.0, RRDI is no longer bundled with the CLM solution. Instead there is a Cognos BI Adapter package that is made available in the Optional Downloads page. This adapter needs to be installed along with a Cognos BI Server in order for RRDI reports to be used with CLM v6.0.

Rational DOORS Next Generation 4.x to 5.x upgrade

Attempts to upgrade from a 4.0.x release of IBM Rational Requirements Composer (RRC) or Rational DOORS Next Generation (RDNG) to 5.0 or higher results in all project areas being deleted.

If you use the Interactive Upgrade Guide to get your the instructions for your situation and you are running in an Enterprise Topology and are using WebSphere Application Server instead of Tomcat, the instructions for upgrading the Requirements Management application are not correct. Specifically, the step Run the -migration_rm_updateConfigurationFiles repotools command to merge the existing configuration files is missing the updateTomcatFiles=no parameter.

This is the incorrect command as it appears in the Interactive Upgrade Guide (the paths may be different depending on your situation):

./repotools-rm.sh -migration_rm_updateConfigurationFiles oldApplicationHome=/opt/IBM/JazzTeamServer/server/conf ignoreJTSVersionCheck

The correct command is as follows:

./repotools-rm.sh -migration_rm_updateConfigurationFiles oldApplicationHome=/opt/IBM/JazzTeamServer/server/conf ignoreJTSVersionCheck updateTomcatFiles=no

Rational Team Concert 4.0.x to 5.0.x upgrade

Upgrading to Rational Team Concert 5.0.x using online migration should only be attempted if the latest iFix for 5.0.x is used. Otherwise, there is a corruption problem with workspaces and streams as indicated by this bulletin: Using online Migration to migrate CCM server from 4.x to 5.x can result in corruption of streams and workspaces.

Rational Quality Manager 4.0.6

New feature of RQM 4.0.6 is the ability to upgrade artifacts while the server is still online. Read the following topic for more information. Online Migration

Rational Requirements Composer 4.0.3

As of this release, it is no longer necessary to have a 4.0 RM Analyst license installed to complete RM Online migration.  The issue was fixed by Jazz Foundation via License asserts should be suppressed during migration (249151)

The issue was initially submitted via Eliminate the need to have any license assigned in order to complete RM Online migration (65651)

Concerns

The IBM Support portal is a good place to look for any troubleshooting technotes regarding upgrade. Some notable ones are mentioned here but there are more if you search the Support portal for upgrade related technotes.

Email notifications after upgrading to 6.0.3

Email Notification may fail after upgrading to CLM 6.0.3

AddTable fails due to performance optimizations in DOORS Next Generation

Performance tuning recommendations modify the schema in a way the upgrade is not expecting

Performance issues after upgrading to DOORS Next Generation

Performance issues and CRRRW7556E after upgrading IBM Rational DOORS Next Generation (DNG) repository

Functional CALs disappear when upgrading from 3.0.1.x or 4.0 to 4.0.1 or later

http://rhnaranjo.wordpress.com/2013/03/01/upgrade-alert-license-package-changes-affect-some-upgrade-scenarios

CLM 4.0.x and WebSphere 8.0.0.5 - Disappearing dashboard BIRT report widgets

If you are planning to upgrade to version 4.0.x of the Rational solution for CLM or have version 4.0.x of the Rational solution for CLM installed and are upgrading to WebSphere Application Server 8.0.0.5, be aware of the problem discussed in work item BIRT reports and dashboard widgets are not working correctly with WAS 8.0.0.5 (242945) You will need to request a WebSphere Application Server fix (WSAS APAR PM79419 ) from IBM Software Support.  You can also choose to use WebSphere 8.0.0.4 or earlier, but be careful to NOT apply all the JIT patches or else the problem will resurface.  Note:  The workaround provided in this technote has been shown to be problematic and does not persist upon reboot.  http://www.ibm.com/support/docview.wss?uid=swg21616615

Upgrade order: RRDI 2.0.x and CLM 4.0.x

CLM should be upgraded first followed by RRDI.

Rational Insight 1.1.1 with the Rational solution for CLM 3.0.1.x

This is supported only if Jazz Team Server is at 4.0.0.x.  This means that the CCM, QM, and RM applications (distributed topology only) can be at 3.0.1.x and work with Rational Insight 1.1.1, but you have to also use the 'new with 1.1.1' data manager ETLs for 3.0.1.  The data manager ETLs that ship with Insight come in various flavors: ones that are for use with the Rational solution for CLM 3.0.1 and ones that are for use with the Rational solution for CLM 4.0.

Rational Insight 1.1.1.1 with the Rational solution for CLM 4.0

This is supported only if Jazz Team Server is at 4.0.1  This means that the CCM, QM, and RM applications (distributed topology only) can be at 4.0.0.x and work with Rational Insight 1.1.1.1, but you have to also use the 'new with 1.1.1.1' data manager ETLs for 4.0.  The data manager ETLs that ship with Rational Insight come in various flavors: ones that are for use with the Rational solution for CLM 4.0 and ones that are for use with the Rational solution for CLM 4.0.1.

Rational solution for CLM installations that use Oracle

Use 4.0.0.1 or later at a minimum or use 4.0.1 because 4.0 contained defects that affect upgrade. The two critical fixes that have to be present BEFORE doing the upgrade to 4.0 are documented.  The first fix is part of version 4.0.0.1 and should be the upgrade target release used rather than using the 4.0 GA release.

In the case of the "repotools -upgradeWarehouse" error, the fix does not work on an already attempted upgrade to the 4.0 GA release.  Rather, the customer was instructed to restore their data warehouse from backup before running the upgrade with the test fix applied.  This amounts to a data corruption of the data warehouse when you attempt and fail the upgrade using 4.0 GA code. For details, see Escalation 231794.

Errors upgrading the data warehouse

The upgrade script is not able to update the RICALM schema. Until this schema is updated, no DataManager ETLs can be executed. This issue only happens when a data warehouse is created by Rational Insight and later upgraded by the Rational solution for CLM. If the original data warehouse was created by the Rational solution for CLM, future upgrades work. A code fix is needed for this issue.

Jazz Team Server 4.0.1

In distributed topologies with various CLM applications deployed, you may attempt to upgrade Jazz Team Server to 4.0.1.  If you do plan to do this, be aware of the following:  If you use a version of Rational Requirements Composer that is earlier than 4.0.1, 4.0.0.2, or 3.0.1.6 and you upgrade Jazz Team Server to 4.0.1, the Requirements ETL job will fail to complete. For more details, see RM 4.0.0.1 ETL fails after upgrade of JTS to 4.0.1 (68057) comment 54.

Rational Requirements Composer 4.0.1

If you are upgrading to 4.0.1 from 3.0.1.x, see RRC online migration fails with licensing errors for rm_user (68474) below under Work items of interest

If you are upgrading to 4.0.1 from 2.x, see Can't create PDF/Word on RRC 4.0.1 for migrated artifacts from RRC 2.0.0.3->RRC3.0.1.5->RRC4.0.1 (68894) below under Work items of interest

Rational Requirements Composer 4.0

IMPORTANT UPDATE - ALERT: Critical stability update for Rational Requirements Composer 4.0 - this issue is significantly less pervasive than originally thought and can occur only under a more limited set of conditions.

Before you upgrade to Rational Requirements Composer 4.0, specifically for customers still at version 2.x, be aware of the issues in this work item: Technote required RRC3 fixes for RRC4 upgrade (60482). You must contact IBM Software Support for these repair tools that have been provided by development to address issues in Rational Requirements Composer 2.x based datasets after to upgrade to 3.0.1.x. If not already upgraded, use 3.0.1.4 or higher when upgrading from version 2.x. Prior to upgrading to version 4.0, make sure to validate your Rational Requirements Composer data and check the upgrade error logs for any issues. The Rational Requirements Composer development team has wiki pages that provide more information on how to proceed when encountering errors during the upgrade process. RRC3Upgrade Wiki

Default WebSphere profile port may change when using the WebSphereMigration Wizard

WebSphereprovides a tool to easily migrate WebSphereApplication Server (WAS) profiles from one version to another (for instance from 7.0.0.27 to 8.0.0.3). This tool can create a new application server profile on the destination version and while doing that it will attempt to assign the same default ports (9080 for insecure HTTP and 9443 for secure HTTPS), however if it detects a port conflict (for instance because another profile on the destination version is already using these ports) it will resolve this conflict by increasing all port numbers by 1 until a free port is found. For instance, if ports 9080 and 9443 are found to be in use, the migrated profile will be configured to use ports 9081 and 9444 (assuming these ports are free, otherwise the port numbers will be even higher).

Since the public URI must not change (outside of a Server Rename scenario), the port numbers need to be adjusted after the profile migration is complete. (Note: If there is a genuine port conflict the other application using the port(s) needs to be re-configured such that it doesn't occupy these ports before.) To adjust the ports, change the WC_defaulthost_secure and WC_defaulthost ports in the WebSphereIntegrated Solutions Console. You will also need to change the ports that are associated to the default_host virtual host accordingly.

Miscellaneous

  • Upgrade Rational Quality Manager first to avoid the incompatibility between a 4.0 Jazz Team Server and Rational Quality Manager 3.0.1.2 or earlier.  Only Rational Quality Manager 3.0.1.3 or later is compatible with the 4.0 DW schema.
  • Rational Requirements Composer 3.0.1.3 or earlier is not compatible with Jazz Team Server 4.0.  Snapshots broken:  Snapshot does not have any contents when only JTS is upgraded from 3.0.1.2 to 4.0 (54708). Use 3.0.1.4 or later in a mixed version topology.
  • Upgrade wrapper scripts improved -

    • If the index location from 3.0.1 has relative paths, it will copy indices to the 4.0 directory. (Tomcat only)
    • If index location from 4.0 is absolute, copy takes place if the 3.0.x index location differs from the 4.0 index location. The index location can remain the same in the 4.0 teamserver.properties file if it is a stable directory.
  • 'Run all data warehouse jobs' from JTS/admin page should be run after every upgrade phase is completed. The ETLs play a role in data validation.
Upgrade Scripts - Usage guidance

If CCM or QM + distributed + can mount Upgrade with upgrade scripts.
If CCM or QM + distributed + cannot mount Upgrade by using repotools (migration, addtables, etc.) commands.
If RM + distributed + can mount Upgrade with upgrade scripts.
If RM + distributed + cannot mount Upgrade by following the unique instructions documented in the 4.0.x interactive guide. (Select RM, distribute, no mount).
All other scenarios Upgrade with upgrade scripts.

Work items of interest

Rational Build Forge integration

N-1 Compatibility issue discovered, Change to IBuildForgeServicesLayerService.getProjects method signature breaks N-1 compatibility (217378)

Workaround:  The above issue affects the Rational Team Concert client, not JBE. There was a breaking API change that Rational Team Concert is unable to fix, which affects the Get Projects button in a Rational Build Forge build definition editor when a 3.0.1.x client is trying to connect to a 4.0 server.  The workaround is to use a 4.0 client to edit the build definition. After the build definition is set up, this does not affect other uses from a 3.0.1.x client; for example, users can request builds, view build results, etc.

Related topics: None

External links:

  • None

Additional contributors: DanToczala ChristianGlockner PaulEllis

Edit | Attach | Printable | Raw View | Backlinks: Web, All Webs | History: r39 < r38 < r37 < r36 < r35 | 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