[1.0.1 upgrade] Smooth upgrade using Installation Manager
Hi
Very smooth upgrade! Great work by the folks in development.
I upgraded my 1.0 installation today, all worked fine. I am running 1.0 on Windows XP, with a client and server on the same machine. App server is Tomcat, database is DB2. I have local admin rights on my machine.
I made sure the server was shut down and used the installation manager to do an upgrade to the server, then upgraded the client and then the build toolkit. The installation manager did a good job of creating backup copies of the relevant config files.
I had to copy the teamserver.properties file from the backup created by the installation manager to keep my DB2 settings, and (because I am using tomcat authentication), the tomcat-users.xml file from the backup.
I also reimported the licenses (the *server* license and then the CAL). This confused me for a minute (I did the CAL but forgot to do the server license).
anthony
Very smooth upgrade! Great work by the folks in development.
I upgraded my 1.0 installation today, all worked fine. I am running 1.0 on Windows XP, with a client and server on the same machine. App server is Tomcat, database is DB2. I have local admin rights on my machine.
I made sure the server was shut down and used the installation manager to do an upgrade to the server, then upgraded the client and then the build toolkit. The installation manager did a good job of creating backup copies of the relevant config files.
I had to copy the teamserver.properties file from the backup created by the installation manager to keep my DB2 settings, and (because I am using tomcat authentication), the tomcat-users.xml file from the backup.
I also reimported the licenses (the *server* license and then the CAL). This confused me for a minute (I did the CAL but forgot to do the server license).
anthony
3 answers
I concur Anthony. Kudos to the development team.
I was puzzled about where to put web.xml until I figured out I had to restart Tomcat to cause the server to recreate directories .\jazz and .\jazz\WEB-INF before replacing the default web.xml. Other than that, the out-of-box experience was great.
I was puzzled about where to put web.xml until I figured out I had to restart Tomcat to cause the server to recreate directories .\jazz and .\jazz\WEB-INF before replacing the default web.xml. Other than that, the out-of-box experience was great.
Hello Sims,
I agree that it was really a smooth upgrade. I took the naive approach -
just update without carefully reading the documents provided......
However I noticed some strange things that might be connected to my setup.
I have a special setup for demos that recreates DB and workspaces for demo
purposes.
After upgrading I had a hard time with my workspaces. For some obscure reason
some would not work - Eclipse crashed in the load screen.
Strangely I managed to open one or two different workspaces but the third
would not open.
I was able to fix that deleting config data stored in the workspaces.
I also notice that once I managed opening the workspaces the IM integration
to OpenFire (older version from May) would not work anymore.
RTC believed to be connected but did not show green on the status.
After installing a newer version of Openfire, that effect was gone.
Ralph
I concur Anthony. Kudos to the development team.
I was puzzled about where to put web.xml until I figured out I had to
restart Tomcat to cause the server to recreate directories .\jazz and
\jazz\WEB-INF before replacing the default web.xml. Other than that,
the out-of-box experience was great.
I agree that it was really a smooth upgrade. I took the naive approach -
just update without carefully reading the documents provided......
However I noticed some strange things that might be connected to my setup.
I have a special setup for demos that recreates DB and workspaces for demo
purposes.
After upgrading I had a hard time with my workspaces. For some obscure reason
some would not work - Eclipse crashed in the load screen.
Strangely I managed to open one or two different workspaces but the third
would not open.
I was able to fix that deleting config data stored in the workspaces.
I also notice that once I managed opening the workspaces the IM integration
to OpenFire (older version from May) would not work anymore.
RTC believed to be connected but did not show green on the status.
After installing a newer version of Openfire, that effect was gone.
Ralph