Upgrade Process Astonishingly Poor

The installation process in Jazz 3.0.1 has improved substantially from prior releases, but the process of upgrading the server from one release to the next is astonishingly poor.

Originally I installed 3.0.1m3. Later I tried to upgrade to 3.0.1 RC and after a week of trying, even with help from experts, I had to abandon my repository and do a clean installation of 3.0.1 RC, then rebuild everything from scratch.

Today I tried upgrading my server from 3.0.1 RC to the final release of 3.0.1, and after 7 hours of trying, I am again ready to pack it in. However, as I now have months worth of real work in my repository, starting from scratch is not an option.

Could someone please tell me if there is any reasonable way to migrate my repository from 3.0.1 RC to 3.0.1 that does not take more than 1 hour.

If I cannot find a way to do this by tomorrow I am just going to move all my work to Perforce and turn my back on Jazz and RTC forever as a waste of time. This will be a shame because I am the only one in my company (Kodak) advocating the use of Jazz, RTC and friends, and we will probably all just move to Jira Studio.
http://www.atlassian.com/hosted/studio/?gclid=COLzk4WtxakCFeoZQgoddBlKMQ

Overall I would have to rate IBM's pre-sales support for Jazz as quite poor. After attending one of the Proof of Technology days I was quite impressed with Jazz, but since I have been trying to evaluate it I have been hugely disappointed at how difficult it is to install and maintain a Jazz environment.

Hi Eric

Sorry you are having such problems on the move from the 3.0.1 RC versions to GA. What (if any) instructions are you following, and what RC are you using RC1/RC2/RC3?

I am pretty sure I have seem info on this - let me see if I can find this (if someone else does not get to you before I find the content).

anthony

Hi Eric

Sorry you are having such problems on the move from the 3.0.1 RC versions to GA. What (if any) instructions are you following, and what RC are you using RC1/RC2/RC3?

I am pretty sure I have seem info on this - let me see if I can find this (if someone else does not get to you before I find the content).

anthony

I am using RC3.

From the IBM Installation Manager when I try to upgrade the server I get

https://lh5.googleusercontent.com/-Z0O64ANN0PA/Tf_RuVScl8I/AAAAAAAAAHA/93D_TyFje3o/JazzServerUpdate.png

When I follow the link I get to http://publib.boulder.ibm.com/infocenter/clmhelp/v3r0m1/index.jsp and from there I cannot find anything clear or useful.

Cheers, Eric

Hi Eric

Sorry you are having such problems on the move from the 3.0.1 RC versions to GA. What (if any) instructions are you following, and what RC are you using RC1/RC2/RC3?

I am pretty sure I have seem info on this - let me see if I can find this (if someone else does not get to you before I find the content).

anthony

I am using RC3.

From the IBM Installation Manager when I try to upgrade the server I get

https://lh5.googleusercontent.com/-Z0O64ANN0PA/Tf_RuVScl8I/AAAAAAAAAHA/93D_TyFje3o/JazzServerUpdate.png

When I follow the link I get to http://publib.boulder.ibm.com/infocenter/clmhelp/v3r0m1/index.jsp and from there I cannot find anything clear or useful.

Cheers, Eric

Hi Eric

OK - I need to confirm the following - but my understanding from the RRC RC to GA upgrade, we installed the GA product in a new group and then pointed the GA product to the old database. I need to confirm this, so bear with me on this.

anthony

I meant to add I have added a documetnation defect for this here:

https://jazz.net/jazz/web/projects/Rational%20Team%20Concert#action=com.ibm.team.workitem.viewWorkItem&id=169359

Please feel free to add your comments to this work item.

anthony

Hi Eric,
I don't think we ever officially supported upgrades from 3.0.1 m to RC,
or upgrades from RC1 to RC2.
In fact, until the product has GA'ed, by using pre-released versions like RC's, you understand you may face difficulties upgrading.

The only officially supported scenario is upgrade from 2.X to 3.0.1 GA.
http://publib.boulder.ibm.com/infocenter/clmhelp/v3r0m1/topic/com.ibm.jazz.install.doc/topics/c_rtc_upgrade_overview.html

This said, this won't help you overcome your issue.

As per the above, I would encourage you to:
1 - current version: repotools -export (JTS/CCM/DW)
2 - uninstall current version
3 - install 3.0.1 GA
4 - repotools -import -export (JTS/CCM/DW)
5 - repotools -addTables -export (JTS/CCM) - just in case model was changed
6 - repotools-ccm -rebuildTextIndices
7 - repotools-ccm -reindex
8 - online verifier tool against JTS and CCM https://jazz.net/wiki/bin/view/Main/OnlineVerifyTool
9 - start your 3.0.1 GA server

Let me know how it goes.
Thanks.

