Our frameworks for UML code generation from IBM Rhapsody are developed in a way that they can be adapted easily to different RTOSes or targets and there is a huge list of supported environments. But there is a big difference between our version 6 frameworks and our version 7 generic framework.
Version 7: For our generic C++ framework there is just one download “containing it all” and allowing all combinations that make sense. That’s why we call it generic. Continue reading
On 2020-03-20 IBM has released Rhapsody 9.0. To be precise, it’s full name is not IBM Rational Rhapsody anymore, but “IBM Engineering Systems Design Rhapsody 9.0”. (Download-Link for Rhapsody 9.0: x86/x64)
It has introduced some changes for the Windows 10 AppLocker compliance that make Willert RXF V6 Setups incompatible with it. In detail: The “Share” folder has been split up into “UserShare” which resides in the Rhapsody data folder and “Share” which is now in the (usually read-only) Rhapsody program files folder. You will find property files like SiteC++.prp in the “UserShare” folder now, while e.g. profiles and settings delivered with Rhapsody are in the Share folder.
What you need to do to use the RXF with Rhapsody 9.0 depends on the RXF you have or want to install:
The property RXF_Rpy_CPP::Configuration::WST_TMR_PROTECTION contains a typo that will lead to a generated define that is not matching the #ifdef tests for timeout protection.
It is:
WST_TMR_USE_CRITICAL_SECION
It should be:
WST_TMR_USE_CRITICAL_SECTION
This is only a problem, when RXF_Rpy_CPP::Configuration::WST_TMR_PROTECTION is set to WST_TMR_USE_CRITICAL_SECION. It is not a problem, it is is set to WST_TMR_USE_MUTEX.
In the Cert framework (RXF_Rpy_CPP_OORTX_Cert), in C frameworks and in V6 releases this problem does not exist.
The problem can be fixed by editing the file “<RXF_Rpy_CPP folder>\RXF\Config\Profiles\RXF_Rpy_CPP_Profile.prp”. In that file search for “WST_TMR_USE_CRITICAL_SECION” and replace the one occurrence by “WST_TMR_USE_CRITICAL_SECTION”.
An official release V7.11 that will fix this problem is planned and will be published soon.
On December 4, 2017 IBM released Rhapsody 8.3. This release contains a lot of fixes and some changes. It is good to take a look at these changes to see what impact they have on your development environment.
Major changes in Rhapsody’s repository data, see next section, unfortunately introduced some problems that will be fixed again with the iFix 2 for Rhapsody 8.3 (32-bit).
Please take care when upgrading to Rhapsody 8.3 to directly also install iFix2.
Hi!
IBM has released the first iFix for the fresh Rhapsody 8.3. This is a good moment to give an overview of the available iFixes and versions.
IBM released a new version of Rhapsody: 8.3
It is available for support customers of Willert Software Tools in the download area, but all guests can read the Release notes there.
Willert Software Tools will, in the next days, check if this release can be used by RXF customers.
One of the changes is the change from the old rhapsody file format to the new XML format.
IBM released a new version of Rhapsody: 8.2.1.
It is available for support customers of Willert Software Tools in the download area, but all guests can read the Release notes there.
Willert Software Tools will, in the next days, check if this release can be used by RXF customers.
Sometimes Rhapsody is not working as it should. Many “problems” can be solved by installing Rhapsody in the right way and by using it the right way.
Here are some quick solutions that might help improving your Rhapsody Experience:
Since a few versions, IBM creates Fixes for actual versions of Rhapsody.
Customers with a valid support contract can download them from this site.
There are several fixes, for 8.2, 8.1.5 and 8.1.4
Fixes are only available on this site for the 32-bit version
Fixes and downloads for 64-bits or for Linux are available on request (support@willert.de)
A new Rhapsody version was released by IBM last week. We have tested this version with our RXF Frameworks and we have not found a show stopping problem using it.
That means that RXF versions that are compatible with Rhapsody 8.1.5 are also compatible with Rhapsody 8.2.
For earlier than 8.1.5 versions of the RXF please read the 8.1.5 support announcement.
Remember to re-install the RXF for the new Rhapsody version.