Rhapsody TechBlog

BLOG about IBM Rhapsody. Contains technical information as well as more private travel stories.

10 Jahre MESCONF

April 24, 2025 / / 0 Comments

MESCONF – Modeling Embedded Systems

Worum geht es bei der MESCONF?

Embedded Systeme sind allgegenwärtig; ein Alltag ohne diese intelligenten kleinen Helfer kaum noch vorstellbar. Wie man Embedded Systeme so baut, dass sie zuverlässig das tun, was erwartet wird, das steht bei der MESCONF im Mittelpunkt. Dabei betrachten wir insbesondere, wie Modelle helfen können, Architekturen, Systeme und Software zu entwickeln und zu verfeinern.

Warum solltest Du teilnehmen?

Der oft beschworene “Blick über den Tellerrand” kann
überraschende und wertvolle Anregungen bringen, wie
die eigene Projektarbeit verbessert werden kann.
Deshalb steht der Austausch von praktischen
Erfahrungen in konkreten Anwendungsbeispielen bei der
MESCONF im Vordergrund. Anwender berichten aus
ihren Projekten, und es gibt viel Raum, sich über das
Gehörte, eigene Ideen, Erfahrungen und Erwartungen im
persönlichen Gespräch auszutauschen.

Format der MESCONF

  • Fachvorträge
  • Diskussionsrunden
  • Workshops der Toolhersteller
  • Fishbowl

Warum gibt es die MESCONF?

Ganz einfach: weil Embedded Systeme heute derart komplexe Aufgaben
lösen, oft auch im Verbund, dass die Entwicklung extrem aufwendig
werden kann. Fehler werden spät entdeckt; deren Beseitigung ist
kompliziert und kann zu unerwünschten Seiteneffekten führen, und am
Ende laufen Kosten aus dem Ruder, und Liefertermine werden verpasst.

Visuelle Hilfsmittel wie Bilder sind hilfreich; noch besser sind Modelle!
Weil die Symbole eindeutig sind und nicht falsch interpretiert werden
können. Modelle können in Entwicklungstools bearbeitet werden, was
viele Entwicklungsaufgaben erleichtert.

Inhalte können überprüft werden, Source-Code, Dokumente und andere
Artefakte generiert werden, mit Hilfe von Simulationen können
Unstimmigkeiten frühzeitig aufgedeckt oder ausgeschlossen werden.
Missverständnisse werden minimiert, viele mögliche Fehlerquellen sind a
priori ausgeschaltet.

