Known issues
The following issues and limitations are known for Rhapsody® Model Manager 7.1 release.
Workaround
- Simplified linking from Rhapsody Model Manager to DOORS Next is not supported when the Rhapsody Model Manager project area is configured with a Source Control Management (SCM) deliver precondition that requires all change sets to be associated with a work item
-
First occurrence: 7.0.3
Internal ID: 80389
Problem: Simplified linking (drag or copy and paste) from Rhapsody Model Manager to DOORS Next is not supported when the Rhapsody Model Manager 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 or copy and paste) from DOORS Next to Rhapsody Model Manager, or use the legacy actions of creating the OSLC link from within Rhapsody Model Manager. In these workarounds, the Create Link dialog offers the ability to select a work item, which is required if the Rhapsody Model Manager Project Area is configured with an SCM Deliver precondition that requires all change sets to be associated with a work item.
- The Rhapsody Model Manager server and client require a locale setting for non-English-language support
-
First occurrence: 6.0.6
Internal ID: 63897
Problem: Rhapsody elements for non-English-language labels display incorrectly in the Rhapsody Model Manager web interface, unless the correct locale is set on the client computer.
Workaround: Manually set the locale on the client computer.
- When you are upgrading to Rhapsody Model Manager 7.0.3 or Rhapsody Model Manager 7.1 from Rhapsody Model Manager 7.0.2 or earlier, rebuild the full-text search indexes to support searching for architecture elements
-
First occurrence: 7.0.3
Internal ID: 80459
Problem: In Rhapsody Model Manager 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 Rhapsody Model Manager 7.0.3 or RMM 7.1 from Rhapsody Model Manager 7.0.2 or earlier, the full-text search indexes must be rebuilt so that the search results include the architecture elements that were created before Rhapsody Model Manager 7.0.3.
Workaround: To rebuild the full-text search indexes after upgrading to Rhapsody Model Manager 7.0.3 or Rhapsody Model Manager 7.1 (if upgrading from Rhapsody Model Manager 7.0.2 or earlier), 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 (by using repotools) must be performed on each node in the cluster. For more information, see Searching for model elements
- Tables and matrix views in Rhapsody Model Manager do not display out-of-sync indications
-
First occurrence: 7.0
Internal ID: 72564
Problem: Unlike diagram views, table and matrix views in Rhapsody Model Manager do not include out-of-sync indications.
Workaround: To help ensure that the information displayed accurately represents the current model data, follow the instructions in Keeping Rhapsody Model Manager diagram/table/matrix views up-to-date.
- The associate change request action in Rhapsody requires a repository connection
-
First occurrence: 6.0.6
Internal ID: 64640
Problem: If you want to associate a change request with a Rhapsody Model Manager change set that is in the Rhapsody client, make sure that the Change and Configuration Management (CCM) repository connection in the Engineering Workflow Management Eclipse client is already defined. Otherwise, you get the following error:
Error while associating a work item to a 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 that is 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:- Open the Engineering Workflow Management Eclipse client.
- Create a Jazz Repository connection.
-
Specify the URI path to https://<;server>:<port>/ccm/
- The create streams action for global configurations does not work for Rhapsody Model Manager snapshots
-
First occurrence: 6.0.5
Internal ID: 64658
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.
- The file path for the Rhapsody client on Microsoft Windows is limited to 256 characters
-
First occurrence: 6.0.5
Internal ID: 62565
Problem: It's not possible to open and save a Rhapsody model to a path that is longer than 256 characters.
Workaround: Use a short path to the EWM sandbox folder to avoid reaching 256 characters.
- You cannot associate a change request when you delete an OSLC link from DOORS Next or DOORS
-
First occurrence: 6.0.5
Internal ID: 62581
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. This happens because these applications do not provide a dialog box where you can select a change request. If the required work items and comments precondition are selected on the server side for a project area, deleting the link fails with an error message.
Workaround: This workaround is available starting in 6.0.5 interim fix 001:-
From DOORS Next go to Rhapsody Model Manager by clicking the OSLC link that you want to delete.
-
In Rhapsody Model Manager, delete the existing OSLC link, and then you can select a change request to associate with the change set.
-
Limitations
- In Rhapsody, you cannot delete, rename, or move saved units in the offline mode
-
First occurrence: 7.0
Internal ID: 72593
Problem: While you can change a model and save the changes in dffline mode in Rhapsody, you cannot delete, rename, or move saved units.
- The following limitations exist when you are generating reports for Rhapsody Model Manager in Report Builder
-
First occurrence: 7.0.3
Internal ID: 80387
Problems:- Link validity data that is entered for Rhapsody Model Manager OSLC links before 7.1 is not available for reporting in Report Builder. Data that is entered or modified in 7.1 is available. A defect exists in which link validity data involving Rhapsody Model Manager model elements might show duplicate results in a Jazz Reporting Service (JRS) report. This can happen if subsequent link validity changes are made from within IBM DOORS Next or Engineering Test Management. For example, when using link validity, the validity status is set to suspect initially, if you change link validity for the first time from any tool, JRS reports show the correct results (that is, either suspect if not changed, or Valid or Invalid if the validity was set). However, if the link validity status is manually changed by using IBM DOORS Next or Engineering Test Management, Jazz Reporting Service reports might show both the old and new link validity status. The workaround is to use the Rhapsody Model Manager web-UI to make subsequent link validity changes if required.
- The reports in the Report Builder will not include results
that contain Rhapsody Model Manager architecture elements that are in a component that is owned
by a user or a team area that has
Team Private
visibility. - When you are generating reports in Report Builder for
architecture elements from a project area that is not enabled for configuration management, help
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 helps ensure 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 are Non-OSLC links or links to arbitrary URLs on architecture elements are not available for reporting in Report Builder.- Use the
Name
orLabel
attribute in Report Builder to extract the Name or Label information instead of theTitle
attribute. - The description of a model element is not available in reports that are generated in Report Builder. This is because the description itself is not exposed as an attribute in the architecture element shape and thus is not available to LQE and Report Builder.
- Link validity status is displayed only in projects that are enabled for configuration management
-
First occurrence: 6.0.6.1
Internal ID: 70107
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.
- Rhapsody client for Rhapsody Model Manager does not display link validity information
-
First occurrence: 6.0.5
Internal ID: 69865
Problem: In Rhapsody, link validity status is not shown for OSLC links between model elements and artifacts in other applications.
- Rhapsody Model Manager can reference only model data on a single server
-
First occurrence: 6.0.5
Internal ID: 62563
Problem: You cannot have elements from different servers in the same model, either by reference or as external units.Note: Rhapsody Model Manager 7.1 introduced the ability to support AM-AM OSLC linking. Thus, it is possible as of Rhapsody Model Manager 7.1 to create an OSLC link (of type Tracks, Allocates, or Realizes) between two Rhapsody Model Manager model elements in different Rhapsody Model Manager servers. While this is different than having models elements from different servers in the same model, these new OSLC links provide a potential workaround to provide a link or relationship between any two model elements. - Specific users cannot own Rhapsody Model Manager components
-
First occurrence: 6.0.5
Internal ID: 62556
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.
-
- Rhapsody Model Manager does not integrate with Rhapsody Gateway
-
First occurrence: 6.0.5
Internal ID: 69165
Problem: You cannot use Rhapsody Gateway for models that are stored on the Rhapsody Model Manager server. To manage traceability for requirements, use the Remote Artifacts OSLC integration with DOORS.
- Rhapsody Model Manager is not supported in a Rhapsody platform integration with Eclipse
-
First occurrence: 6.0.5
Internal ID: 62561
Problem: You cannot use the Rhapsody platform integration with Eclipse as a client for the Rhapsody Model Manager server. Use the stand-alone version of Rhapsody that is not integrated with the Eclipse platform.
- Rhapsody does not support Rhapsody Model Manager in a Citrix environment
-
First occurrence: 6.0.5
Internal ID: 69167
Problem: You cannot use Rhapsody Model Manager if Rhapsody is running in a Citrix environment.
- Rhapsody client does not support Rhapsody Model Manager on a Linux® operating system
-
First occurrence: 6.0.5
Internal ID: 62558
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 Microsoft Windows operating system as a client for the Rhapsody Model Manager server.
- Rhapsody Model Manager does not support export and import of Engineering Workflow Management source-control management components
-
First occurrence: 6.0.5
Internal ID: 73463
Problem: For Rhapsody Model Manager projects, you cannot use the repository tool commands that are provided by EWM for exporting and importing components.
- Role-based permissions cannot be used to customize who can update the 'Link validity' status from within Rhapsody Model Manager
-
First occurrence: 6.0.6.1
Internal ID: 80388
Problem: The ability to update link validity status from within Rhapsody Model Manager does not use role-based permissions. All users that have access to the architecture element and OSLC link in the Rhapsody Model Manager web UI can update the link validity status.
- Some Engineering Workflow Management options must be turned off when you use Rhapsody Model Manager
-
First occurrence: 6.0.5
Internal ID: 61956
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
. -
Allow modeling tools (For example, UML) to participate in merging file content during accept. To locate this option, click
.
-
- Tags that are defined for a tag and stereotypes that are applied to a tag are not displayed on the Properties page of the tag in Rhapsody Model Manager
-
First occurrence: 7.0
Internal ID: 72592
Problem: While stereotypes applied to an element and tags of an element are displayed on the Properties page of the element in Rhapsody Model Manager, tags defined for a tag and stereotypes applied to a tag are not displayed on the Properties page of the tag.