Month: January, 2008

Happy new year everyone! Our team is hard at work creating additional collateral and guidance for some of the new RMC 7.2 features. First up are the missing online pages for the new Workspaces capability. This feature is intended for advanced users that want to scale up their method development effort with their team(s). It allows you to distribute a method library to many filesystem directories throughout your network infrastructure, which so far had to be maintained in exactly one directory. In this workspace mode a method library is able to reference method plug-ins and method configurations that even exist in other libraries without importing or exporting. This allows you to easily share method plug-ins across teams, manage your plug-in in multiple ClearCase VOBs, or even mix and match plug-ins maintained in different source control system.

Download some overview slides here: Overview to RMC Workspaces. The first slide shows you a typical customer situation in which workspaces make a big difference. You see that several teams manage their own method libraries, but that some method plug-ins are used by more than one team. What normally happens is that one team owns and maintains the content of a plug-in and that many other teams reuse these plug-ins in their library. Before RMC 7.2 is was required that users export these plug-ins, zip them up, send them to their partners, those would import them into their local library. Now, all you do is maintain all your plug-ins in a source control system and the other teams can pick and choose plug-ins from that server (instead of loading an entire library as it was required by 7.1.x). The way this has been realized is by utilizing the Eclipse workspace capability and the option to now make every method plug-in an Eclipse project; instead of managing the whole method library as one Eclipse project in 7.1.x. The old way is still supported by RMC 7.2 and in fact is the default usage model, hence nothing will change if you are not interested in using the new feature. Everything can stay the same. However, if the attached help pages show you how you can convert your existing library into such a new workspace library and use that.

An example for using the feature you see on Slide 2. It shows a Library view of RMC in Workspace mode that uses method plug-ins that are physically stored in different locations: the my.test one is stored in my local workspace directory. Here I can experiment and author locally without the need to share the files with other by checking them in. The second and third plug-ins with the yellow harddisk symbol overlay icons indicate that these method plug-ins are managed in CVS. These are actually coming directly from the EPF Server on eclipse.org. The fourth one with the blue frame is managed on a ClearCase here in my office and stored in my local ClearCase view directory. The same is true for the configurations: the first one is in CVS the second in ClearCase.