RTC V4 Migration Plan
We are having RTC V3.0.1 currently running in our production server.
Now we are planning to upgrade it to RTC V4. We want RTC V3 should be running and create a separate instance for V4 on the same hardware. Is there any way to populate V3 DB data to V4 DB? We want to test V4 instance before shutting down V3 as it is production environment. Problem is we don't have any staging/testing environment. So we don't want to touch V3 instance during upgrade. Please suggest immediately. |
2 answers
Ralph Schoon (62.0k●3●36●43)
| answered Dec 11 '12, 6:04 a.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER edited Dec 11 '12, 6:07 a.m.
In general it is suggested to have a test environment to test upgrades. For 4.0.1 this help entry talks about some more details http://pic.dhe.ibm.com/infocenter/clmhelp/v4r0m1/topic/com.ibm.jazz.install.doc/topics/c_upgrade_staging_env.html
The Test environment needs to be using the same names used in the public URI and thus needs to be isolated from the production environment. You basically use network techniques such as host entries or unplugging the networs or virtualization to separate them. It is essential that they can not see each other and you can't hook up artifacts of one with the other. Testing the upgrade is a good way to make sure everything works afterwards and also to answer questions like will the dashboards stay available. The answer to the latter is, you should see exactly the data you saw before migrating. No data should be lost. While upgrading the data in the database is adjusted to the new schema. The upgrade process and other details is described in the online help - you should use the interactive upgrade guide to create individual upgrade guides. https://jazz.net/library/#tag=upgrading shows a whole host of other information you can tap into. Comments I forgot to mention that it is not possible and not supported to change the public URI when going to 4.x. So you can't run the old and the new version in parallel in the same network.
|