Workarounds: General Problems in Design Management 4.0.4
The following known problems are related to general problems in Design Management 4.0.4.
Workarounds
The following problems in this release have workarounds:
- When an impact analysis artifact has multiple types, you cannot filter out one of the types by setting it as an active filter in the diagram. (4.0.3 workaround article)
- Links to resources that are have an Arabic or Hebrew name may result in dangling references during import. (4.0.1 workaround article)
- In the Design Management web client, clicking on references to visualized elements does not return relevant information. (4.0.1 workaround article)
- The import process creates duplicate models in a child workspace. (4.0.1 workaround article)
- If running under load on a multiprocessor or multicore system that is running Windows Server 2008 R2 (including SP1), the Jazz Team Server or Design Management application might stop responding and show this error in the server or application log: No buffer space available (maximum connections reached?). (4.0.3 workaround article)
- When you change the access controls for a project area in the Configuration Management application from the default permissions to more restricted role-based permissions, you must add the functional user (dm_user) to this project area and give them specific privileges to avoid data loss in the unexpected event of a Design Management server crash. (4.0.3 workaround article)
- If you edit a Rational Rhapsody model in the Design Management actively managed mode, you cannot add a resource in a dependent project area by using the Add to Model action. (4.0.3 limitation article)
- In Rational Rhapsody Design Manager, the Architect role does not have permission to delete links. (4.0.1 workaround article)
- Rational Software Architect models version 8.0 and later with version 1.0 of the MSL Deployment profile cannot be uploaded to Design Management Server 4.0.3 (4.0.3 workaround article).
- You cannot create a UML model for Integrated Architecture (UPIA), RealTime (RT), or Service-Oriented Architecture (SOA) models when a project area is associated with the correct corresponding domains. (4.0 workaround article)
- You cannot install the Rational Software Architect Extension for Design Management into an existing Rational Software Architect installation. (4.0.1 workaround article)
- If an alias URI was used to configure a Collaborative Lifecycle Management (CLM) server as a friend of the Design Management Server, you might have to log in twice to the Rational Software Architect Design Manager Client Extension to access that server. (4.0 workaround article)
- You might not be able to create or delete links to artifacts in Rational DOORS by using the Rational Software Architect Extension for Design Management. (4.0.1 workaround article)
- You cannot import topologies and deployment artifacts that are stored in the Design Management repository into other topologies. (4.0 workaround article)
- Transformations that target UML Models located on a Design Management server will fail to execute. (4.0.1 workaround article)
Limitations
The following problems in this release do not currently have workarounds:
- After you import a Rational Software Architect model onto the Design Management Server, any custom or stock images associated to a sketch shape in Rational Software Architect will not display when the diagram is viewed using the Web UI.
- Rational Software Architect Extension for Design Management can extend various versions of the Rational Software Architect product.
- Exceptions occur when you use the web client to explore Deployment Planning and Automation models that contain capabilities that are introduced in Rational Software Architect 9.0. (4.0.3 workaround article)
- BPMN models that were created in and that use elements introduced in Rational Software Architect 9.0 cannot be imported into Design Management Server 4.0.3 or earlier. (4.0.3 workaround article)
Limitation summary
Problem
Using Rational Software Architect, you can assign an image to a sketch shape that modifies default appearance of the shape on free-form or sketch diagrams. You can use either the predefined set of images available in the Rational Software Architect, or use custom images of your own. However, after you import a Rational Software Architect model onto the Design Management Server, any custom or stock images associated to a sketch shape in Rational Software Architect will not display when the diagram is viewed using the Web UI.
Related information
Limitation summary
Problem
Rational Software Architect Extension for Design Management allows you to connect to and work with project areas available on the Design Management Server that have a dependency on a snapshot of the System Domains project. The System Domains project contains predefined Rational Software Architect resources such as ontologies, profiles, libraries and so on. Each snapshot of this project corresponds to a corresponding version of a Rational Software Architect product:
- snapshot "0.1" was introduced in Design Manager 4.0 and corresponds to Rational Software Architect 8.5.0;
- snapshot "0.2" was introduced in Design Manager 4.0.1 and corresponds to Rational Software Architect 8.5.1;
- snapshot "0.3" was introduced in Design Manager 4.0.2 and corresponds to Rational Software Architect 8.5.1;
- snapshot "0.4" was introduced in Design Manager 4.0.3 and corresponds to Rational Software Architect 9.0.
Note: there are no differences between snapshots "0.2" and "0.3" from a Rational Software Architect Extension for Design Management point of view; however, those differences have an impact on the Design Manager Web Client.
There are three main domains for Rational Software Architect Design Manager that should be taken into account while describing compatibility between Rational Software Architect Extension for Design Management and the snapshots mentioned above:
- UML Domain
- BPMN Domain
- Deployment (Topology) Domain
Recommended combinations for the UML Domain
- Rational Software Architect Extension for Design Management 8.0.4.2 should connect to project areas that have the "0.1" snapshot in the project dependencies list.
- Rational Software Architect Extension for Design Management 8.5 should connect to project areas that have the "0.1" snapshot in the project dependencies list.
- Rational Software Architect Extension for Design Management 8.5.1 should connect to project areas that have the "0.3" snapshot in the project dependencies list.
- Rational Software Architect Extension for Design Management 9.0 should connect to project areas that have the "0.4" snapshot in the project dependencies list.
Known limitations with UML models
- Rational Software Architect 8.0.4.2, 8.5, 8.5.1 and 9.0 UML models are compatible with either the 0.1 or 0.2 snapshot of the System Domains project area. There are no known limitations with any of the combinations (no model corruption or data loss). However, you should follow the combinations mentioned above.
Recommended combinations for the BPMN Domain
- Rational Software Architect Extension for Design Management 8.0.4.2 should connect to project areas that have the "0.1" snapshot in the project dependencies list.
- Rational Software Architect Extension for Design Management 8.5 should connect to project areas that have the "0.1" snapshot in the project dependencies list.
- Rational Software Architect Extension for Design Management 8.5.1 should connect to project areas that have the "0.3" snapshot in the project dependencies list.
- Rational Software Architect Extension for Design Management 9.0 should connect to project areas that have the "0.4" snapshot in the project dependencies list.
Known limitations with BPMN models.
- Rational Software Architect Extension for Design Management 8.0.4.2 can only work in read-only mode to view Business Process Modeling Notation (BPMN) models.
- Rational Software Architect Extension for Design Management 8.5 is partially compatible with the 0.3 snapshot of the RSA System Domains project area.
- Rational Software Architect Extension for Design Management 8.5.1 is partially compatible with the 0.1 snapshot of the RSA System Domains project area. There will be data loss if the user uses the "parallel multi-instance markers/multi-instance activities" feature introduced in Rational Software Architect 8.5.1.
- Rational Software Architect Extension for Design Management 9.0 does not support new model elements introduced in Rational Software Architect 9.0, namely "Complex Gateway" and "Event-Based Gateway" model elements. For more information, see work item 38823.
Recommended combinations for the Deployment (Topology) Domain
- Rational Software Architect Extension for Design Management 8.5 should connect to project areas that have the "0.1" snapshot in the project dependencies list.
- Rational Software Architect Extension for Design Management 8.5.1 should connect to project areas that have the "0.3" snapshot in the project dependencies list.
- Rational Software Architect Extension for Design Management 9.0 should connect to project areas that have the "0.4" snapshot in the project dependencies list.
Known limitations with Deployment (Topology) models
- Only the above three combinations are supported. Other combinations can cause data loss or model corruption and are not fully supported.
- Rational Software Architect Extension for Design Management 9.0 does not support new concepts introduced in Rational Software Architect 9.0. For more information, see work item 38823.
Related information
Copyright © 2013 IBM Corporation