How to integrate ClearQuest and RQM?

We have RQM and ClearQuest setup separately, now would like to integrate them so tester can log defect from either RQM or CQ and run reports on both.

It seems to have different ways, i.e. ClearQuest Bridge or ClearQuest Connector. What is the simplest and reliable configuration to doing this.

TIA.

We have RQM and ClearQuest setup separately, now would like to
integrate them so tester can log defect from either RQM or CQ and run
reports on both.

It seems to have different ways, i.e. ClearQuest Bridge or ClearQuest
Connector. What is the simplest and reliable configuration to doing
this.

TIA.

The simplest configuration is to use the Bridge ... no need to define
sync rules that map the (arbitrarily customizable) CQ record schema to
the (arbitrarily customizable) RTC work item schema. But as Patrick
says, you will have to work harder to get cross-cutting queries and
reports.

Cheers,
Geoff

gmclemmwrote:
The simplest configuration is to use the Bridge ... no need to define

sync rules that map the (arbitrarily customizable) CQ record schema
to
the (arbitrarily customizable) RTC work item schema. But as Patrick

says, you will have to work harder to get cross-cutting queries and

reports.

Cheers,
Geoff

See Patrick's comment about running reports.

If you use the Bridge, the requests are stored only in CQ (unlike the
Synchronizer, which creates a copy, and keeps them synchronized), so you
won't be able to see them with reports that run against the RQM repository.

Cheers,
Geoff

gmclemmwrote:
See Patrick's comment about running reports.

If you use the Bridge, the requests are stored only in CQ (unlike
the
Synchronizer, which creates a copy, and keeps them synchronized), so
you
won't be able to see them with reports that run against the RQM
repository.

Cheers,
Geoff




Will CQ see defect logged in RQM with Bridge setup?

Yes, with the Bridge, when you post a request/defect in RQM, it actually
creates that request as a CQ record, and then links that record back to
the appropriate RQM objects (test results, whatever).

So from a data perspective, everything about the request (except the
link) is stored in CQ, and the RQM WebUI just makes it easy for you to
create those requests, and then navigate to that request (when you click
on that link, you effectively end up in the CQ WebUI).

Cheers,
Geoff

gmclemmwrote:
Yes, with the Bridge, when you post a request/defect in RQM, it
actually
creates that request as a CQ record, and then links that record back
to
the appropriate RQM objects (test results, whatever).

So from a data perspective, everything about the request (except the

link) is stored in CQ, and the RQM WebUI just makes it easy for you
to
create those requests, and then navigate to that request (when you
click
on that link, you effectively end up in the CQ WebUI).

Cheers,
Geoff

ClearQuest bridge will allow RQM users to log defects in CQ as part of their workflow. The defects would be stored in CQ, and linked to from RQM.

ClearQuest connector will synchronize defect records between the CQ and RQM databases.

What are you using for reporting? The most robust solution is to use ClearQuest bridge and then use Rational Insight for reporting (it supports connectivity to multiple data sources -- in this case, RQM and CQ). If you do not have an Insight license available, you might want to consider using ClearQuest connector so that you can use the free reporting solution (Rational Common Reporting for RQM) to report on your defects.

We want to track defect by requirement and test case/plan, and vice versa. So probably we'll run the report in RQM. Will it works if we configure CQ Bridge?

Also will the defect logged in RQM appears in CQ?

Thanks,
Gary