Workarounds and Limitations: Known issues in IBM Engineering Systems Design Rhapsody – Model Manager 7.0.2

The following known problems are related to this release.

Workarounds

The following problems in this release have workarounds:

Limitations

The following problems in this release do not currently have workarounds:


Workarounds

Tables and matrix views in RMM do not display out-of-sync indications

 

First occurrence

7.0

 

Problem

Unlike diagram views, table and matrix views in RMM do not include out-of-sync indications.

 

Workaround

To ensure that the information displayed accurately represents the current model data, follow the instructions in this document.

 

Related information

[RMM] Tables and Matrices in Web: Show Out-of-Sync marks (72595)

Back to top


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 ELM servers and the Engineering Workflow Management 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 Engineering Workflow Management Client for Eclipse maintains a local full-text search index for the Team Artifact History view. When you upgrade the Engineering Workflow Management 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 ELM 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.

 

Related information

Work Item 467449

 

Back to top


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

 

First occurrence

6.0.6

 

Problem

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

Back to top


The Associate Change Request action in 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 Rhapsody client, you must already have defined a Change and Configuration Management (CCM) repository connection in the Engineering Workflow Management 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 Engineering Workflow Management Eclipse client to the server that manages the work items:

 

1. Open the Engineering Workflow Management Eclipse client.

2. Create a new Jazz Repository Connection.

3. Specify the URI path to https://<;server>:<port>/ccm/

 

Related information

Work Item 64639

Back to top


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 License Key Center (formerly known as 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 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 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 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 License Key Center
Interactive Upgrade Guide
Oracle release note: Restrict JARs signed with weak algorithms and keys

Back to top


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

Back to top


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 EWM sandbox folder to avoid reaching 256 characters.

 

Related information

Work Item 62000

Back to top


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

 

First occurrence

6.0.5

 

Problem

When you create an OSLC link from DOORS Next or 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 DOORS Next or 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 DOORS Next 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

Back to top


Limitations

In Offline mode in Rhapsody, you cannot delete, rename, or move saved units

 

First occurrence

7.0

 

Problem

While you can make changes to a model and save the changes in Offline mode in Rhapsody, you cannot delete, rename, or move saved units.

 

Related information

Offline mode (Phase 2): Allow CM operations and less restrictions in Offline mode (72177)

Back to top


Tags defined for a tag and stereotypes applied to a tag are not displayed on the Properties page of the tag in RMM

 

First occurrence

7.0

 

Problem

While stereotypes applied to an element and tags of an element are displayed on the Properties page of the element in RMM, tags defined for a tag and stereotypes applied to a tag are not displayed on the Properties page of the tag.

 

Related information

[RMM] Add more modeling information to Reportable REST APIs (stereotypes, tags, dependencies) [7.0] (69001)

Back to top


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

Back to top


Rhapsody Model Manager does not integrate with Rhapsody Gateway

 

First occurrence

6.0.5

 

Problem

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

 

Related information

Work Item 69166

Back to top


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

Back to top


Rhapsody Model Manager components cannot be owned by specific users

 

First occurrence

6.0.5

 

Problem

Any of these three roles can own an Engineering Workflow Management 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

Back to top


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

 

First occurrence

6.0.5

 

Problem

Continuous Engineering (CE) and Engineering Lifecycle Management (ELM) 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

Back to top


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

 

First occurrence

6.0.5

 

Problem

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

 

Related information

Work Item 68818

Back to top


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

 

First occurrence

6.0.5

 

Problem

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

 

Related information

Work Item 69168

Back to top


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

 

First occurrence

6.0.5

 

Problem

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

 

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

 

Related information

Work Item 61483

Back to top


RMM does not support export and import of EWM source-control management components

 

First occurrence

6.0.5

 

Problem

For RMM projects, you cannot use the repository tool commands provided by EWM for exporting and importing components.

Back to top


Some Engineering Workflow Management (EWM) 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 Engineering Workflow Management 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.

Back to top


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

 

First occurrence

6.0.5

 

Problem

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

 

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

 

Related information

Work Item 62591

Back to top


Feedback
Was this information helpful? Yes No 0 people rated this as helpful.