I just migrated our HA-enabled 2.0.0.2iFix4 RTC test infrastructure to RTC 3.0iFix1.

As this is not documented anywhere so I had lots of fun to get it work and would like share my findings with you so you don't have to go through it again.

The test infrastructure is composed of a front-end IBM HTTP web server, primary RTC server and standby RTC server, and DB2 server.

The key and also trouble-maker during this migration is the public uri root value, which is set to point to the front-end web server on both primary and standby RTC server in our case.

1. You want to shut down both primary and standby servers and start with the primary server as the migration will modify the repository database;

2. The migration is not a normal upgrading to 3.0 from your 2.0 instance. You actually need to uninstall the 2.x RTC server and then install a new 3.0 one. So all HA related configuration is lost. One needs to review all HA configurations did with the 2.x servers and re-apply them again on the 3.0 instance; and you need to do it for both the jts and the jazz applications;

3. For the new introduced jts application, the web plugin configuration on the front-end web server needs to be modified to route request to it by adding a new entry for /jts. Otherwise, you won't be able to run jts server setup wizard at the end of your migration.

4. After the primary server is migrated to 3.0, shut it down and reconfigure web plugin to run a failover to the standby server and then start the stanby server to run migration.

5. Run configuration files migration from 2.x to 3.0 on the standby server, but Don't run the database migration again on the standby server as it shares the same ones with the primary one;

6. Don't use the teamserver.properties merged by the configuration file migration scripts for both jts and jazz on the standby server. Copy ones from the primary server and reconfigure them for backup server HA. Otherwise, you'll never pass the jts server setup wizard;