Hello,

You should be able to do this at a later date, without moving the existing DW data.

Note, by jts/admin, jts/setup, ccm/admin, qm/admin I mean the full url required to access the administrative web interface for a specific application. For example jts/admin for a server running on the machine smiley.example.com on default port, would be https://smiley.example.com:9443/jts/admin.

Access the jts/setup configuration interface. Skip all the pages (which, on a healthy server should have a green status) until you reach the data warehouse configuration page (no pages should require you to perform an action; if that's the case, there might be a problem with the way the server is configured).

So, after skipping all those pages by testing the connections and whatnot, in the datawarehouse configuration page you can specify the Oracle database info and use the Create Tables button to initialize it. After that, specify the etl user credentials (probably you want to reuse the existing user) and click Next. This will save the info about the Oracle DW. Continue in order to make sure the same Oracle DW info is specified for the other applications as well (CCM and QM). Do not finalize any application. The application should detect that the finalize process has been launched already.

Go to jts/admin and access the Reports tab. Check that the correct user credentials are specified for the jobs listed in the Data Warehouse Collection Jobs section.
You can also verify the DW connection information by going to the Data Warehouse Connection section.
Access the ccm/admin and qm/admin admin interfaces and perform the same verification as in the case of jts/admin to make sure the Oracle DW is used by all of the applications.
Then go back to jts/admin and access the Reports tab and click on Run all data warehouse collection jobs for all applications link. This will trigger a full load into the DW (because the Oracle DW is new). After all the ETLs finish successfully (the Star job is the last one to run), the DW should be fully loaded and ready for reporting.

Here are the steps summarized for your convenience:
1. Access jts/setup. The Introduction page is loaded. Click Next.
2. Test the public URI. Click Next.
3. Wait for the JTS database connection to be verified (should be green). Click Next.
4. Click Next on the email notifications page.
5. No applications should require registration. Click Next.
6. The user registry should already be configured (and green). Click Next.
7. On the Configure Data Warehouse page you get to specify the Oracle DW info and use the Create Tables button to initialize the Oracle DW. After the tables are created you need to specify the credentials for the ETL user (probably you will want to reuse the existing user). Click Next.
8. The CCM database should test ok. Click Next.
9. On the Configure Data Warehouse page you get to verify that the same Oracle DW will be used by CCM. Make the necessary changes (if needed) and test the connection. Specify the same ETL user if it's not already set. Click Next.
10. The CCM application should not require finalization. Click Next.
11. The QM database should test ok. Click Next.
12. On the Configure Data Warehouse page you get to verify that the same Oracle DW will be used by QM. Make the necessary changes (if needed) and test the connection. Specify the same ETL user if it's not already set. Click Next.
13. The QM application should not require finalization. Click Next.
14. The RM application should detect that the finalization process has been successfully executed already. Click Next.
15. Same goes for the Finalize Setup page. Click Next.
16. Click Finish and go to Jazz Team Server - Server Administration.
17. Access the Reports tab and verify that all the ETL jobs from the Data Warehouse Collection Jobs section have the correct credentials specified. Check that the Oracle DW info was saved correctly by going to the Data Warehouse Connection section.
18. If CCM and QM are installed, access the ccm/admin and qm/admin interfaces and verify the DW info similar to Step 17.
19. Access jts/admin (Server Administration url) and go to the Reports tab. Once the jobs are loaded, click on Run all data warehouse collection jobs for all applications link. This will trigger a full load into the DW (because the Oracle DW is new). After all the ETLs finish successfully (the Star job is the last one to run), the DW should be fully loaded and ready for reporting.

Good luck!
P

I believe Tony was looking for a way of migrating all the historical
data that has been collected in the current data warehouse (for trending
reports). Does the process you describe do that, or does it just
initialize the new data warehouse with a single initial snapshot?

Cheers,
Geoff

On 6/13/2011 7:08 PM, pacsinte wrote:

Hello,

You should be able to do this at a later date, without moving the
existing DW data.

Note, by jts/admin, jts/setup, ccm/admin, qm/admin I mean the full url
required to access the administrative web interface for a specific
application. For example jts/admin for a server running on the
machine smiley.example.com on default port, would be
https://smiley.example.com:9443/jts/admin.

Access the jts/setup configuration interface. Skip all the pages
(which, on a healthy server should have a green status) until you
reach the data warehouse configuration page (no pages should require
you to perform an action; if that's the case, there might be a
problem with the way the server is configured).

So, after skipping all those pages by testing the connections and
whatnot, in the datawarehouse configuration page you can specify the
Oracle database info and use the Create
Tables button to initialize it. After that, specify
the etl user credentials (probably you want to reuse the existing
user) and click Next. This will save the info about the Oracle DW.
Continue in order to make sure the same Oracle DW info is specified
for the other applications as well (CCM and QM). Do not finalize any
application. The application should detect that the finalize process
has been launched already.

Go to jts/admin and access the Reports
tab. Check that the correct user credentials are specified for the
jobs listed in the Data Warehouse Collection
Jobs section.
You can also verify the DW connection information by going to the
Data Warehouse Connection section.
Access the ccm/admin and qm/admin admin interfaces and perform the
same verification as in the case of jts/admin to make sure the Oracle
DW is used by all of the applications.
Then go back to jts/admin and access the Reports tab and click on
Run all data warehouse collection jobs for all
applications link. This will trigger a full load into
the DW (because the Oracle DW is new). After all the ETLs finish
successfully (the Star job is the last one to run), the DW should be
fully loaded and ready for reporting.

Here are the steps summarized for your convenience:
1. Access jts/setup. The Introduction
page is loaded. Click Next.
2. Test the public URI. Click Next.
3. Wait for the JTS database connection to be verified (should be
green). Click Next.
4. Click Next on the email notifications page.
5. No applications should require registration. Click Next.
6. The user registry should already be configured (and green). Click
Next.
7. On the Configure Data Warehouse page
you get to specify the Oracle DW info and use the
Create Tables button to initialize the
Oracle DW. After the tables are created you need to specify the
credentials for the ETL user (probably you will want to reuse the
existing user). Click Next.
8. The CCM database should test ok. Click Next.
9. On the Configure Data Warehouse page
you get to verify that the same Oracle DW will be used by CCM. Make
the necessary changes (if needed) and test the connection. Specify
the same ETL user if it's not already set. Click Next.
10. The CCM application should not require finalization. Click Next.
11. The QM database should test ok. Click Next.
12. On the Configure Data Warehouse page
you get to verify that the same Oracle DW will be used by QM. Make
the necessary changes (if needed) and test the connection. Specify
the same ETL user if it's not already set. Click Next.
13. The QM application should not require finalization. Click Next.
14. The RM application should detect that the finalization process has
been successfully executed already. Click Next.
15. Same goes for the Finalize Setup
page. Click Next.
16. Click Finish and go to
Jazz Team Server - Server
Administration.
17. Access the Reports tab and verify
that all the ETL jobs from the Data Warehouse
Collection Jobs section have the correct credentials
specified. Check that the Oracle DW info was saved correctly by going
to the Data Warehouse Connection
section.
18. If CCM and QM are installed, access the ccm/admin and qm/admin
interfaces and verify the DW info similar to Step 17.
19. Access jts/admin (Server Administration url) and go to the
Reports tab. Once the jobs are loaded,
click on Run all data warehouse collection jobs for all
applications link. This will trigger a full load into
the DW (because the Oracle DW is new). After all the ETLs finish
successfully (the Star job is the last one to run), the DW should be
fully loaded and ready for reporting.

Good luck!
P

The above scenario can be used for a single initial snapshot. 3.0.1 does not support loading the RM historical data into a new DW.

Migrating the DW data between different db vendors is not supported.