Workarounds and Limitations: Known issues in Rhapsody Model Manager 6.0.6.1

Full-text search indexes must be rebuilt when you upgrade to 6.0.6.1 or later

First occurrence
6.0.6.1

Problem
In the 6.0.6.1 release, the Apache Lucene full-text search engine was upgraded to a more recent version. This upgrade requires all existing full-text search indexes that were created in 6.0.6 or earlier to be rebuilt. Full-text search indexes must be rebuilt for both the CLM servers and the Rational Team Concert Client for Eclipse IDE.

Workaround
Typically, when you upgrade an installation by using the upgrade scripts, the full-text search indexes from the earlier installation are copied to the new installation. However, the upgrade scripts in 6.0.6.1 and later do not copy previous indexes from version 6.0.6 or earlier (including interim fixes). Instead, the new server automatically rebuilds the indexes in the background after you start it. Results of full-text searches might be incomplete until the reindexing operation is finished; the progress of the reindex is periodically written to the server log file.

Alternatively, instead of allowing the server to rebuild full-text search indexes online, you can rebuild them manually by running the repotools-<app> -rebuildTextIndices command after the upgrade is complete, but before you start the server, where <app> is one of am, ccm, or qm. Note that reindexing might be a lengthy process and can take many hours for a large database. In the web client, a system alert in the banner states that reindexing is in progress.

If you follow a manual upgrade procedure instead of running the upgrade scripts, you must ensure that the full-text indexes are not copied from the old installation to the new installation. If the new installation is configured to use the same full-text index location as the old installation (the value of the com.ibm.team.fulltext.indexLocation property in the old and new teamserver.properties file is the same absolute path name), you must either run the repotools-<app> -rebuildTextIndices command before you start the server, or delete the contents of the folder at that location before you start the server. You might want to preserve the old contents if you decide to abandon the upgrade and roll back to the previous release.

If an application is clustered, the offline reindexing procedure (using repotools) or the online procedure (ensuring that the full-text index folder is empty before starting the server) must be performed on each node in the cluster.

The Rational Team Concert Client for Eclipse maintains a local full-text search index for the Team Artifact History view. When you upgrade the Rational Team Concert Client for Eclipse to version 6.0.6.1 or later, the full-text search index is automatically deleted, which means the artifact history is cleared and will accumulate artifacts again after the upgrade.

For CLM servers, complete one of these steps:

• For online background indexing, no action is required except to ensure that the full-text index folder is empty before you start the server
• For offline indexing before you start the server, run the appropriate repotools-<app> -rebuildTextIndices command.

Rational Rhapsody 8.3.1 and Rhapsody Design Manager are not updated from the server if you installed the feature to import Design Manager projects to Rhapsody Model Manager

First occurrence
6.0.6

Problem
If you install Rhapsody Model Manager, including the feature to import projects from Rhapsody Design Manager, and you open a Design Manager model in Rhapsody, the expected message that notifies you of updates to Rhapsody and the Design Manager client is not displayed.

Workaround
In the rhapsody.ini file, change the EnableDmToRmmMigration value to FALSE, and open the Design Manager model again. After the updates are applied, change the value of EnableDmToRmmMigration back to TRUE.

Related information
Work Item 69619

The Rhapsody Model Manager server and client require a locale setting for non-English support

First occurrence
6.0.6

Problem
Rational Rhapsody elements for non-English labels display incorrectly in the Rhapsody Model Manager web interface, unless the correct locale is set on the client machine.

Workaround
Manually set the locale on the client machine.

Related information

The Associate Change Request action in Rational Rhapsody requires a repository connection

First occurrence
6.0.6

Problem
If you want to associate a change request with a Rhapsody Model Manager change set that is in the Rational Rhapsody client, you must already have defined a Change and Configuration Management (CCM) repository connection in the Rational Team Concert Eclipse client. Otherwise, you get the following error:

