Workarounds: Rational Rhapsody problems in Design Management 4.0.1
The table of contents lists the known problems and workarounds related to the Rational Rhapsody client extension functionality in the Design Management 4.0.1 release.
- You might have to restart the Rational Rhapsody Design Management client extension to make OSLC-RM Integration work
- The Model Browser view of the Rational Rhapsody Design Management client extension does not show new terms in profiles until the model is expanded or loaded in that view
- Rational Rhapsody client extension does not retain login credentials.
- OSLC RM Integration is not supported on Linux.
- The Metrics view of Rational Rhapsody queries is not shown in the Rational Rhapsody Design Manager web interface.
- OSLC DOORS integration does not support connections to a DOORS server using HTTP protocol
Problem Summary
You might have to restart the Rational Rhapsody Design Management client extension to make OSLC-RM Integration work.
You can use the Rational Rhapsody Design Management client extension to view and edit comments and links from the Design Management Server for models in Published Mode. In published mode, models are managed by an external configuration management tool and published by the import engine in the Design Management Server. In managed mode, the models are managed by and loaded from the Design Management Server.
To use the OSLC-RM Integration feature in published mode, open the Collaboration view and specify a Rational Rhapsody Design Management server address; then select a project area and a stream.
To enable the published mode for the current model, open the Links view when you are connected to the Design Management Server.
Problem
After you configure OSLC-RM Integration, it might fail the first time that you use it.
Workaround
Close and reopen the Rational Rhapsody Design Management client extension.
Problem Summary
The Model Browser view of the Rational Rhapsody Design Management client extension does not show new terms in profiles until the model is expanded or loaded in that view.
Problem
The Rational Rhapsody Design Management client extension loads a model that is stored on the Design Management Server based on the domains that the model uses. In specific scenarios, if a model references a profile, you can upload the model to the Design Management Server without creating a domain for the model. If you do not create a domain, the Rational Rhapsody Design Management client extension recognizes the new term type of the element only after the element is loaded.
The client loads models on demand, which means that the resources are loaded only as you expand or open them in the Model Browser view. As a result, the Model Browser view shows elements as native Rhapsody model elements, such as a class. When you expand an element in this view, the element is loaded and converted to its type based on its profile-based type, such as a SysML::Block.
Workaround
Complete the following steps:
- Before moving the model to the Design Management Server, create a domain for the profile.
- In the Model Browser view, expand the resource to resolve to its actual type.
- Start an operation that loads the entire project, such as Search (Ctrl+F).
Problem Summary
Rational Rhapsody client extension does not retain login credentials.
Problem
Rational Rhapsody client extension does not retain the login credentials you provide after you open a model from design manager and then attempt to access a Design Manager View.
Workaround
To open a Design Manager view, provide your login credentials a second time when prompted.
Known Limitation
OSLC RM Integration is not supported with the Rational Rhapsody Design Manager client extension on Linux.
Known Limitation
The Metrics view of Rational Rhapsody queries is not shown in the Rational Rhapsody Design Manager web interface.
Problem
Model data generated through queries and shown using a metrics layout in Rational Rhapsody is not available when the model is viewed in the Rational Rhapsody Design Manager web interface.
Problem Summary
OSLC DOORS integration does not support connections to a DOORS server using HTTP protocol.
Workaround
You must connect to a DOORS server using HTTPS protocol.
Copyright © 2012 IBM Corporation