I’m not a fan of updates. A few years ago I always switched off my automatic updates. On a Mac that was possible and would hardly have other consequences.
Unfortunately, this is not the case anymore. Modern development methods like DevOps, Agile, Continuous Engineering and I_don’t_know_how_it_is_called are forcing you to keep your system up-to-date. Either Apps don’t work with the latest OS or an App requires a certain minimum version of the OS.
Many systems do not even allow you to wait with updates, even my beloved Mac starts whining and will update without asking.
Walter Quote #2: If it aint broke: Don’t fix it!
The same applies to Rhapsody. Newer versions will have improvements, bug fixes and sometimes new options or features. Since 8.1.3, IBM will at least deliver so-called iFixes that enclose bug fixes for the most serious bugs. (Check our download portal or the IBM website to download the iFix for you Rhapsody version. You only need to install the highest number, it will contain all previous iFixes for that version.
Here is a list with all versions (and Build numbers) since 8.0.
5 june 2017
|Rhapsody Version||Build Number||Release date|
|24 june 2018|
|4 dec 2017|
|1 dec 2016|
|25 april 2016|
|14 dec 2015|
|26 june 2015|
|20 feb 2015|
|5 dec 2014|
|5 sep 2014|
|2 jun 2014|
|28 feb 2014|
|5 dec 2013|
|3 sep 2013|
|14 jun 2013|
|21 mar 2013|
|27 nov 2012|
|8 nov 2012|
|21 sep 2012|
De-install the old one?
You don’t have to. You can install multiple versions of Rhapsody in parallel. A few things to consider:
- Install in the same way as the previous version (Same directory structure)
- The last installed version is the default version that will start when you double-click a .rpy file.
You don’t have to do anything to update your models. But…. As soon as you save a model it is updated and cannot be opened with older versions of Rhapsody anymore. (Not always, sometimes 2 consecutive versions use the same database version.)
You can, however, use “Save As” to save the model in an older version. You can do that 2 versions back. So not too much.
Here is a list with the Rhapsody Versions and how they can be “saved” back.
|Rhapsody Version||„Save As“|
Of course a new version of Rhapsody can have changes in Code Generation. Best is to install a new version, start the old version, generate code, start the new version, load the model, generated code (In a different directory!!) and compare the code. If it is the same, you’re good. If different, first compile, you might still be good. But if it doesn’t work, try to understand the consequences of the changed code.
You will have some “Settings” files in your browser that are named “CGCompatibilityPreX.Y”. These files include the changed properties.
You MUST re-install the RXF and then during install tell the RXF the right directory for the new version of Rhapsody. (It will usually detect it automatically)
You can load the older models if you do not install the RXF but it will not work.
If you use Eclipse you have to either re-install the Eclipse plugin (first de-install the old one and then re-install the new one!)
If you want to use 2 versions then you will have to install Eclipse twice (I have not found any other way to do it…) and install the Eclipse Plugins/Workflow for the newer Rhapsody version in the second Eclipse.
Easy to forget… If you use the ReqXChanger, you have chosen the rhapsody.jar that matches the Rhapsody Version you use to sync your requirements with.
You have to edit the configuration to allow for ReqXChanger to use the new version of Rhapsody!
Happy Upgrading (and modeling) with Rhapsody
Walter van der Heiden (firstname.lastname@example.org)
One thought on “If it ain’t broke, don’t fix it….”