Jazz Library Workarounds and Limitations: Known issues in IBM Engineering Systems Design Rhapsody – Model Manager 7.0.3
Author name

rhapsody-model-manager

Thu, 05 Oct 2023
5 min read
0

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

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

When upgrading to RMM 7.0.3, rebuild the full-text search indexes to search for architecture elements


First occurrence
7.0.3

Problem
In RMM 7.0.3, the user is allowed to search for architecture elements in the OSLC link creation dialog and the quick search menu. If you are upgrading to RMM 7.0.3, the full-text search indexes must be rebuilt so that the search results include the architecture elements that were created before RMM 7.0.3.


Workaround

To rebuild the full-text search indexes after upgrading to RMM 7.0.3, run the repotools-ccm -rebuildTextIndices command before starting the server. The reindexing might be a lengthy process and can take many hours for a large database. If an application is clustered, the reindexing procedure (using repotools) must be performed on each node in the cluster. For more information, see Searching for model elements. 

Back to top

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
Work Item 63674
Work Item 63895

Back to top

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

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 the 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

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

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

Simplified linking from RMM to DOORS Next is not supported when the RMM project area is configured with an SCM Deliver precondition that requires all change sets to be associated with a work item


First occurrence
7.0.3

Problem
Simplified linking (drag and drop or copy and paste) from RMM to DOORS Next is not supported when the RMM Project Area is configured with an SCM Deliver precondition that requires all change sets to be associated with a work item.

Workaround
If this precondition is set, use simplified linking (drag and drop or copy and paste) from DOORS Next to RMM, or use the legacy actions of creating the OSLC link from within RMM. In these workarounds, the ‘Create Link’ dialog offers the ability to select a work item which is required if the RMM Project Area is configured with an SCM Deliver precondition that requires all change sets to be associated with a work item.

Back to top

Limitations

 

Role-based permissions cannot be used to customize who can update ‘Link validity’ status from within RMM


First occurrence
6.0.6.1

Problem
The ability to update link validity status from within RMM does not use role-based permissions. All users that have access to the architecture element and OSLC link in the RMM web UI can update the link validity status.

Related information
Work Item 80179

Back to top

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

When generating reports for RMM in Report Builder


First occurrence
7.0.3

Problem

  • Link validity data that is entered for RMM OSLC links before 7.0.3 will not be available for reporting in Report Builder. Data that is entered or modified in 7.0.3 will be available.
  • The reports in the Report Builder will not include results containing RMM Architecture Elements that are in a component that is owned by a user or the Team Area that has ‘Team Private’ visibility.
  • When generating reports in Report Builder for architecture elements from a project area that is not enabled for configuration management, ensure that all components in the ‘Default OSLC Context’ belong to the same project area. This means a component from one project area that is not enabled for configuration management must not be used in another project area. This restriction ensures that each architecture element in the project area that is not enabled for configuration management has only a single version in the report.
  • “External links” that is, non-OSLC links or links to arbitrary URLs on Architecture Elements are not available for reporting in Report Builder.
  • Use the “Name” or “Label” attribute in Report Builder to extract the Name or Label information instead of the ‘Title’ attribute.

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

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

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 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 the 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

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

© Copyright IBM Corporation 2023

Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.

Thu, 05 Oct 2023