RTC ugrade/migration
3 answers
Hi,
4 to 6 isn't possible afaik, you'll have to go 4 -> 5 -> 6.
In general I would avoid to many steps in one "migration" to get the risk and complexity as low as possible.
I would go the following way:
Upgrade to 5 on the old hardware
Switch to new hardware, where WAS 8.5 with RTC 5 is installed
Upgrade to 6 in the new environment
DB2 upgrade whenever possible or needed
If you're using Data Warehouse at the moment, you'll have to switch to Data Collection Component to get to 6.
If you are using SCM, one of the 5.0.x upgrades introduced version numbers, which are calculated in the upgrade process. In our environment this took around two hours. Should be depending on the amount of files and versions.
greetings georg.
Comments
Hi Georg,
Assuming you are using a DNS alias, pointing to your old hardware:
- install the applications on the new hardware, RTC in the same version as on the old server
- shutdown the services on the old hardware
- switch the DNS alias to the new hardware
- run server.net/jts/setup to configure the new system to use the existing databases and to doublecheck other settings
Also make yourself familiar with backup: https://jazz.net/wiki/bin/view/Deployment/BackupCLM because it explains the files you need to know if you want to change to another machine.
Great!
You want to really read up on the Deployment Wiki. For example, you want to understand the recommended Standard Topologies https://jazz.net/wiki/bin/view/Deployment/StandardTopologiesOverview and how to distribute the applications if you want to go to 6.0.x. Even if you only have RTC, you want to consider the changes to reporting. (RB/DCC)