Error while associating work item to change-set containing files
L:\Demo Sandbox\Model\Model_rpy;Pkg.sbsx
Failed to associate work-item https://server:9443/ccm/resource/itemName/com.ibm.team.workitem.WorkItem/10 to change-set:
Repository connection was not found for work item identified by the following URL:
https://server:9443/ccm/resource/itemName/com.ibm.team.workitem.WorkItem/10

Workaround
You need to create a new repository connection from the Rational Team Concert Eclipse client to the server that manages the work items:

1. Open the Rational Team Concert Eclipse client.
2. Create a new Jazz Repository Connection.
3. Specify the URI path to https://<server>:<port>/ccm/

Related information
Work Item 64639

An error occurs when you register Rhapsody Model Manager on a CLM server earlier than version 6.0.5 with WebSphere Application Server Liberty

First occurrence
6.0.5

Problem
After you upgrade to CLM version 6.0.5 or later, you must register Rhapsody Model Manager because the application did not exist before 6.0.5. If the initial installation of the CLM server was version 6.0.4 or earlier with WebSphere Application Server Liberty, when you try to register Rhapsody Model Manager, you receive the following error:

CRJAZ2081E: The server could not access the discovery URL for the application. If you have configured a virtual host for an application, the virtual hostname must be used in the URL for the application. 

The WebSphere Application Server Liberty configuration application.xml file, which is located in the <Installation Folder>/server/liberty/servers/clm/conf folder, does not contain an entry for the Architecture Management (AM) application. You receive this error because the configuration file was copied from the older version of the server, which does not include the Rhapsody Model Manager application.

Workaround
After the upgrade and before you register the Rhapsody Model Manager application, complete these steps:

1. Stop the server.
2. Open the <Installation Folder>/server/liberty/servers/clm/conf/application.xml file in a text editor.
3. Add the following content before the “<!–  Applications that delegate authentication to a JTS –>” comment:

  <application type=”war” id=”am” name=”am” location=”${server.config.dir}/apps/am.war”>
       <application-bnd>
           <security-role name=”JazzAdmins”>
               <group name=”JazzAdmins” />
           </security-role>
           <security-role name=”JazzProjectAdmins”>
               <group name=”JazzProjectAdmins” />
           </security-role>
           <security-role name=”JazzUsers”>
               <group name=”JazzUsers” />
           </security-role>
           <security-role name=”JazzGuests”>
               <group name=”JazzGuests” />
           </security-role>
       </application-bnd>
   </application>

4. Optional: During the installation, if you changed the default root context for the Rhapsody Model Manager application, make the corresponding changes to the <application …> tag entry:

• ID field
• Name field
• Name of the WAR file

5. Save the changes.
6. Start the server.
7. Register and configure Rhapsody Model Manager as usual.

Related information
Work Item 62574

Licensing errors might occur if you upgrade the Java environment or upgrade applications to 6.0.5

First occurrence
6.0.5

Problem
If you upgrade your version of Java to a fix pack that was built after April 2017, or you upgrade an application to version 6.0.5 or later and are using WebSphere Liberty, licensing errors might occur. The errors occur because earlier licenses were signed with the MD5 algorithm, which is now blocked by newer versions of Java.

For example, the License Key Management page for Jazz Team Server might display the following error in the Description field: CRJAZ1236I A development time license is being used. Similarly, the jts.log file might display the following error: CRJAZ0965I The file was not a valid server or client access license activation key.

The latest license files no longer contain the MD5 algorithm because IBM and Oracle Java introduced restrictions on JAR files that are signed with weak algorithms and keys.

Workaround
The licenses in the IBM Rational License Key Center were updated to use a different signature algorithm.

After you upgrade your server to version 6.0.5 or later, obtain the updated licenses from the IBM Rational License Key Center to replace your current licenses. If you previously used floating, token, or authorized user single install licenses, install their updated versions. Your existing user license assignments are kept during the installation of the updated licenses.