Eric(s), while accurate, those are the most conservative, worst-case steps. I'm optimistic that there is a better path, which we would have used in our self-hosting. If you can be patient for another half-day, we will update you here, hopefully with a much faster and simpler upgrade path.

Thanks,
Scott Rich
Jazz Team

Eric(s), while accurate, those are the most conservative, worst-case steps. I'm optimistic that there is a better path, which we would have used in our self-hosting. If you can be patient for another half-day, we will update you here, hopefully with a much faster and simpler upgrade path.

Thanks,
Scott Rich
Jazz Team

Sigh, I posted a response 6 hours ago, but for some reason Jazz forum server did not record it, so I will try again. Is it just me, or is the Jazz forums server slow for everyone else too?

My goal is to have this all solved by the end of the today, which for me is 11:00 PM PST (Vancouver, Canada) today, so I don't mind waiting. I would greatly appreciate a better solution.

Cheers, Eric

Eric,

I'm going to assume that you are using the out-of-the-box tomcat config with all the apps on 1 server (since I don't see anything here which indicates what your exact config is). Since you are planning to use it for production I'm also assuming you are using a db other than derby (if you are still using derby i can provide steps for that as well but it would likely not be a recommended config for production). I'm also going to assume windows here but the changes to the steps should be trivial if you are on linux.

There are essentially 3 things that need done to go from 3.0.1 RC3->GA. It depends a bit on the size of your db but assuming it is small at this point, I don't see any reason this couldn't be completed in under an hour.

1. Install the GA bits into a new location on the system
   
2. Merge/copy the application and tomcat config files from your existing RC3 deployment to the GA location (this is automated somewhat)
   
3. Run repotools -addTables on the databases (this may, in fact, be a noop in many cases but it is safest to do it).
   

Here is a more detailed breakdown of the commands:

1. Backup your databases and stop the RC3 server
   
2. Install the GA bits into a new location on the system
   
3. Go to the server directory of the GA installation
   
4. Merge/Copy config files
   
   
   
   1. Run repotools-jts.bat -migration_jts_updateConfigurationFiles oldJTSHome=3.0.1RC3_install_dir/server/conf
      
   2. Copy the file 3.0.1_RC3_install_dir/server/conf/qm/teamserver.properties to 3.0.1_install_dir/server/conf/qm
      
   3. Copy the file 3.0.1_RC3_install_dir/server/conf/rm/fronting.properties to 3.0.1_install_dir/server/conf/rm
      
   4. Copy the file 3.0.1_RC3_install_dir/server/conf/rm/friendsconfig.rdf to 3.0.1_install_dir/server/conf/rm
      
   5. Copy the file 3.0.1_RC3_install_dir/server/conf/ccm/teamserver.properties to 3.0.1_install_dir/server/conf/ccm
      

(substituting your directory for 3.0.1_RC3_install_dir and 3.0.1_install_dir)

Run addTables on the databases

1. Run repotools-jts.bat -addTables
   
2. Run repotools-qm.bat -addTables
   
3. Run repotools-ccm.bat -addTables
   

Start the 3.0.1 server

If you were still using trial licenses, you may need to activate the 3.0.1 trials. Just go to <server>/jts/admin and go to the license key management page and click the activate trial links as needed.

Note that the error you showed in one of your earlier posts is due to the fact that we don't support update-in-place of the server. Instead you need to do a side-by-side install and upgrade. This has the advantage that if you backup your dbs and anything goes wrong you can quickly/easily just restore the dbs and revert to the original deploy until any issue can be worked out.

Also, as noted, upgrading from a milestone to GA is generally not a supported scenario. This is the reason the steps are a bit more manual and that the information in the help topic that was linked from the installation manager does not contain sections for 3.0.1 milestones -> 3.0.1.

Hope this helps and please let us know if you have any other questions or if your config is a bit different and you need clarification.

@jstuckey

I am using the out-of-the box tomcat config as installed by the Jazz server installer. I am also using Derby, as this started as a trial evaluation. While I am now using it in a production situation now, it is limited use as I am currently the only user. My ultimate goal was to show the rest of our team how Jazz worked with a real product in a real situation to be able to showcase the merits of Jazz RTC and friends.

I would appreciate the Derby steps if you have them.

I am indeed using Windows 7 Professional x64 as my server.

I have both 3.0.1 RC3 and GA installed and running and can start either server. I just cannot figure out how to move the database from RC3 to GA.

I tried using the scripts used to upgrade 3.0.0 to 3.0.1, and that gave me the same configuration on GA as RC3, but not the database.

Cheers, Eric

Eric,

If you are using derby the simplest thing to do is remove or rename the 'derby' folder under GA_install_dir/server/conf/ccm,qm,jts (this is the empty derby db from that install so you don't need it) and copy the derby folder under the RC3_install_dir/server/conf/ccm,qm,jts directories to the corresponding location in the GA install directory.

After you have done this you will want to run the 'addTables' commands I listed in my previous response.