Warning! I'm not a RTC expert. This is explained so testers might benefit from it.

Guidance on using source control from Rational Integration Tester



  1. Setup of RIT/RTC connection
  2. Defect creation
  3. Code Management (Full RTC/Tiny RTC)

Setup the "Test Code Management"

This paragraph describes the steps to setup a environment where each user has it's own (local) sandbox and can share changes using RTC.

Several steps might be optional or already done if you repeat the sequence.

Make connection to RTC

Now we have connected to a Repository

Make Repository Workspace

Now we create a Repository Workspace which we will load to our local computer.

Load Repository Workspace to local Sandbox

Now we have created a Repository Workspace configured and a local Copy is loaded on the computer.

Open the RIT Project

For change propagation check next paragraphs.

Defect Creation

When a test fails, you can create a defect from the GUI.

Figure: Select CM environment and Workitem Type

Figure: Sample RTC defect creation from RIT.

Change Propagation - Heads Up

Heads Up! I'm not a RTC expert.
Suppose two developers are working on the same piece of code (e.g. java class) at the same time. When delivering the changes can be merged using advanced code comparators.
These kind of merging options are not available for tests. So be sure that not two SV-developers are working on the same artifact.

Change Propagation - Full RTC

With Full RTC I mean the complete useage of RTC Work Items and controlled propagation.

Figure: The 'whole' process of change propagation.

On the first user

Just to your work in RIT. Save your work as you normally would do. When it's in acceptable state than you can ask for a refresh on the Pending Changes view (use twisty to request "Refresh Sandboxes and Remote Changes").
Apply changes as you would expect.

Figure: Change in RIT is shows in the Eclipse

Request for a Check In. This makes a copy the changes from the Sandbox to the server residing Repository Workspace. This workspace can be shared with other users (e.g. for debugging purposes).

Figure: Check in of change

Advice! Check in frequently.

The (default) rules of the SCRUM template are set that changes can only be delivered when a work item is attached. You can disable the rule, see Tiny RTC.

Figure: Apply a Work Item

When the work item is applied (e.g. drag/drop) than you can deliver the changes to the stream. The deliver action copies Repository Workspace content to the Steam.

On the second user

Figure: Checkin of change

At various (contextual) menu's of RIT there is a Refresh.

Change Propagation - Tiny RTC

Sample! I'm not a RTC expert.
Depending on the need of the customer/project you might re-use some of these settings/configuration. There are disadvantages of this approach, like less control over what's delivered by who.

Tiny RTC is a configuration of the Scrum process template where the rule to attach Work Items to changes is removed. With the proposed settings in RIT Eclipse both Delivering and Receiving of test ware is a 2 step approach.

RIT Customization for Tiny RTC

These settings are RIT Eclipse configurations to automate even more on the client side.

In the RIT Eclipse GUI:

Add the Pending Changes View to your favourite perspective.



Receiving changes happens in a similar fashion

Repository Workspace

The repository workspace resides on the server. This way it can easily be shared with others. Not only other developers but also a build machine.

Figure: RIT RTC Repository Workspace definition


Make sure you are loading the Repository Workspace on a non-used directory.

By executing a load on a already loaded Repository Workspace you can view the location where it's loaded.
Use always the Advanced option to steer the location of you local Sandbox.

Figure: Re-loading shows the current settings.


Installing the RTC plugin in RIT

RTC Help: Installation Instructions for Eclipse.
Based on that documentation, the following steps are to install the RTC Client in the RIT Eclipse client.

  1. Download the "p2 Install Repository" from Jazz.net
    No need to unzip it.

    Figure: The "p2 Install Repository" to install RTC Client in RIT Eclipse.


    The "Client for Eclipse 3.6.x IDE" or
    "CLient for Eclipse 4.2.x IDE" or
    "Client for Eclipse IDE (Extension install)" will NOT give the RTC Client

  2. In RIT, select File > Source Control
    The source control option of RIT appears.
  3. If needed cancel the "Share Project" window

    Figure: The Eclipse environment of RIT

  4. Select Help > Install New Software ...

    Figure: The Eclipse environment of RIT

  5. Select "Availabel Software Sites".
  6. Select Add to
  7. Select Archive
  8. Select the RTC-Client-p2Repo-5.0.1.zip
    Select Ok
  9. Point the "Work With:" to the zip-file.

    Figure: Point to the right zip file

  10. Select the Rational Team Concert Client Feature
    Accept the License
  11. Select Finish
  12. Select OK on the Security Warning
  13. A restart of RIT is needed

When opening the details of the pop-up you will see that RIT will download directly from internet. Apparently an internet connection is needed to download.eclipse.org.

Note: At a customer we noticed that if the user directory is mapped to a UNC path //FILE-USERS/User.. etc. the Overview tab of the WI is not filled. Forcing to use a local directory solves this issue. D:\Program Files\IBM\RationalIntegrationTester\GHTools.ini

D:\Program Files\IBM\RationalIntegrationTester\jre\bin\j9vm\jvm.dll
D:/Program Files/IBM/RationalIntegrationTester
You must force redirect to a local disk:
D:\Program Files\IBM\RationalIntegrationTester\jre\bin\j9vm\jvm.dll
D:/Program Files/IBM/RationalIntegrationTester

Un-installing a plugin

Check here

Configure the CCM in RIT

There is no need to install the RTC Plugin to have this integration.

Root services:


Figure: Configuration of RTC as CM system

Check this technote: Raise Defect fails to display the defect form

Proposed Settings

Other sources