Important: If you are not upgrading all applications at the same time, you must apply an interim fix to the applications at earlier versions before you upgrade Jazz Team Server. The following interim fixes contain the compatible version of Java:

• 6.0.4 interim fix 007 and later
• 6.0.3 interim fix 010 and later
• 6.0.2 interim fix 015 and later
• No version of 5.0.2 contains a compatible Java version. For 5.0.2, complete the steps in the IBM Support flash article.

If you cannot apply the interim fix before the upgrade, upgrade Jazz Team Server and then complete the steps in the IBM Support flash article. If you do not apply the interim fix or complete the steps in the article, the internal licenses do not load on Jazz Team Server and the applications might experience issues.

To update your current license files, follow the instructions in the Interactive Upgrade Guide or complete the following steps based on the type of license:

For term (floating or authorized user) or token licenses:

Note: For token licenses, you are only required to download the jazztokens.zip file. You do not have to download the license.dat file because it does not contain changes.

1. Log in to Jazz Team Server, go to jts/admin > Server > License Key Management and note all the licenses on the server.
2. In IBM Rational License Key Center, under License Management, click Return Keys.
3. Click the product link that you want to return the license keys for, and then click Return.
4. After the license is returned, click Get Keys.
5. Click the product link to generate licenses for.
6. When prompted, provide the required information and click Generate.
7. Download the  file that contains the new licenses.
8. Log in to Jazz Team Server, go to Server > License Key Management and reimport the new license files.
9. To add a license, click Add, accept the license agreement if you agree to its terms, and then complete the steps in the wizard.

For non-term floating and authorized user licenses:

1. Log in to Jazz Team Server, go to jts/admin > Server > License Key Management and note all the licenses on the server.
2. In IBM Rational License Key Center, go to View keys by host or View keys by user.
3. Enter the information about the host or the user.
4. Select the product to generate the license for.
5. Click View Licenses for Selected Product Lines.
6. Select the license and click View Details.
7. Click Download Keys.
8. Log in to Jazz Team Server, go to Server > License Key Management and reimport the new license files.
9. To add a license, click Add, accept the license agreement if you agree to its terms, and then complete the steps in the wizard.

Note: If you imported trial licenses before the newer versions of Java were adopted, you might still receive errors in the jts.log file even after you import the updated licenses. For example, you might receive this error: CRJAZ0965I The file was not a valid server or client access license activation key. You can ignore these errors.

Related information
IBM Rational License Key Center
Interactive Upgrade Guide
Oracle release note: Restrict JARs signed with weak algorithms and keys

The Create Streams action for global configurations does not work for Rhapsody Model Manager snapshots

First occurrence
6.0.5

Problem
If you include a Rhapsody Model Manager snapshot in a global configuration and you run the Create Streams operation from the Rhapsody Model Manager snapshot, you might get the following error message: CM provider does not support stream creation.

Workaround
Manually remove the old stream and add the new stream.

Related information
Work Item 61489

The file path for the Rhapsody client on Windows is limited to 256 characters

First occurrence
6.0.5

Problem
It’s not possible to open and save a Rhapsody model to a path that is longer than 256 characters.

Workaround
It’s recommended to use a short path to the RTC sandbox folder to avoid reaching 256 characters.

Related information
Work Item 62000

You cannot associate a change request when you delete an OSLC link from Rational DOORS Next Generation or Rational DOORS

First occurrence
6.0.5

Problem
When you create an OSLC link from Rational DOORS Next Generation or Rational DOORS to Rhapsody Model Manager, you can associate a change request to track corresponding modifications.

However, when you try to delete an existing OSLC link from Rational DOORS Next Generation or Rational DOORS, you don’t have this ability, because these applications do not provide a dialog box where you can select a change request.

If the Require Work Items and Comments precondition is selected on the server side for a given project area, deleting the link fails with an error message.

Workaround
This workaround is available starting in 6.0.5 interim fix 001:

