take 1 day to load data ( RTC + Rational Insight)
Hello,
I already integrating between RTC and Insight. I used RTC to fill workitem Template and Ratinal Insight is to display report, the problem is every time i insert new data in workitem it take 1 day to load data in Ratinal insight. Why this happen? Can anyone give suggestin? Please.
Regards
Mohamad Izzuddin
Accepted answer
If you are using 5.0, you can install the Data Collection Component (DCC) to execute faster and more frequent ETL's to refresh your data closer to real time. This table is useful in determining which ETL solution suits you best. Hope it helps,
Comments
1 vote
1 vote
2 votes
2 other answers
Hello Mohamad,
this is the expected behavior.
Insight pulls the data for the reports from the data warehouse; this is populated with the data from the applications like RTC, RQM, etc. when the ETL runs.
Usually you run the ETL once a day, so what you see in the reports is the status of RTC at the time the last ETL was executed.
Best Regards,
Francesco Chiossi
this is the expected behavior.
Insight pulls the data for the reports from the data warehouse; this is populated with the data from the applications like RTC, RQM, etc. when the ETL runs.
Usually you run the ETL once a day, so what you see in the reports is the status of RTC at the time the last ETL was executed.
Best Regards,
Francesco Chiossi
Hello Mohamad,
the CLM ETL job is divided in the following components:
The JFS_ODS, RTC_ODS, RM_ODS and RQM_ODS jobs are populating the part of the data warehouse called operational data store. This is like a snapshot of the current status of the applications at the time the ETL jobs is executed. You can run this 4 jobs multiple times a day if you want the data of the data warehouse be closer to the actual status of RTC. One important consideration is that you need to evaluate how long those jobs take to complete, meaning you should schedule them in a way that the sequential executions doesn't overlap.
The Build_Star job, populate the metrics, that are basically trending and historical information. It's important that this job is run only once a day and after the other four are completed. Reason for not running it more than once a day is that you may incur in anomalous growth of the data warehouse size and reports based on metrics might display incorrect values (for example the original value multiplied by the time the Build_Star run that day). You can find more information on metrics in this article:
Improve the value of your CLM reports by using metrics
http://www.ibm.com/developerworks/rational/library/improve-value-clm-reports-metrics/index.html
Best Regards,
Francesco Chiossi
the CLM ETL job is divided in the following components:
The JFS_ODS, RTC_ODS, RM_ODS and RQM_ODS jobs are populating the part of the data warehouse called operational data store. This is like a snapshot of the current status of the applications at the time the ETL jobs is executed. You can run this 4 jobs multiple times a day if you want the data of the data warehouse be closer to the actual status of RTC. One important consideration is that you need to evaluate how long those jobs take to complete, meaning you should schedule them in a way that the sequential executions doesn't overlap.
The Build_Star job, populate the metrics, that are basically trending and historical information. It's important that this job is run only once a day and after the other four are completed. Reason for not running it more than once a day is that you may incur in anomalous growth of the data warehouse size and reports based on metrics might display incorrect values (for example the original value multiplied by the time the Build_Star run that day). You can find more information on metrics in this article:
Improve the value of your CLM reports by using metrics
http://www.ibm.com/developerworks/rational/library/improve-value-clm-reports-metrics/index.html
Best Regards,
Francesco Chiossi