Have you had problems with your IBM TRIRIGA Installations/Upgrades? If so, you are not alone. The suppport team has experienced a surge in the number of issues revolving around an installation or upgrade. In this blog, I will talk about some best pratices that may help future upgrades to run more smoothly.
First, you will likely find that no 2 installations/upgrades will run the same. Having performed installations of software for a fair amount of my career, I have found that the one constant is that not everything is constant. A problem you run into when installing/upgrading an application in your development environment may not occur when you run the same install/upgrade process in test. Likewise, problems you encounter in test may not occur when you run the same process in production. Be prepared to see this as you perform your installations and accept it for what it is, another chance to learn something new.
Second, always take notes during the installation process. This will vary from person to person, but I find that if I document an issue during my installations in my lower environments, I find that I may be able to determine why the problem occurred and prevent the problem from occurring in my higher environments. As an example, I found that I had corrupt data in an environment that resulted in a failed upgrade. I determined exactly how I could find out if the same corruption occurred in my higher environments and took steps to clean up the corrupted records before I ran through the installation/upgrade process in those environments.
Third, backup both your database and your file server to provide restore points that you can go back to if an installation/upgrade should go too horribly wrong. If nothing else, these backups can provide you with multiple tests of the installation/upgrade process so that you can improve your estimates on how long you might expect the process to take in your higher environments. In one instance, I restored an environment several times and indentified various problems with each upgrade attempt. At the same time, I was able to give a more precise measure of how long it would take to complete an installation/upgrade when it came time to upgrade production. There is nothing worse than having to postpone an upgrade when the user community is expecting the change the following day.
In the spirit of full disclosure I should make it clear that the upgrades I have discussed in this blog entry were not solely a result of my experience with TRIRIGA installations/upgrades. I have seen these same issues with software I have written and installed in my previous jobs as well as other enterprise software for which I was responsible at other companies. Realizing that these issues can happen, regardless of how much control you may have (or think you have) over an environment, should ease your mind when these problems do occur. Also remember, the support team is here to help you achieve a successul instalation/upgrade. If you encounter a problem in the process that you cannot resolve, do not hesitate to involve us when you encounter the problem in your lower environments. Together we can determine a resolution and make your next installation/upgrade a better experience. Who knows, maybe your next installation/upgrade will go off without a hitch.