It's all about the answers!

Ask a question

Reporting across multiple data warehouses


David Doughty (1812219) | asked Jul 20 '11, 5:30 a.m.
hi,

due to our historical deployment of RTC we will have multiple "silo" deployments of RTC, a new RRC deployment and shortly RQM. Each will be supported by a JTS, and therefore a DWH (data warehouse).

I have limited understanding of insight, but it seems to me that having independant DWH is going to limit or complicate our reporting capacity, especailly generating consolidated reports across the lifecycle, requirements to change to tests.

So, what we would be looking for is a mechanism to generate consolidate reports which extract data from RRC,RTC and RQM, across multiple projects.

Does Insight facilitate this? I understand that it allows multiple datasets (similar to RPE), which I assume can then be joined to formulate a more detailed report.

Are there any caveats or issues that we should be aware of with our topology (which currently cannot be changed)....

3 answers



permanent link
Jeff McRae (2711) | answered Jul 21 '11, 8:44 a.m.
FORUM MODERATOR / JAZZ DEVELOPER
hi,

due to our historical deployment of RTC we will have multiple "silo" deployments of RTC, a new RRC deployment and shortly RQM. Each will be supported by a JTS, and therefore a DWH (data warehouse).

I have limited understanding of insight, but it seems to me that having independant DWH is going to limit or complicate our reporting capacity, especailly generating consolidated reports across the lifecycle, requirements to change to tests.

So, what we would be looking for is a mechanism to generate consolidate reports which extract data from RRC,RTC and RQM, across multiple projects.

Does Insight facilitate this? I understand that it allows multiple datasets (similar to RPE), which I assume can then be joined to formulate a more detailed report.

Are there any caveats or issues that we should be aware of with our topology (which currently cannot be changed)....


Hi

Rational Insight is deliberately designed to use an independent data warehouse. This way data can be ETL'd (extract, transform and load) from the various products into the Insight data warehouse so that reports can be generated which cross many products and provide linkage between the domains that you mentioned. Insight seems to fit your requirements very well.

permanent link
David Doughty (1812219) | answered Jul 22 '11, 4:39 a.m.
hi,

due to our historical deployment of RTC we will have multiple "silo" deployments of RTC, a new RRC deployment and shortly RQM. Each will be supported by a JTS, and therefore a DWH (data warehouse).

I have limited understanding of insight, but it seems to me that having independant DWH is going to limit or complicate our reporting capacity, especailly generating consolidated reports across the lifecycle, requirements to change to tests.

So, what we would be looking for is a mechanism to generate consolidate reports which extract data from RRC,RTC and RQM, across multiple projects.

Does Insight facilitate this? I understand that it allows multiple datasets (similar to RPE), which I assume can then be joined to formulate a more detailed report.

Are there any caveats or issues that we should be aware of with our topology (which currently cannot be changed)....


Hi

Rational Insight is deliberately designed to use an independent data warehouse. This way data can be ETL'd (extract, transform and load) from the various products into the Insight data warehouse so that reports can be generated which cross many products and provide linkage between the domains that you mentioned. Insight seems to fit your requirements very well.

Hi Jeff,

Am I correct to assume from your responseno that we can set up 1 insight DWH and ETL data from multiple RTC, RRC, RQM instances into it???

thanks

dD

permanent link
David Doughty (1812219) | answered Jul 22 '11, 4:48 a.m.
I think that I have answered my own question, having read the documentation....

Your answer


Register or to post your answer.


Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.