Taking backups are essential if you are upgrading to the new version of Rational Insight because after you upgrade to version 1.0.0.1, you cannot roll back your installation to version 1.0.
The fix pack is deployed through IBM Installation Manager. If a new version of Installation Manager is available, you must install it before you upgrade Rational Insight.
After you have upgraded to the new version, you must restore the custom settings that were made to the artifacts of the previous version. These might include the following: changes made to the IBM Cognos® connection, XML data configuration files, Rational Insight skin, and, if you are using Rational Insight Data Services, the servlet parameter settings for the data service.
You might also need to restore the changes you made to the metadata of your Framework Manager projects and the extract, transform, and load (ETL) catalog. The updated versions of the jobs and builds of version 1.0 are all contained in a new job in the same folder as version 1.0. This new job has the same name as the original job, with Update appended to its name, and is in itself not executable; it contains all builds updated in the new version and can be used for exporting as a package and importing into the ETL catalog.
To migrate your data warehouse, you must run an automated script that is placed on your file system during the installation process.
The data warehouse of version 1.0.0.1 of Rational Insight has new version of the reporting data model. If you are using Rational Insight data warehouse as a data source, you must import this model to the Framework Manager project.
Version 1.0.0.1 of Rational Insight has support for Rational Quality Manager 1.0.1.1 and Rational Quality Manager 2.0. If you are using either of these two versions of Rational Quality Manager as a data source, you must update the metadata models for these data sources.
Version 1.0.0.1 of Rational Insight of Rational Insight has a new content store. If you have customized your reports, do not upgrade the content store to the new version. Instead, continue using your old content store and import the new report package into your existing content store.