The dimensions in Rational Team Concert snapshots are loaded into the tables of the operational data store in Rational® Insight data warehouse. The dimensions are loaded into data mart in Rational Insight data warehouse with the common dimension builds in the sample ETL catalog later. For facts in Rational Team Concert snapshots, if the data is aggregated, it is loaded directly into fact tables in data mart in the data warehouse; if the data is actually detailed data, it is loaded into operational data store area in the data warehouse.
The Rational Team ConcertE2E job includes builds to load data into operational data store and builds to load data into facts directly. But if you want to use Rational Team Concert data in common metrics related with request change history data for example request creation date metrics and request aging, you need to run the BuildStar job after running the Rational Team ConcertE2E job. Because the data is taken directly from the database and the XML ODBC driver is not used, the data source GUID has to be specified in the Rational Team ConcertE2E job (in the RESOURCEGROUP_ID variable).
If you are using Oracle as database for the Rational Team Concert repository, the value of the User variable in the Rational Team ConcertE2E job should be specified as the name of the JAZZDBUSER used for creating the Rational Team Concert repository database.