| Table of Contents | ||||
|---|---|---|---|---|
|
...
You can also watch a YouTube video of new features: .Coming Soon
Cognos developer report testing at the beginning of the upgrade is critical to a timely and successful upgrade.
...
Cognos Sandbox = Now thru 5:00 PM, Friday, January 10: ITS-BIA will review the upgrade in our sandbox prior to planning an upgrade of DEV. The 12.0.4 upgrade has already been installed on our sandbox.
BONUS: Monday, January 6 thru 5:00 PM, Friday, January 10: Cognos Developers will be allowed into the Cognos Sandbox for a preview
Cognos DEV = 5:00 PM on Friday, January 10:
A backup of the DEV content store will be conducted. This will be insurance against any unforeseen issue during the upgrade process.
The admin team will perform the upgrade of the DEV environment.
Cognos DEV will be unavailable while this work occurs.
Cogno DEV = Post DEV upgrade Friday, January 10 thru 5:00 PM Friday, January 24:
All development teams to review content in Cognos DEV for two weeks and test for issues related to the upgrade.
Any issues are to be reported by sending an email tobusintel@ucsd.edu
If an issue is deemed critical, a rollback of DEV to the current version will be scheduled as soon as possible.
NO MIGRATIONS OUT OF DEV can occur as the content from the upgraded environment will not work in environments on an earlier version.
Cognos DEV = Friday, January 24
GO/ROLLBACK determination for QA upgrade will be made.
GO – the upgrade is applied to QA only over the weekend following the DEV upgrade.
This will be the determination if no new issue(s) are found in the upgraded version or if any new issue noted is deemed insignificant enough to move forward.
ROLLBACK – the upgrade is rolled back from DEV
This will be the determination only if new issues are found in the upgraded version and those issues are deemed significant.
Cognos QA = 5:00 PM on Friday, January 24 (based on GO determination in previous step):
A backup of the QA content store will be conducted. This will be insurance against any unforeseen issue during the upgrade process.
The admin team will perform the upgrade of the QA environment.
Cognos QA will not be available while this work occurs.
Cognos QA = Post QA upgrade Friday, January 24 thru 5:00 PM Friday, January 31:
All development teams to review content in Cognos QA and work with end users to test for issues related to the upgrade.
Any issues are to be reported by sending an email to busintel@ucsd.edu
If an issue is deemed critical, a rollback of QA and DEV to the current version will be scheduled as soon as possible.
NO MIGRATIONS TO PROD can occur as the content from the upgraded environment will not work in environments on an earlier version. Content may be migrated from DEV to QA.
Cognos QA = Friday, January 31
GO/ROLLBACK determination for PROD upgrade will be made.
GO – the upgrade is applied to PROD over the weekend following the QA upgrade.
This will be the determination if no new issue(s) are found in the upgraded version or if any new issue noted is deemed insignificant enough to move forward.
ROLLBACK – the upgrade is rolled back from DEV and QA.
This will be the determination only if new issues are found in the upgraded version and those issues are deemed significant.
Cognos Prod = 5:00 PM on Friday, January 31 (based on GO determination in previous step):
A backup of the PROD content store will be conducted. This will be insurance against any unforeseen issue during the upgrade process.
The admin team will perform the upgrade of the PROD environment.
Cognos Prod will not be available while this work occurs.
...