This section provides details about known limitations that
are related to migrating from IBM® Rational® Requirements Composer
version 2 to version 3.0.1.
These items are known limitations when migrating:
- Migrating Rational Requirements
Composer version 2 project archives is not supported.
- The host name of the version 3.0.1 server must be the same as
the host name for the version 2 server. This requires some coordination
with server and network administrators if you intend to upgrade or
physically move hardware.
- The context root for the Requirements Management web application
on migrated servers must continue to be /rdm to support migrated artifact
URLs and links.
- If you are using floating licenses, you must either activate and
apply a Trial Rational Requirements Composer -
Analyst CAL to the user performing the upgrade or your license server
must have version 3.0.1 licenses installed and a Rational Requirements Composer
- Analyst CAL must be assigned to the Rational Requirements Composer admin
user before offline migration.
- Rational Requirements Composer version
2 to version 3.0.1 migration occurs for an entire database. You cannot
migrate part of the database or migrate project-by-project.
- You cannot rollback the migration. The only recourse if a migration
is rejected is to restore the server from a previously generated backup
and attempt the migration again. Be sure to back up databases before
beginning a migration.
- Migrating Rational Publishing
Engine report templates is not supported.
- All URI references that use the rich-client based protocol (rpc://
protocol) will be broken after migration to Rational Requirements Composer
version 3.0.1. There is no rich (Eclipse) client in version 3.0.1.
- The migration can encounter non-critical errors. See https://jazz.net/wiki/bin/view/Main/RRC3UpgradeErrors for more information.
Note: Content on Jazz.net is governed
by the Jazz.net
Terms
of use and is provided as-is without warranties of any kind.