IBM Rational Rhapsody on a database? No way! Really?
As those of us who know and love IBM
And as those of us who know and love the IBM
So, the natural question is whether you can bring Rhapsody to the Jazz platform to take advantage of all the Jazz goodness. Well, yes you can. Let me introduce you to IBM Rational Rhapsody Design Manager (Rhapsody DM) or as I like to call it, "Rhapsody on Jazz."
A change of mind-set
To take full advantage of Rhapsody DM, you will need to stop thinking about the Rhapsody tool as working with a set of model files. Rather, in this mode, it's now the "rich client"—or just another client—of the Jazz-based Rhapsody DM model server which hosts your models. Why do I say "just another client”? Because now you can view the model in read-only mode on a web client using your web browser and collaborate on things like reviews and team areas. In the following diagram, you can see a typical deployment of Rhapsody DM in this mode:
Rich client versus web client
So, what are the differences between these two types of clients? The rich client is the fully functional Rhapsody tool that you're already familiar with. However, the model that you're working with on the rich client can be hosted on the Rhapsody DM server instead of on your file system. By working with a model hosted on the Rhapsody DM server, you gain collaboration capabilities. The following screen capture shows the Rhapsody rich client with some of the Rhapsody DM collaboration views:
On the other hand, the models that you can view on the web client have to be hosted on the Rhapsody DM server. You cannot edit these models on the web client but you can do things like set up team areas, perform reviews and mark up diagrams. With the web client, you have the ability to view a model without having Rhapsody installed on your workstation. All you need is a web browser, the URL for the Rhapsody DM server and the appropriate access permissions. You can see some of the web client's collaboration capabilities in the following screen capture:
Everything I have explained so far is just one of three choices you have for working with Rhapsody and Rhapsody DM. It is called the “actively managed” mode. The Rhapsody DM server actively manages your model and provides not only collaboration capabilities, but also configuration management (CM) capabilities that you can use to manage your models in a multi-user, parallel development mode. You have the ability to exclusively lock model elements or create baselines and snapshots, among other things.
However, you also have the option of working in “externally managed” mode. In this case, you will continue working in Rhapsody in file-based mode, but you can choose to set up regularly-scheduled imports of your model to the Rhapsody DM server to perform collaborative activities such as reviews and diagram mark-ups. Of course, in this case model CM is not done in Rhapsody DM; though you might do this externally with a CM tool that Rhapsody interfaces to.
Finally, the third option is to continue using everything the way you are now, which is to use Rhapsody without Rhapsody DM in file-based mode.
Come to think of it, you also have a fourth option, which is a combination of the above. For example, you could be working with one model that is actively managed, another model that is externally managed and yet another one that is file-based.
You now have many more options for how you want to work with Rhapsody and I hope this blog post has piqued your interest in IBM