IBM Rational Rhapsody and Add-On registration and registry key access when switching between versions

Answer

In general, the update of the registry is done by a COM mechanism which is not under IBM Rhapsody control.

If you want to know what is being changed, you can do the following steps:

1. Take a clean machine
2. Backup the registry
3. Install Rhapsody
4. Backup the registry
5. Compare the two versions of the registry

A way to check registry keys:

Use the procmon tool:
https://technet.microsoft.com/en-us/library/bb896645.aspx

When launching it, capture the Rhapsody process only and filter the registry access requests only. Same for regsvr (capture according to process name). It will show you all registry access requests.


In terms of product registering and registry keys:


Rhapsody (core product)


rhapsody.exe /RegServer


(this also invokes the rhapsody.tlb necessary for COM and VBA)


This is similar to executing:


rhapsody.reg


(in the Rhapsody root you will fine this file, and can execute by double - clicking on it (or put in a script))

Recommendation is to use /RegServer to ensure COM API registered

These do some registering of the Rhapsody core within HKEY_CLASSES_ROOT:


HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Rhapsody.Application
HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Rhapsody.Application.1
HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Wow6432Node\CLSID
HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Wow6432Node\TypeLib\{47DBF9D5-F318-1
1D2-B825-00104B3E6572}

HKEY_CLASSES_ROOT\Rhapsody.Application = Rhapsody Application
HKEY_CLASSES_ROOT\Rhapsody.Application\CLSID =
{57DBF9D8-F318-11D2-B825-00104B3E6572}

HKEY_CLASSES_ROOT\CLSID\{47DBF9EE-F318-11D2-B825-00104B3E6572} =
Rhapsody Application
HKEY_CLASSES_ROOT\CLSID\{47DBF9EE-F318-11D2-B825-00104B3E6572}\ProgId =
Rhapsody.Application
HKEY_CLASSES_ROOT\CLSID\{47DBF9EE-F318-11D2-B825-00104B3E6572}\LocalServ
er32 = C:\Rhapsody813_32bit\rhapsody.exe

HKEY_CLASSES_ROOT\TypeLib\{47DBF9D5-F318-11D2-B825-00104B3E6572}\1.0\0\w
in32 = C:\Rhapsody813_32bit\rhapsody.tlb

HKEY_CLASSES_ROOT\TypeLib\{47DBF9D5-F318-11D2-B825-00104B3E6572}


By default on Microsoft Windows NT systems, the 'INTERACTIVE' user has 'Special Access' rights to this registry key and all of it's sub keys.


ReporterPLUS:

regsvr32 ReporterDLL.dl

will ensure registration of this tool but the keys accessed do not defer from the above from what we can establish.

Any problems in registration, the user will be notified of it's failure.


Gateway:

Gateway -regserver is a plus but not fundamental (only involved with a few features from external tools).


"Gateway\bin.w32\rg.exe" -regserver


(The RG command with -regserver argument registers the Rhapsody Gateway COM API to enable automation from other programs such as VBS or DOORS DXL. This is necessary for navigation from DOORS Module to Gateway so it is recommended.)

Some more background information:

To locate DOORS, Gateway looks in the Windows registry:
1. HKEY_CLASSES_ROOT\DOORS.Application\CLSID\ ===> it takes the CLSID value

Then it looks into:
2. HKEY_CLASSES_ROOT\CLSID\{the-previous-CLSID-value}\LocalServer32\

When you run the DOORS client, the first registry key is supposed to be updated unless the user
does not have the rights.

You are not supposed to update the second registry key manually, instead, you are supposed to fix
the first key so the CLSID points to a valid registry location.

Otherwise, there is work around, you can define the environment variable DOORS_SCRIPT with the full path of doors.exe (which is easily done and there is public technote on this
http://www.ibm.com/support/docview.wss?uid=swg21426873 )