Workarounds and Limitations: Known issues in Rhapsody Model Manager 6.0.5

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

Rhapsody Model Manager cannot be registered on a CLM server upgraded to 6.0.5 on WebSphere Application Server Liberty

First occurrence
6.0.5

Problem
After you upgrade to 6.0.5, you must register Rhapsody Model Manager because it’s a new application that did not exist before 6.0.5. However, when you try to register, you get the following error:

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. ID CRJAZ2081E

The working copy of 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 representing the Architecture Management (AM) application. You get this error because this configuration file was copied from the older version of the server, which is not aware of the new Rhapsody Model Manager application.

Workaround
After the upgrade to 6.0.5 and before registering the Rhapsody Model Manager application, follow 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: If, during the installation, the default root context of the RMM application was changed, make the corresponding changes to the <application …> tag entry:

    a) ID field

    b) Name field

    c) Name of the WAR file

5. Save the changes.

6. Start the server.

7. Register and configure the Rhapsody Model Manager application in the usual way.

Related information
Work Item 62574

Rhapsody Model Manager cannot create a lifecycle project

First occurrence
6.0.5

Problem
Steps to recreate the problem:

1. Rhapsody Model Manager is installed. You want to create an Architecture Management (AM) template.
2. Create a lifecycle project, and select the Quality Professional, Analyst, Developer – with Design Management template.
3. The lifecycle project administration (LPA) project area is not created, and you get this error message:
Error instantiating the template: com.ibm.team.repository.common.TeamRepositoryException: CRJCA0003E The Lifecycle Project Administration (LPA) application made a request that was answered by an unexpected response code. The request was: <server>/am/process/project-areas. The response was: HTTP/1.1 400 Bad Request.

Workaround
Create a lifecycle project without Rhapsody Model Manager, and add a manually created AM project.

These are the steps:
1. Create a new Architecture Management project area.
2. Create a lifecycle project using the Quality Professional, Analyst, Developer template.
3. Click Add in the Additional Artifact Containers section.
4. In the Application field, select Design Management (/am).
5. In the Artifact Container field, select the Architecture Management project area you created.
6. Click Add Artifact Container.
7. Manually add the required project area associations.

Related information
Work Item 61069

Rhapsody controlled files are not automatically included in change sets created when you save

First occurrence
6.0.5

Problem
If your Rhapsody model includes controlled files and you make changes to those controlled files, the automatically created change set doesn’t include the modified controlled files.

Workaround
Manually include the controlled files by grabbing and dropping them from the Unresolve section of the change set in the Rational Team Concert Eclipse client.

Related information
Work Item 61145

The Create Streams and Replace actions for global configurations do not work for Rhapsody Model Manager streams

First occurrence
6.0.5

Problem
If you include a Rhapsody Model Manager stream in a global configuration and you run the Create Streams or Replace operation from the Rhapsody Model Manager stream, you might get the following error message:
You cannot use this configuration to replace the original one because they are not configurations of the same component.

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

When you use a trial license, you might get an errorr that the Rational Team Concert – Developer license is not assigned

First occurrence
6.0.5

Problem
If you are using a trial license, and you use the Associate Change Request command in the Rational Team Concert Client for Eclipse IDE to associate a Rhapsody Model Manager change set with a Rational Team Concert change request, you might get an error in the Team Advisor view that the Save Change Set Links and Change Request operation cannot be performed because the Rational Team Concert – Developer license is not assigned.

This error occurs because, in a trial, you need the Rational Team Concert – Developer license to perform that operation.

Workaround
Use one of the following workarounds:

• During the evaluation period, assign both the Rational Team Concert – Developer and the Rational Rhapsody Design Manager – Design Manager trial licenses to a user.
• Install non-trial license keys from the License Key Center.

Related information
Work Item 62212

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

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

A Rhapsody Design Manager license is required to create links from Rational DOORS Next Generation or Rational DOORS

First occurrence
6.0.5

Problem
To create OSLC links between requirements and models, you must have a Design Management license with client access to Rational DOORS Next Generation or Rational DOORS.

Related information
Work Item 61895

Java 7.1 SR4 FP10 is not supported

First occurrence
6.0.5

Problem
Collaborative Lifecycle Management (CLM) applications that run on WebSphere Application Server Liberty (16.0.0.4 and 17.0.0.2) and that are configured with JRE 7.1 SR4 FP10 might crash. By default, versions 6.0.5 and later include a Java version that is stable.

Related information
Work Item 439584

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

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

Global Configuration Management cannot detect multiple configurations of the same Rhapsody Model Manager component (component skew)

First occurrence
6.0.5

Problem
The Global Configuration Management application can’t detect skew if a global configuration contains different configurations of the same RMM component. In this case, you won’t know if the application is able to find the correct version of the artifacts you need. Any report on skew won’t find skewed configurations of RMM components.

Avoid adding different configurations of the same RMM component to a global configuration. If you’re not sure if the component is there already, or if you’re getting unusual results, check the configuration tree.

Related information
Work Item 61489

Rhapsody Model Manager does not support link validity

First occurrence
6.0.5

Problem
Link validity status is not shown for OSLC links between Rhapsody Model Manager and artifacts in other applications. In other CLM applications, link validity indicates whether the contents of two artifacts meet the intended meaning of the link between the artfacts.

Related information
Work Item 59392

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.