Best practice for upgrading to RTC 3?
Talking to a customer about planning a large scale upgrade of RTC 2 to 3, I wanted to see if my suggestion matches others best practices. Because the 2.x and 3.x client and server are not compatible, we need an upgrade plan that gets all the new clients online as soon as possible after the server upgrade. Here's what I've proposed:
1. Have users install the RTC 3 Eclipse client as an additional Eclipse shell on their desktops. Do not uninstall RTC 2 first, or attempt to upgrade it via P2, etc. If you're working with more than one server, you'll need the 2.0 client for a while anyway.
2. Install and configure the RTC 3 server. If this is Tomcat, it can be installed alongside the existing server. For WAS, you can at least get the bytes in place on the server before upgrading.
3. Take the server down for upgrade.
4. Backup!
5. Upgrade the database with repotools -addTables.
6. Activate the new server bytes by starting the new Tomcat or updating the WAS config.
7. Sanity check server functionality before advertising availability.
8. Server opens for business.
9. Users come in the next morning and start their RTC 3 clients, opening their existing RTC workspaces. (If you have projects loaded from servers which are still running 2.0, you'll need to create a new workspace.) The client should connect to the RTC 3 server and be usable immediately.
Anything I missed here? Any issues with the client upgrade strategy?
Thanks,
Scott
IBM Rational
1. Have users install the RTC 3 Eclipse client as an additional Eclipse shell on their desktops. Do not uninstall RTC 2 first, or attempt to upgrade it via P2, etc. If you're working with more than one server, you'll need the 2.0 client for a while anyway.
2. Install and configure the RTC 3 server. If this is Tomcat, it can be installed alongside the existing server. For WAS, you can at least get the bytes in place on the server before upgrading.
3. Take the server down for upgrade.
4. Backup!
5. Upgrade the database with repotools -addTables.
6. Activate the new server bytes by starting the new Tomcat or updating the WAS config.
7. Sanity check server functionality before advertising availability.
8. Server opens for business.
9. Users come in the next morning and start their RTC 3 clients, opening their existing RTC workspaces. (If you have projects loaded from servers which are still running 2.0, you'll need to create a new workspace.) The client should connect to the RTC 3 server and be usable immediately.
Anything I missed here? Any issues with the client upgrade strategy?
Thanks,
Scott
IBM Rational