Was kann Modellierung konkret leisten und was ist dabei zu
berücksichtigen? Das „Modeling Manifest“ (http://mdse-manifest.org)
einer Gruppe von Experten ist ein guter Einstieg. Jedoch: was sich darin
einfach liest und logisch anhört, ist in der Praxis nicht in jedem Projekt
exakt so umsetzbar, und es stellen sich immer wieder neue Fragen.

Und genau deshalb gibt es die MESCONF, fokussiert auf diese Thematik.
Am 22. und 23. Mai 2025 treffen sich Experten und Anwender, um „Best
Practices“ auszutauschen, Ideen und Fragen zu besprechen und neue
Erkenntnisse zu gewinnen.


Rückblick auf die MESCONF 2024


Fachvorträge MESCONF 2024 (Auswahl)

  • Funktionsorientierte Entwicklung mit MBSE und Potentiale für den Einsatz von AI
    Jochen Epple, Mercedes-Benz, Anuschka Gummel, BHC
  • Game Changer SysML v2 und AI
    Tim Weilkiens, oose
  • Guided System Modeling und Übergang in die SW und E/E Domäne
    Johannes Trageser, SodiusWillert
  • SysML v2 in der praktischen Erprobung
    Samir Sarkic, Bosch


Workshops MESCONF 2024

  • Infineon: Model-Based Design (MBD) and Automated Code Generation
  • Mathworks: System Architecture Modeling of an Electric Vehicle with MathWorks Toolchain
  • Incquery: Model Governance für das Digital Engineering der Zukunft: IncQuery Validator Product Launch
  • IBM: Einstieg in die Modellbasierte Entwicklung – Welchen Einfluß hat die neue SysML v2 auf etablierte MBSE Methoden?


Auszug aus den Diskussionsrunden MESCONF 2024

  • AI-Assisted MBSE
  • Model-based requirements engineering
  • Text vs. Grafik aus Anwendersicht
  • Reviewing models — review management, results management, results documentation
  • Requirements in the loop — Verifikation von Anforderungen durch Formalisierung
  • Product-line engineering — ab wann sinnvoll, wo anfangen?
  • Impact analysis in models — how to make it work
  • Das Problem mit den UML-Komponenten in IBM Rhapsody


Hier gehts zur Agenda 2024

Ich hoffe viele von euch zu sehen auf der MESCONF!

Walter van der Heiden (walter@sodiuswillert.com)

10 Years of MESCONF 

April 16, 2025 / / 0 Comments

10 Years of MESCONF – Let’s Talk Models, Not B.S.

April 16, 2025 / rhapsody207 / 1 Comment / Edit

🎉 We’re celebrating 10 years of modeling, collaboration, and fresh ideas!

📅 May 22–23, 2025 | 📍 Infineon Campeon, Munich

Let’s cut to the chase: 2025 marks 10 years of MESCONF.

What started as a small prototype has grown into the go-to event for model-based systems engineering (MBSE) pros, tool nerds, process thinkers—and let’s be honest, all of us who just really like making complex stuff actually work.

Whether you’re a Systems Engineer, Architect, Tool Wizard, or just MBSE-curious, MESCONF is where the real conversations happen—with folks who know what they’re talking about, no PowerPoint fluff required.

💬 What’s on the agenda?

Classic expert talks? Yep.

Open discussion formats? You bet.

PowerPoint prison? Nope.

Pre-scripted speakers? Forget it.

The real star? Open Space.

Here’s how it works:

👉 Got a topic? Bring it.

👉 Others care? Talk about it.

👉 No hierarchy, no moderator—just smart people exchanging real-world ideas.

From SysMLv2 to traceability, simulation, tool integration, and yes—AI in modeling—Open Space is where the sparks fly.

🤖 My 2 cents this year:

I’m pitching an Open Space session on AI in modeling.

(And yes, I do say “AI” not “KI”. “KI” sounds like a technique for getting cows pregnant—no offense to the cows. 🐄💉)

On a serious note:

  • Where does AI actually help in MBSE?
  • Where is it just shiny nonsense?
  • How can we integrate smart assistance into our workflows without handing over the model to some black box?

Curious? Opinionated? Just want to argue a bit over coffee? Come join the conversation—I’d love your input.

🛠️ Why bother showing up?

Because modeling is how we wrangle complexity.

Because MBSE doesn’t have to live in an ivory tower.

And because MESCONF is one of the very few places where you’ll find open, honest, practical exchange without corporate smoke and mirrors.

🎟️ Spots are limited – sign up now:

👉 https://mesconf.de

🚀 10 years of MESCONF – let’s write the next chapter together.

See you in Munich!

Keep modeling – with Rhapsody or whatever gets the job done.

Walter van der Heiden

walter@sodiuswillert.com

Happy Modeling ( preferably with Rhapsody)!!

Walter van der Heiden email://walter@sodiuswillert.com

🚀 Implementing DDS in IBM Rhapsody: Real-Time Systems Engineering for the Future

April 10, 2025 / / 0 Comments

As embedded and distributed systems become increasingly complex, ensuring reliable, real-time communication is no longer optional—it’s essential. That’s where the integration of Data Distribution Service (DDS) into IBM Rhapsody changes the game.

At SodiusWillert, we’re enabling teams to build smarter, more connected systems by combining DDS with model-based systems engineering (MBSE). Here’s a breakdown of what DDS is, how it works with Rhapsody, and why it’s a major win for industries like aerospace, automotive, defense, and industrial IoT.

🧠 What is DDS?

Data Distribution Service (DDS) is a middleware standard defined by the Object Management Group (OMG), designed for scalable, real-time, and reliable data exchange in distributed systems. It uses a publish-subscribe communication model—perfect for:

  • Autonomous vehicles
  • Aerospace and defense systems
  • Industrial automation
  • Internet of Things (IoT) and cyber-physical systems

Key features of DDS:

  • ⚡ Low latency and deterministic communication
  • 🔁 Decentralized architecture (no single point of failure)
  • ✅ Built-in Quality of Service (QoS) management for reliability

💡 Why Combine DDS with IBM Rhapsody?

IBM Rhapsody is a powerful MBSE tool for designing and simulating embedded systems. Integrating DDS into Rhapsody brings multiple benefits:

1. Real-Time Simulation & Execution

Model systems in SysML or UML and simulate live DDS-based communication within Rhapsody. Perfect for systems where timing and data flow are critical.

2. Seamless Distributed Design

Define DDS publishers and subscribers directly in your Rhapsody models. Automatically generate DDS-compatible code for distributed execution.

3. Earlier Testing & Validation

Simulate DDS networks inside Rhapsody before deployment to reduce integration risk—vital for mission-critical domains.

4. Industry Standards Support

DDS is a core part of frameworks like AUTOSAR, ROS 2, and FACE. With DDS integration, Rhapsody projects stay compliant and future-proof.

🔧 How It Works

Using the SodiusWillert DDS integration for IBM Rhapsody, here’s how the workflow looks:

  1. Model your architecture in SysML or UML using IBM Rhapsody
  2. Use SodiusWillert M2M to transform SysML to UML
  3. Apply the DDS profile in Rhapsody
  4. Generate DDS-compliant source code
  5. Integrate with your target DDS libraries
  6. Build and execute your DDS applications
  7. Visualize results directly in Rhapsody

This approach enables a full MBSE cycle from modeling to real-time distributed execution.

🌍 Real-World Benefits

Whether you’re building autonomous vehicles, avionics systems, or industrial control software, DDS in Rhapsody provides:

  • 📉 Reduced development risk
  • 🧪 Testing before hardware is available
  • 🔁 Faster development cycles
  • 🛡️ Improved system robustness and reliability

🔎 Learn More

Want to dive deeper into DDS modeling with IBM Rhapsody? Need help setting up your DDS development environment?

👉 Contact us at SodiusWillert for a demo or expert advice.

Based on insights from a recent LinkedIn post by SodiusWillert Deutschland, this article highlights our commitment to advancing model-based engineering with real-time communication support.

Happy Distributing with Rhapsody!!

Walter van der Heiden email://walter@sodiuswillert.com

Detroit Rhapsody Rock Units

September 2, 2024 / / 0 Comments

Introduction

For our US Automotive Day I flew to Detroit again! I really like Detroit, it’s way better than its reputation!
We organized a day after the German Automotive Day example. Our Marketing Guru, Tom Hollowell, discovered a racing track. It offered a great conference place and a race track where we were driven around.
No we were not allowed to take the wheel, unfortunately, but we were chauffeured by 2 professional racing drivers.
It was pretty awesome. We had just enough rides for everybody. Luckily, not everybody had enough nerves to go in a fast car around the track.
So I went twice… Loved it…

Rhapsody Units

There are still people asking what “Units” are in Rhapsody. And it is easy: it is the smallest “Unit” you can store in CM separately. Default units are:

  • Model
  • Package
  • Component

Units are easily ( if you have good eyes, that is… ) recognizable by the small icon decorator in the lower left corner. The decorator is either Grey (saved) or Red ( not saved). This indicates that Rhapsody will store that “unit” in a separate file. It allows it to be stored separately in a CM (That is mostly file-based). By right-clicking on a “non-Unit” element in Rhapsody, you can select “Create Unit.” This will give you the opportunity to store a Unit in its own file. The property General::Model::DiagramIsSavedUnit causes all diagrams to be saved in a separate file. In the same Subject::Metaclass, you can also find properties like BlockIsSavedUnit, ClassIsSavedUnit, and ComponentFileIsSavedUnit. There are also properties like ComponentIsSavedUnit (Default on), FileIsSavedUnit, and FolderIsSavedUnit. You will find ObjectIsSavedUnit and PackageIsSavedUnit (Default on) too. With these, you can control what is a Unit and what not.

The file extensions are: (add an “x” for the post 8.3 file format)

ElementOld < 8.3New > 8.3
Model.rpy.rpyx
Package/Profile.sbs.sbsx
Component.cmp.cmpx
Object Model Diagram.omd.omdx
Sequence Diagram.msc.mscx
Use-Case Diagram.ucd.ucdx
Structure Diagram.std.stdx
Deployment Diagram.dpd.dpdx
Collaboration Diagram.clb.clbx
Panel Diagram.pld.pldx
Timing Diagram.tmd.tmdx
Class/Object.cls.clsx
Did I miss one????????x


Ann Arbor

After the event I was invited by Tom and Carol to a dinner in Ann Arbor. A beautiful place, we drove around after dinner. (Thanks again! It was great!) Tom always posts sunsets on FaceBook… unbeatable.

Have fun modeling with Rhapsody

Walter van der Heiden ( walter@sodiuswillert.com )

Rhapsody to Cameo: Save Time and Effort.

June 24, 2024 / / 4 Comments

Introduction

So… you are a Rhapsody user. Always have been, always will be. Like me, I also have a love/hate relationship with it. More love but there are times when I think: “Rhapsody??? really???”

But suppose you work somewhere in a place where people want to force you to use MagicDraw (Cameo). Not a bad tool, definitely not, but no Rhapsody. Because in spite of all it’s peculiarities, it’s a brilliant tool. And then there’s Code Generation.

You protest is futile: You have no choice. You have to. But… What to do with all your old models? Make them again? Use XMI (Spoiler alert: doesn’t work very well)

That’s only one use-case for a product we call “Publisher.” A tool that can take Rhapsody Models and save them as perfect Cameo models. Or the other way around. Or from System Architect. Or RSA. Or even Enterprise Architect!

Another use-case is that the US Defense Ministry demands models to be in Cameo format. In that case, you want a converter that 1:1 copies your Rhapsody Project to Cameo. Or saves it as a Cameo Model.

Wait! There’s more: If you really like Cameo (and who doesn’t!) then you can use it for Systems ENgineering and then use the Rhapsody CG to do Software Engineering.

So as you will understand: SodiusWillert has that. A perfect way to save your valuable models in another format with the certainty that no information is lost in the process.

Vegas. Really??

Yep. It seems all large events are in Vegas nowadays. Also the Siemens Realize live I had to visit. My regular readers know how I think about Las Vegas, read this BLOG entry if you don’t.

But the Siemens conference was great, it was in the Mandalay Bay, which is a bit less bad IMHO. We had a booth there and it was quit successfull, I think.
My personal highlight was the Keynote by Tony Hemmelgarn, CEO of Siemens DI SW. He spoke about the advantages of MBSE and mentioned Rhapsody in a very nice and loving way. I cannot remember an IBM event where I heard anybody speak in such a way about modeling (Except for me, of course! 😉 )

The best news was, however, that next years event will be in Detroit. And the European version in Amsterdam. Less travel. Also, only 6 hours of time difference and not 9. The latter is a real burden on the communication with home, there’s just not enough time overlap left. And the times that you are both awake, there is the fact that the times don’t sync. One always is doing something when the other has time to call and vice versa.

We spent some time walking around. I must confess that this “Sphere” was pretty impressive.

Back to the Publisher

First of all: here you can read all about it and… Try Before You Buy!

Convert systems models from IBM Rhapsody to Cameo Systems Modeler and Cameo MagicDraw with one click. Our Publisher for Rhapsody supports the conversion of modeling formats like SysML, UML, and UPDM and all model diagrams, elements, structure, and hierarchy. Convert large systems models fully automated with full support for diagrams, logging of model transformation action and configurable diagram layouts.

Save time manually cleaning up your target model by leveraging user-configurable settings and display styling in the conversion. Publisher for Rhapsody provides two configuration files that allow teams to control and consistently apply their defined methods and styling.

Publisher for Rhapsody implements model checking to identify, log, and report inconsistencies in the source model, then converts UML, UPDM, or SysML elements​ such as hierarchy, diagrams, and relationships to ensure 100% compatibility in Cameo Systems Modeler. For UPDM elements, it also converts Architecture Description, Packages, and Viewpoints.

The Publisher does the complete model. All model elements, also all diagrams! It keeps your diagrams in the same shape so you will recognize them in the blink of an eye! It even check-ups your models before converting them, we don’t want “garbage in, garbage out!”

Even roundtripping is supported. So if you want to exchange models that will be changed in oth tools: All possible!

That’s it for today. Feel free to contact me if you have any questions;

Happy Modeling with (either Cameo or ) Rhapsody.

Walter van der Heiden walter@sodiuswillert.com

Using MatLab Simulink with Rhapsody

April 3, 2024 / / 0 Comments

Back in Nantes

Since we are together with Sodius I have my regular visits to Nantes. Luckily! I really like Nantes and of course my collegues in Nantes. Always big fun and great to see beautiful Nantes.

Simulink

People still use Simulink; I’m always surprised that nobody objects to the fact that it generates code; people use it without thinking. When it’s Rhapsody, millions of objections pop up against Code Generation. Probably, it is because Simulink is used by all kinds of engineers and Rhapsody by Software Engineers who feel attacked in their honor by Rhapsody (That does an excellent job generating code,..)

Now, with the Automotive Extension, there is another way to integrate the two tools: ARXML. That’s a “lightweight” integration; it doesn’t add much. The real benefit comes from co-simulation, and that’s what Andy does in his video. AFAIK that still works (I do not own a Simulink license, I cannot try it)

Resources

Now, I could be explaining here how it works but other people have done that already, way better than I can.

Andy’s (old) video. Explains it really good.

Justin Dyer IBM explaining. A tiny bit newer than Andy’s video.

Frank Braun’s video. Great explaination!

IBM TechXChange Lab (Also by Andy, you need an IBM ID for that)

TechXChange

Coincidently I answered a question on TechXChange, about this, it seems the Library for CygWin is broken:

OK. Not so easy but it works:

Add to your configuration in the “Settings” Tab under: “Link Switches”:
"<<UserShare>>/LangCpp/lib/cygwinsimulinkintegrationapplx64.a"

(Replace the <<UserShare>> with the path to your UserShare directory.)

Then you need to build the Simulink library, the following files need to be placed:

– In the directory <<Share>>\LangCpp\SimulinkIntegration the file cygwinsimulinkintegration.mak

– In the directory <<Share>>\LangCpp\ the file cygwinbuild.mak

Then call “Code” and “Build the Framework” from the menu. there is 1 warning, you can ignore that.

You can also edit sitec++.prp and add the Cygwin makefilecontent with the changed linker statement. But this works too.

So. That’s it for today! Happy simulinking with Rhapsody!

Walter van der Heiden walter@sodiuswillert.com

Barcelonaaaaa ( & Rhapsody 10 )

March 20, 2024 / / 0 Comments

Travel is entirely back now. COVID is over. Well, it’s still there, but nobody cares anymore. So after the worldwide TechXChange in @#$%^&* Las Vegas ( See “I hate Las Vegas“), it was now the European version held in Barcelona.
I’ve been to Barcelona before (incidentally, that was where I got my own COVID infection…). I really like that city; it has beautiful architecture, a nice buzz, great food, and much, much more.

So I went to my second home (Schiphol Airport) by train, checked in, did the security check, and then went straight to the KLM Crown Lounge. I’m a luxury traveler; I have had a KLM Platinum badge for five years (and counting), which is so cool. It makes traveling (almost) bearable..

The flight was as it should be: quiet and fast. It takes only 2 hours from gate to gate. Love that. Then, the Uber to the hotel. We live in a beautiful time. The only thing I used was my phone. Everything I needed was there, and I did it on the phone. I booked the flight with the KLM App, Called Uber with the Uber App, and booked the hotel with the Hilton App. I checked the locations with maps; the IBM App had my entry ticket. The only thing you need is, of course, the phone and enough battery… And sometimes a connection. But that is only a problem in Germany; it all worked fine in Barcelona.

The venue was on a great location, near the sea, next to one of the recommended hotels. I wasn’t in that hotel, I booked too late. But I don’t mind a small ride in the morning/evening.

As in Vegas, there was also a sandbox where partners and IBM had booths and the Champions Lounge. Yes, I have been an IBM Champion for 4 years now! It’s like being KLM Platinum but even better!
Champions are treated as kings by IBM! Front-row seats and people who do nothing else than care for our wellbeing. Thanks Libby, Cathryn, Amy and all others!

Unfortunately there was not much ELM, most was, “the ol’ Hardware” I learned that Mainframes are not dead, on the contrary! One of the things I started with after I graduated was the IBM AS/400, now SystemZ. Still cool stuff. I also learned there are “open source” Mainframes.

Some small items were there on ELM, there was a small item about Rhapsody, the new version was coming. And loo and behold: on February 29, 2024 Rhapsody 10 was officially released!!!!

What is new: Actually all is new… The GUI is changed and therefor all under the hood needed a thorough make-over. And the IBM boys and girls did the magic, just like on the TV make-over programs for houses or people: the result is stunning.
Here is the official IBM “WhatIsNew“.
Soon I get back to you guys with more news about Rhapsody 10!

Also new is the HarmonyMBE profile. Yes that is our work, Andy made that and it’s part of Rhapsody! We have a BLOG about it, we will fill that with more information soon.

So. Have fun with Rhapsody (10, but also with the older versions)

Walter (wvdheiden@sodiuswillert.com)

Automotive Day 2023

October 19, 2023 / / 0 Comments

Automotive Systems und Software Engineering zwischen Standards, Effizienz und Qualität

Politische Vorgaben und Prioritäten sind kontinuierlichen Veränderungen unterworfen, und die Automobilindustrie wird wie kaum ein anderer Wirtschaftszweig durch politische Rahmenbedingungen in den Zielmärkten beeinflusst. Als beständiger Fakt in dieser sich ständig wandelnden Umgebung gilt: Die Fahrzeugelektronik ist der Schlüsselfaktor für die Agilität und Anpassungsfähigkeit der Modellstrategie. 

Um diesem Anspruch gerecht zu werden, wird die Elektronik immer komplexer. Die Anzahl der Module, Systeme, Schnittstellen und Varianten steigt rasant, und die Entwicklungsprojekte werden in gleichem Maße immer schwerer zu beherrschen. Dennoch sind Hersteller und Zulieferer, trotz der schwierigen Rahmenbedingungen, gefordert, qualitativ hochwertige und sichere Fahrzeuge zu liefern. 

Beim Automotive Day 2023 hören Sie von praktischen Erfahrungen bei Mercedes-Benz, Robert Bosch, FORVIA HELLA, Continental und anderen. Schwerpunktthemen sind unter anderem ASPICE, AUTOSAR, ISO26262, Systems Engineering, Prozesse und Normenkonformität. 

Dieses Event ist Ihre Plattform, von Erfahrungen Ihrer Peers zu profitieren und sich mit ihnen darüber auszutauschen, wie die täglichen Herausforderungen im Automotive Systems und Software Engineering bewältigt werden können.

Sichern Sie sich Ihren Platz beim Automotive Day 2023, und nehmen Sie Erkenntnisse mit, die Ihnen bei den weiteren Planungen in Ihrem Unternehmen helfen können.

Zitate von Teilnehmern des Automotive Day 2022:

„Es war eine sehr interessante Veranstaltung, darf gern länger sein!“

„Sehr hilfreich und informativ!!!“

„Gute Einblicke, interessante Gesprächspartner“

„Top Veranstaltung, gute Atmosphäre, tolle Gespräche und Vorträge“

„Es war super. Tolle Location, sehr gute Vorträge und hochkarätige Gespräche“

„Informative Vorträge, gute Möglichkeiten zum Netzwerken. Blick über den Tellerrand in die Domänen Mechanik, Elektronik“

Hotelinfos

Motel One München-Parkstadt Schwabing
Anni-Albers-Straße 10
80807 München

muenchen-parkstadtschwabing@motel-one.com

Photo by Pixabay on Pexels.com

I hate Las Vegas….

September 17, 2023 / / 3 Comments

Introduction

Yes. Sorry. But I do hate it. Noisy, Energy wasting, overpriced. I know there are few places in the world where you can organize big congresses like IBM Think, etc.
But really? Does it have to be in a place that forces you to walk through a flipping casino to get to where you have your congress?
Do you know how much energy that costs for a poor guy with Asperger’s? Thank god for Apple Airpods with noise canceling, Shades, and a Cap that prevents the lights from overflowing.
And then the prices. Not a single bottle of red wine under $100,-? Seriously?

But OK. We were there for the IBM TechXChange. I had a slot of an hour together with Ed Mayer from IBM. This went very well ( Though I would have liked more customers… )

How to start Rhapsody?

There are multiple ways to start Rhapsody.

Open a Model

Just double-click on a Rhapsody File, a .rpyx (Or an old .rpy file). But what will be started now??

  • The latest version of Rhapsody that you have installed. (Unless you have edited the registry)
  • The Rhapsody Version described in the rhapsody.ini file that belongs to the started version. So if DefaultVersion is “Developer” then that’s the one you get. That is: when you have a license!

This will also open the model that you have chosen. And the language of that model. Even if your defualt is e.g. C++ and the model is C, the latter is the one that is opened.

Create a shortcut

I like to have shortcuts for all the versions of Rhapsody so I can decide what I start. IN the shortcut you can:

  • Put a command line parameter to start the correct version _-dev_ed, etc -lang=c++
  • Change the directory where you start RHP. So you can store multiple rhapsody.ini files!

Use the Windows Menu

Just go to “Start”. Then you can choose the version you want. 8.x, 9.x, C/C++, Developer, Architect. (If you have installed “Developer”.

Use the Context Menu

You first need to edit some registry stuff to add the versions to the Windows Context Menu.

  1. Delete or rename HKEY_CLASSES_ROOT\rpyxFile and HKEY_CLASSES_ROOT\rpyFile
  2. Create file rpy_reg.reg for old model versions or rpyx_reg.reg for new model versions
  3. Change the paths and versions to match your version

rpy_reg.reg old fileformat

[HKEY_CLASSES_ROOT\.rpy]
@=""

[HKEY_CLASSES_ROOT\.rpy\shell]

[HKEY_CLASSES_ROOT\.rpy\shell\02_84C]

[HKEY_CLASSES_ROOT\.rpy\shell\02_84C\command]
@="C:\\Dev Tools\\IBM\\Rational\\Rhapsody\\8.4\\rhapsody.exe  %1  -dev_ed -lang=c"

[HKEY_CLASSES_ROOT\.rpy\shell\01_84C++]

[HKEY_CLASSES_ROOT\.rpy\shell\01_84C++\command]
@="C:\\Dev Tools\\IBM\\Rational\\Rhapsody\\8.4\\rhapsody.exe  %1  -dev_ed -lang=cpp"

[HKEY_CLASSES_ROOT\.rpy\shell\04_831C]

[HKEY_CLASSES_ROOT\.rpy\shell\04_831C\command]
@="C:\\Dev Tools\\IBM\\Rational\\Rhapsody\\8.3.1\\rhapsody.exe  %1  -dev_ed -lang=c"

[HKEY_CLASSES_ROOT\.rpy\shell\03_831C++]

[HKEY_CLASSES_ROOT\.rpy\shell\03_831C++\command]
@="C:\\Dev Tools\\IBM\\Rational\\Rhapsody\\8.3.1\\rhapsody.exe  %1  -dev_ed -lang=cpp"

[HKEY_CLASSES_ROOT\.rpy\shell\06_815C]

[HKEY_CLASSES_ROOT\.rpy\shell\06_815C\command]
@="C:\\Dev Tools\\IBM\\Rational\\Rhapsody\\8.1.5\\rhapsody.exe  %1  -dev_ed -lang=c"

[HKEY_CLASSES_ROOT\.rpy\shell\05_815C++]

[HKEY_CLASSES_ROOT\.rpy\shell\05_815C++\command]
@="C:\\Dev Tools\\IBM\\Rational\\Rhapsody\\8.1.5\\rhapsody.exe  %1  -dev_ed -lang=cpp"\

rpyx_reg.reg new fileformat

Windows Registry Editor Version 5.00

[HKEY_CLASSES_ROOT\.rpyx]
@=""

[HKEY_CLASSES_ROOT\.rpyx\rpyxFile]

[HKEY_CLASSES_ROOT\.rpyx\rpyxFile\ShellNew]

[HKEY_CLASSES_ROOT\.rpyx\shell]

[HKEY_CLASSES_ROOT\.rpyx\shell\01_902C++]

[HKEY_CLASSES_ROOT\.rpyx\shell\01_902C++\command]
@="C:\\IBM\\Rhapsody\\9.0.2\\rhapsody.exe  %1  -dev_ed -lang=cpp"

[HKEY_CLASSES_ROOT\.rpyx\shell\02_902C]

[HKEY_CLASSES_ROOT\.rpyx\shell\02_902C\command]
@="C:\\IBM\\Rhapsody\\9.0.2\\rhapsody.exe  %1  -dev_ed -lang=c"

[HKEY_CLASSES_ROOT\.rpyx\shell\03_901C++]

[HKEY_CLASSES_ROOT\.rpyx\shell\03_901C++\command]
@="C:\\IBM\\Rhapsody\\9.0.1\\rhapsody.exe  %1  -dev_ed -lang=cpp"

[HKEY_CLASSES_ROOT\.rpyx\shell\04_901C]

[HKEY_CLASSES_ROOT\.rpyx\shell\04_901C\command]
@="C:\\IBM\\Rhapsody\\9.0.1\\rhapsody.exe  %1  -dev_ed -lang=c"

Now create the registry entries with double click on rpyx_reg.reg or rpy_reg.reg. 

Thanks to Dennis Koelbel!

Have fun modeling with Rhapsody!

Walter van der Heiden ( walter@sodiuswillert.com )

« Older posts

© 2025 Rhapsody TechBlog

Theme by Anders Noren — Up ↑