Upgrading IBM Cognos Analytics: A Large-Scale Bank Migration Success Story
Upgrading IBM Cognos Analytics in a large financial organisation is about far more than installing a new version of the software. When the platform supports thousands of users, thousands of reports and business-critical integrations, the upgrade becomes a major technology migration – one that needs to be carefully planned, tested and executed with minimal disruption.
We successfully delivered a large-scale Cognos Analytics upgrade for a major banking organisation, migrating from IBM Cognos 10.2 to Cognos Analytics 11.1.7 across a multi-environment estate.
The project involved approximately 3,000 users, 2,400 reports and multiple bespoke applications, requiring a structured approach to infrastructure, application compatibility, testing and migration.
The Challenge
The bank’s existing Cognos 10.2 platform was a mature and heavily integrated reporting environment. It supported:
- Approximately 3,000 users
- Around 2,400 reports
- Multiple Cognos environments
- Bespoke Java applications using the Cognos SDK
- Enterprise scheduling and integration processes
- Business-critical reporting across the organisation
The challenge was to introduce the new platform while ensuring that existing reports, integrations, applications and user functionality continued to work as expected. With thousands of reports, traditional manual regression testing would have been extremely time-consuming and would have provided limited confidence across the entire estate.
Building The New Platform
Rather than upgrading the existing servers in place, we established new virtual machine infrastructure for Cognos 11.1.7. This provided a clean and controlled target environment for the migration.
The approach also reduced the risk associated with making significant changes directly to the existing production platform. The legacy Cognos environment could remain available while the new platform was built, configured and tested.
A Phased Migration Strategy
The upgrade was delivered progressively across the different environments, with the migration beginning with the sandbox and test environments, allowing the team to identify issues early and refine the migration process before moving towards the more critical environments.
The phased approach provided several advantages:
- Early identification of compatibility issues
- Validation of the new infrastructure
- Opportunity to refine deployment processes
- Early testing of reports and applications
- Reduced risk when moving towards production
- Greater confidence for business stakeholders
Each environment provided another opportunity to validate the platform before progressing to the next stage.
Automated Regression Testing
One of the most important components of the project was the use of Cognos Lifecycle Manager for automated regression testing. With approximately 2,400 reports, manually running and comparing reports before and after the upgrade would have been impractical.
Lifecycle Manager provided a way to systematically compare report results between the existing Cognos 10.2 environment and the new Cognos 11.1.7 platform. This allowed the team to identify potential differences and focus investigation on reports where the upgrade had introduced a change.
Automated regression testing significantly increased confidence in the migration and helped turn what could have been a largely manual testing exercise into a structured, repeatable process.
The Cognos SDK Challenge
The upgrade was not limited to Cognos reports. The bank also had bespoke Java applications that used the Cognos SDK. These applications represented an important dependency because changes between Cognos versions could affect SDK functionality and application behaviour.
As part of the upgrade, these bespoke Java applications were reviewed and upgraded to work with the new Cognos 11.1.7 platform.
A Cognos upgrade can appear successful from the perspective of the standard Cognos interface while still breaking applications that interact with the platform programmatically. By treating the SDK-based applications as part of the migration rather than an afterthought, we were able to validate the wider Cognos ecosystem.
Testing Beyond The Reports
The testing strategy therefore covered much more than report output. Validation included:
- Report execution
- Report output comparisons
- Scheduled reports
- User access and security
- Data source connectivity
- Cognos configuration
- SDK-based Java applications
- Integration points
- Business-critical reporting processes
The combination of automated regression testing and targeted functional testing provided broad coverage while allowing specialist effort to be focused on areas where differences or compatibility issues were identified.
Production Migration
By the time the project reached the production environments, the migration process had already been proven through the earlier sandbox and test environments. The team had:
- Built and validated the new VM infrastructure
- Refined the Cognos migration process
- Tested approximately 2,400 reports
- Used CLM for automated regression testing
- Upgraded bespoke Java applications using the Cognos SDK
- Validated integrations and critical functionality
- Progressively migrated and tested the environments
This meant the production migration was not an unknown event. It was the final stage of a process that had already been tested and refined.
The outcome
The bank successfully migrated from Cognos 10.2 to Cognos Analytics 11.1.7 across its Cognos estate and the project delivered:
- Cognos 10.2 → Cognos Analytics 11.1.7
- Approximately 3,000 users
- Approximately 2,400 reports
- New VM infrastructure for the upgraded platform
- A phased migration across environments
- Automated regression testing using Cognos Lifecycle Manager
- Upgraded bespoke Java applications using the Cognos SDK
- Comprehensive validation of reports, integrations and applications
- A controlled transition into the production environment
What Made The Project Successful?
The key to the project was treating the Cognos upgrade as an end-to-end platform migration, rather than simply a software upgrade. Three principles were particularly important.
Start small, then scale
Beginning with sandbox and test environments provided a safe place to identify problems and refine the approach. By the time production was reached, the migration process was well understood.
Automate regression testing
At 2,400 reports, manual testing alone would have been inefficient and difficult to repeat. Using Cognos Lifecycle Manager provided a scalable approach to regression testing and gave the project greater confidence in the upgraded platform.
Don’t forget what’s outside Cognos
The Cognos platform rarely operates in isolation. Bespoke applications, SDK integrations, scheduling systems, data sources and downstream processes can all be affected by an upgrade. Including these components in the migration scope was essential to delivering a successful outcome.
The Bigger Lesson
Large-scale Cognos upgrades are ultimately about reducing uncertainty. You cannot eliminate every risk from a major platform migration, but you can progressively reduce it through good architecture, phased implementation, automation and comprehensive testing.
For this bank, the combination of new infrastructure, a phased migration strategy, automated regression testing and application remediation provided a controlled route from Cognos 10.2 to Cognos 11.1.7.
The result was not simply a newer version of Cognos. It was a modernised and validated analytics platform capable of supporting approximately 3,000 users and 2,400 reports, with the wider application ecosystem upgraded alongside it.
Planning An IBM Cognos Analytics Upgrade?
We help organisations assess, plan and deliver complex Cognos upgrades and migrations – from individual environments to large enterprise estates.
Talk to us about your Cognos environment and how we can help you plan your next upgrade.