• Jazz ID Registration
• Repository and Project Area Access
• RTC Client Setup

A repository connection is just what it sounds like: a connection to our RTC repository. The repository holds the source code, defects, enhancements, other work items, etc.

1. From the Team Artifacts view, click Create a Repository Connection
2. For URI, put https://jazzdev02.rtp.raleigh.ibm.com:9443/jazz02
3. For login info, use your Jazz.net credentials
   • If it asks if you want to accept the certificate, accept the certificate permanently
4. Right click on the repository connection you just established
5. Click Manage Connected Project Areas
6. Select Rational Quality Manager and Rational Quality Manager Private
7. Click Finish

Optionally, you may want to create the following repository connections and connected project areas for opening/viewing/linking work items:

• https://jazzdev.rtp.raleigh.ibm.com:9443/jazz:

  • ALM Portfolio (CCM)
  • Jazz Collaborative ALM
  • Jazz Foundation
  • Jazz Reporting Service
  • Rational Team Concert

• https://jazzdev02.rtp.raleigh.ibm.com:9443/jazz02:

  • JazzCS
  • Rational Quality Manager
  • Rational Quality Manager Private

• https://jazzdev03.rtp.raleigh.ibm.com:9443/jazz03:

  • Requirement Management
  • Requirement Management Private

• https://jazzdev04.rtp.raleigh.ibm.com:9443/jazz04:

  • Design Management
  • Design Management (Private)
  • Rational Publishing Engine
  • Rational Publishing Engine (Private)

To start making changes in QM, you'll obviously need the QM source code. These are the steps you need to take to get a copy of the QM source code stored locally on your workstation.

• Creating a repository workspace is only required once. After the once, you will login to your existing repository connection each time you launch Eclipse. While you can still make new repository workspaces, it is rarely necessary.

1. Click Rational Quality Manager Private then Source Control
2. Right click the mainline stream for the current development release (Quality Manager Mainline (RQM 6.0.6.1 or earlier) or Engineering Test Management Mainline (ETM 7.0 or later)) then select New Repository workspace
   • Note: If you have set up a repository workspace in the past, go to Connect to existing Workspace instead.
3. Click Finish
4. In the new window, select Find and Load Eclipse projects
5. Click Finish

Note: There is no need to load the following components:

• CQTM Migration Client
• QMMobileClient¹
• RelEng Common
• STAX LM SPI Integration
• XSLFO

The streams to be used for ETM is as follows -

Engineering Test Management Mainline - This will be used for the 7.0.3 mainline sprint deliveries example - 7.0.3 Sprint12, 7.0.3 Sprint 13 etc
Engineering Test Management Stable Used for Stable Stream deliveries when the mainline is locked for the development example - 7.0.3 Sprint12
Test Management 7.0.2 FixDelivery Mainline Used for all defects on top 7.0.2 ifix08 mainline. Defects will be forward ported to 7.0.3 mainline
Test Management 7.0.2 FixDelivery Stable Critical defects to be delivered to mainline and Stable when the streams are locked during testing stage
User Assistance - RQM 7.0.3 User Assistance 7.0.3 mainline deliveries
User Assistance - RQM 7.0.2 Used for User Assistance 7.0.2 delivery

¹ Required if developing the RQM Mobile Application.

These steps ensure you will always have a recent version of the target platform. To use a specific target platform, see this.

1. Click the Reload Target Platform button
2. Enable Reload Automatically and Clean Projects after Reload
3. Open Eclipse settings
4. Search for target platform
5. Select the one for the latest release with "Integration Prerequisites"
6. Click apply
7. Log in with your jazz credentials
8. Click Ok
   • Note: It may take a while for the target platform to load

Some of the packages have additional dependencies and cause errors in the workspace, or are rarely worked on by most developers. The QMMobile client is an example of one of these. The FVT packages mentioned below also require additional dependencies and are only used by testers, not developers. So, these packages should be closed.

1. Open the package explorer in eclipse
2. Click the downward point arrow
3. Click Top Level Elements, then Working Sets
4. Right click the QMMobile client and close project
5. Expand Test Automation
6. Right click and close
   • com.ibm.team.fvt.tests.qm
   • com.ibm.team.fvt.tests.qm.bvt
   • com.ibm.team.fvt.tests.qm.junit
7. Expand RelEng Common
8. Right click and close
   • com.ibm.team.releng.common.anttasks
   • com.ibm.team.releng.common.anttasks.source
9. Expand Offerings
10. Right click and close
    • com.ibm.team.install.rqm.license
11. Expand Tools
12. Right click and close
    • com.ibm.rqm.devtools.ecoreanalyzer
13. In some maintenance releases (e.g. 6.0), you may need to close the following plug-ins to remove build path cycle errors and then reopen the plug-ins:
    • com.ibm.rqm.performance.proxy.common
    • com.ibm.rqm.performance.proxy.feature
    • com.ibm.rqm.performance.proxy.service
    • com.ibm.rqm.server.proxy.test.generator
    • com.ibm.rqm.server.proxy.test.performance

1. Expand "My Repository Connections"
2. Right click on the one you want to load
3. Click "Finish"

1. If you see an error message that looks like the following: you may need to apply to get the following permissions:
   • Rational Quality Manager - Quality Professional-Floating
   • Rational Team Concert - Developer-Floating
   • Rational DOORS Next Generation - Analyst-Floating

and this can be done via opening a RES ticket. We believe this should be part of getting permissions but need to confirm.