1. Navigate from Rational DOORS Next Generation to Rhapsody Model Manager by clicking the OSLC link that you want to delete.
2. In Rhapsody Model Manager, delete the existing OSLC link, and then you can select a change request to associate with the change set.

Related information
Work Item 62435

Link validity status is displayed only in projects that are enabled for configuration management

First occurrence
6.0.6.1

Problem
In Rhapsody Model Manager, link validity status is displayed only in projects that are enabled for full configuration management (for use with global configurations) on the Configuration Management page of Application Administration.

Related information
Work Item 70042

Rhapsody Model Manager does not integrate with Rhapsody Gateway

First occurrence
6.0.5

Problem
You cannot use Rational Rhapsody Gateway for models stored on the Rhapsody Model Manager server. To manage traceability for requirements, use the Remote Artifacts OSLC integration with Rational DOORS.

Related information
Work Item 69166

Rational Rhapsody client for Rhapsody Model Manager does not display link validity information

First occurrence
6.0.5

Problem
In Rational Rhapsody, link validity status is not shown for OSLC links between model elements and artifacts in other applications.

Related information
Work Item 68818

Rhapsody Model Manager can only reference model data on a single server

First occurrence
6.0.5

Problem
You cannot have elements from different servers in the same model, either by reference or as external units.

Related information
Work Item 59546

Rhapsody Model Manager components cannot be owned by specific users

First occurrence
6.0.5

Problem
Any of these three roles can own a Rational Team Concert component:

• Project area
• Team area
• User

In contrast, Rhapsody Model Manager supports only the first two roles, project or team areas. Specific users cannot own a component.

Related information
Work Item 61188

Java 8 SR5 Fix Pack 5 through Fix Pack 10 is not supported as the runtime for CE/CLM applications on a Windows platform

First occurrence
6.0.5

Problem
Continuous Engineering (CE) and Collaborative Lifecycle Management (CLM) applications on a Windows platform that run on Java 8 SR5 Fix Pack 5 through Fix Pack 10 encounter null pointer exceptions and might not be usable. Use Java 8 SR5 Fix Pack 11 (8.0.5.11) or later as the runtime.

Related information
Work Item 455371
Work Item 452307
APAR IJ04429

Rhapsody Model Manager is not supported in a Rational Rhapsody platform integration with Eclipse

First occurrence
6.0.5

Problem
You cannot use the Rational Rhapsody platform integration with Eclipse as a client for the Rhapsody Model Manager server.

You must use the stand-alone version of Rational Rhapsody that is not integrated with the Eclipse platform.

Related information
Work Item 62591

Rhapsody Model Manager is not supported with Rational Rhapsody in a Citrix environment

First occurrence
6.0.5

Problem
You cannot use Rhapsody Model Manager if Rational Rhapsody is running in a Citrix environment.

Related information
Work Item 69168

Rhapsody Model Manager is not supported with Rational Rhapsody client on a Linux operating system

First occurrence
6.0.5

Problem
You cannot use Rational Rhapsody on a Linux operating system as a client for the Rhapsody Model Manager server.

You must use Rational Rhapsody on a Windows operating system as a client for the Rhapsody Model Manager server.

Related information
Work Item 61483

Rhapsody Model Manager shows dates in UTC

First occurrence
6.0.5

Problem
Rhapsody Model Manager shows all dates in Coordinated Universal Time (UTC) and not in local times.

Related information
Work Item 69090

Some Rational Team Concert options must be turned off when you use Rhapsody Model Manager

First occurrence
6.0.5

Problem
When you use Rhapsody Model Manager, you must turn off the following source control options in your Rational Team Concert client:

• Auto-check-in local changes: To locate this option, click Window > Preferences > Team > Java Source Control > Check-in Policies.
• Allow modeling tools (e.g. UML) to participate in file content merging during Accept: To locate this option, click Window > Preferences > Team > Java Source Control > Model Enablement.