Download 6.0.6 Release
June 15, 2018
June 15, 2018
IBM Rhapsody Model Manager
Analysis · Design change management · Lifecycle traceability
Rhapsody Model Manager 184.108.40.206 M2 Milestone
Early Access Milestone | November 20, 2018
This is not the recommended version. We recommend Rhapsody Model Manager 220.127.116.11 RC3. This is made available for archival purposes and may contain bugs and/or security vulnerabilities. If you do download this version, it is being provided AS IS, without warranties of any kind, including the implied warranties of merchantability and fitness for a particular purpose. We strongly advise you review the support pages for this version and update the product or take actions recommended therein. Security bulletins contain instructions for the security vulnerability addressed therein, and may require upgrading to a newer version. Link to security vulnerability blog: IBM PSIRT blog.
Upgrade and migration details for Rhapsody Model Manager 18.104.22.168 M2
UpgradeThe upgrade from Rhapsody Model Manager 6.0.6 to 22.214.171.124 M2 is not supported in this milestone.
If you are upgrading from a version other than 6.0.6, or will now use WebSphere Liberty or a version of Java that was built after April 2017, after you upgrade your server to 6.0.6 you must obtain updated licenses from the IBM Rational License Key Center to replace your current licenses. If you previously used floating, token, or authorized user single install licenses, install their updated versions. Your existing user license assignments are kept during the installation of the updated licenses. For details, see the instructions in the following release note, which also apply to 6.0.6: Licensing errors might occur if you upgrade the Java environment or upgrade applications to 6.0.5
MigrationStarting in 6.0.6, you can migrate Rational Rhapsody models and OSLC links from Design Management to Rhapsody Model Manager.
When you migrate the model, you can choose whether or not to import the included OSLC links. If you decide not to import the OSLC links, you can import them into the new model at a later time.
You can also import only the OSLC links, without the model. Use this method for externally managed projects.