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

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

Work Item 72595

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.

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

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

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

• 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.

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.

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.

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

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

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

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

Work Item 72177

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

Work Item 69001

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

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

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

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

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

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

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

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

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.

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