You know the drill: IBM announces a new version of their Business Intelligence tool, Cognos. You search the Cognos Blog-o-sphere and attend sneak-preview sessions for information on the newest release. It’s so shiny! Your reports will be so much happier in the latest and greatest Cognos version! But your excitement slowly slips away and is replaced by a nagging feeling in the back of your mind. Upgrading to the newest version of Cognos takes a lot of time, planning, and work.
There are so many circumstances that can affect how smoothly your upgrade goes. In a survey of over 100 cross-industry Cognos users, 37.1% said that managing the Cognos migration was their biggest challenge.
Project managers try to lower the level of uncertainty by designing project plans, which outline goals, budget, and deadlines. But they can’t totally eliminate the unknowns. And no amount of budget and time planning can prepare you to estimate the additional costs of unknown factors.
In the same survey, 31.4% of Cognos users admitted that automating the testing and validation was their biggest challenge of a Cognos upgrade. How do you ensure that your production content is working after the upgrade? Well, that requires ensuring your production content is working before the upgrade, and identifying what is not currently working. This is where testing before, during, and after the upgrade is necessary. But how do you gain complete visibility into content functionality and quality? And how do you automate the testing process? Okay, so maybe you don’t upgrade to the latest version of Cognos after all. Maybe you give up the promised new features for the comfortable existing ones.
But you know that technology is always evolving and improving. Staying stagnant will give your competitor the edge. You can’t have that!
Instead of fretting, try our 5 step methodology that includes using MotioCI software. This methodology is designed to help you set realistic expectations on how to plan, execute, and manage the upgrade process while MotioCI automates the painful tasks involved in upgrades. Read our Improving IBM Cognos Upgrades White Paper (found in our Cognos Upgrade Resource List below) to learn the more in-depth attributes of each step.
Assess Your Current Production Environment
The white paper begins with the importance of preparing and assessing your environment. Start off by determining what, specifically, you’d like to move. Think of the Cognos upgrade like moving to a new house. Toss out the junk you aren’t using (e.g. reports not used in over a year) and that broken lamp that is just not worth fixing (e.g. Cognos reports that no longer run.) And why would you move all 5 hammers when you only need one? (e.g. why move duplicate reports?)
Having a clutter-free Cognos content store can help you better predict the timeline for the upgrade process. In this first step, you will determine what you should move vs. what is clutter in your production environment. Now does getting to the latest version of Cognos already seem more manageable?
Setup for Scoping
Your next step is to version all objects in Production with MotioCI. Freezing production is ideal, but in some cases it is just not possible. With MotioCI in place, you have added protection with a “safety net” of your content so you can roll back to previous versions if need be.
You will then connect MotioCI to a sandbox and copy production here. The white paper goes into more detail about the importance of using a sandbox that I won’t go into in this blog. You will use MotioCI to create an initial version of your production content in the sandbox and then setup and run test cases. This gives you a baseline of your production environment. You’ll run stability, output, and data validity tests, to know the state of your assets. The results of these tests will identify what needs further assessment.
Determine the Impact of Your Upgrade
Once you have your first round of test results, this will help you establish what is in scope, out of scope, needs further attention, etc. This is where you gain control over your project’s timelines and the amount of work involved in your upgrade. You’ll label your assets as:
- Out of scope content
- Ready to upgrade- no issues detected
- Broken, model change required
- And so on.
And yes, you guessed it! The white paper goes into greater detail on this step.
After you run the sandbox upgrade, run your test cases again so MotioCI can capture the results of the upgrade immediately.
This phase is where you will save a great deal of time and money on testing. You will utilize the automated testing available in MotioCI to test/repair/test/repair all of your assets until they are either out of scope or ready to upgrade.
It’s important to repair any problems MotioCI may have identified while upgrading to the new version of Cognos. Instead of the guess & check method (“let me fix the issue, did it work? No. Does changing that work? Still no.”) MotioCI’s reporting feature is very valuable in gauging the number of failing or passing test cases over time, so that you can easily monitor their progress.
Upgrade and Go Live
The final step is to execute a secured “go live.” This usually happens during off business hours. Copy the MotioCI test cases from the sandbox to the live environment, and ensure that a backup of the content store has been made. You will save some additional time by using MotioCI’s deployment capabilities to easily move the “Repaired” label content from your Sandbox to Live environments. You will also rerun the test cases here, assess the results and determine when to go live.
So, maybe the upgrade process just requires a different, more agile approach to be successful. It requires a thoughtful, but not daunting, process to ensure that your Cognos upgrades are planned and executed more efficiently. Utilize MotioCI in the process from start to finish. MotioCI will help you:
- Plan the appropriate scope to determine workload
- Assess the impact of the upgrade
- Repair problems and ensure they stay repaired
- Execute a secure “go live”