Linux Server Upgrade from ifix5 to ifix7a (2.0.0.2)
I need to upgrade our 64 bit Linux server from RTC 2.0.0.2 ifix5 to ifix7. I am accessing the server using Putty with an admin account. We previously used the zip install (installed by someone else), so I downloaded:
RTC-Standard-Server-2.0.0.2iFix7a-Trial-Linux64.zip
Questions:
1. It says "trial" - can I ignore that or is this the wrong file?
2. The instructions that come with it are for the Express-C edition even though the file clearly says Standard. Also there are no instructions for upgrading from one ifix to another, only for upgrading to a newer version of RTC (such as 1.x to 2.x). What are the instructions for upgrading the server from one ifix to another with the same 2.0.0.2 Standard Edition of RTC?
RTC-Standard-Server-2.0.0.2iFix7a-Trial-Linux64.zip
Questions:
1. It says "trial" - can I ignore that or is this the wrong file?
2. The instructions that come with it are for the Express-C edition even though the file clearly says Standard. Also there are no instructions for upgrading from one ifix to another, only for upgrading to a newer version of RTC (such as 1.x to 2.x). What are the instructions for upgrading the server from one ifix to another with the same 2.0.0.2 Standard Edition of RTC?
15 answers
Hi,
please follow the upgrade instructions on the download page for your fixpack: https://jazz.net/downloads/rational-team-concert/releases/2.0.0.2?p=upgrading
The package you download can be activated using a permanent license as noted in the upgrade instructions.
Would you mind telling me which section? There is no section in those instructions for upgrading from one ifix to another on the same version (2.0.0.2) of RTC. I recommend adding a section for that.
Mike,
"You can upgrade directly to the 2.0.0.2 release of Rational Team Concert from the previous releases. A database migration is required for 1.x to 2.x updates."
So in your case there is no need for a repository migration.
If you install from a zip file you have to install it in a different folder. Or you back up the required configuration files. Then you follow: "Copying the required configuration files from a previous server installation".
You could create a work item for your suggestion.
"You can upgrade directly to the 2.0.0.2 release of Rational Team Concert from the previous releases. A database migration is required for 1.x to 2.x updates."
So in your case there is no need for a repository migration.
If you install from a zip file you have to install it in a different folder. Or you back up the required configuration files. Then you follow: "Copying the required configuration files from a previous server installation".
You could create a work item for your suggestion.
Release Notes are not helping me. Isn't there a list of commands to run to get this installed? Here is what I tried and it did not work:
first I unzipped RTC-Standard-Server-2.0.0.2iFix7a-Trial-Linux64.zip to /opt/app/jazz/install/rtc7azip
then:
I can connect to the tomcat server, but not the repository. Can someone please post corrections to this? I am not a Unix guru. The gurus are extremely busy making our product work, so I have the task of getting this update working on the test server.
Note that I can restore from the tar backup and everything works again, so I know the backup is good.
first I unzipped RTC-Standard-Server-2.0.0.2iFix7a-Trial-Linux64.zip to /opt/app/jazz/install/rtc7azip
then:
cd /opt/app/jazz
server/server.shutdown
Removed existing files (from jazz folder):
rm -r /opt/app/jazz/server
rm -r /opt/app/jazz/repotools
Copied all files from zip folder:
cp -rpf /opt/app/jazz/install/rtc7azip/* /opt/app/jazz
copied needed files from backup (from jazz folder):
tar --overwrite --same-owner -xpf backup/backup-2011-10-31.tar server/conf
tar --overwrite --same-owner -xpf backup/backup-2011-10-31.tar server/repositoryDB
tar --overwrite --same-owner -xpf backup/backup-2011-10-31.tar server/workitemindex
server/server.startup
I can connect to the tomcat server, but not the repository. Can someone please post corrections to this? I am not a Unix guru. The gurus are extremely busy making our product work, so I have the task of getting this update working on the test server.
Note that I can restore from the tar backup and everything works again, so I know the backup is good.
Hi,
have you followed https://jazz.net/downloads/rational-team-concert/releases/2.0.0.2?p=upgrading as suggested?
<<<<<<quote>
Upgrading a Server from 1.0, 1.0.1, 1.0.1.1, 2.0, or 2.0.0.1
You can upgrade directly to the 2.0.0.2 release of Rational Team Concert from the previous releases. A database migration is required for 1.x to 2.x updates. For information on performing a database migration, see Migrating Jazz repository after upgrading Jazz Team Server.
Note: Before you begin upgrading a WebSphere Application Server, reset the server by navigating to https://{servername}:9443/jazz/admin#action=com.ibm.team.repository.admin.serverReset and clicking Request Server Reset.
If you installed the previous release from a zip file, then there is no intersection with the previous install. You can install the 2.0.0.2 release from a zip in a new location, or you can use the IBM Installation Manager to install an instance of 2.0.0.2.
If you used IBM Installation Manager to install the previous release, you can either install 2.0.0.2 as a separate instance or update the previous instance to 2.0.0.2. If you install a separate instance of the server for the 2.0.0.2 release, select Create a new package group on the Install Packages page of the installation wizard.
Note: To upgrade a WebSphere Application Server deployment of the Jazz Team Server, remove the previous jazz.war file and deploy the 2.0.0.2 jazz.war file.
To complete the upgrade, see Copying the required configuration files from a previous server installation and Installing 2.0.0.2 Activation Keys.
<<<quote>>>
There are links in the section of the page for the details.
So what you do is
- Install the product
- Copy the required data of the configuration files over. This includes information such as the DB to connect to.
- Shutdown the old server
- Start the new server
have you followed https://jazz.net/downloads/rational-team-concert/releases/2.0.0.2?p=upgrading as suggested?
<<<<<<quote>
Upgrading a Server from 1.0, 1.0.1, 1.0.1.1, 2.0, or 2.0.0.1
You can upgrade directly to the 2.0.0.2 release of Rational Team Concert from the previous releases. A database migration is required for 1.x to 2.x updates. For information on performing a database migration, see Migrating Jazz repository after upgrading Jazz Team Server.
Note: Before you begin upgrading a WebSphere Application Server, reset the server by navigating to https://{servername}:9443/jazz/admin#action=com.ibm.team.repository.admin.serverReset and clicking Request Server Reset.
If you installed the previous release from a zip file, then there is no intersection with the previous install. You can install the 2.0.0.2 release from a zip in a new location, or you can use the IBM Installation Manager to install an instance of 2.0.0.2.
If you used IBM Installation Manager to install the previous release, you can either install 2.0.0.2 as a separate instance or update the previous instance to 2.0.0.2. If you install a separate instance of the server for the 2.0.0.2 release, select Create a new package group on the Install Packages page of the installation wizard.
Note: To upgrade a WebSphere Application Server deployment of the Jazz Team Server, remove the previous jazz.war file and deploy the 2.0.0.2 jazz.war file.
To complete the upgrade, see Copying the required configuration files from a previous server installation and Installing 2.0.0.2 Activation Keys.
<<<quote>>>
There are links in the section of the page for the details.
So what you do is
- Install the product
- Copy the required data of the configuration files over. This includes information such as the DB to connect to.
- Shutdown the old server
- Start the new server
Yes, I did, what little info there was. There are no instructions for your first step - "install the product" - so I had to guess on that part. The info on config files was there, but a tad convoluted. Not sure I covered all the necessary files. Can you take a look at the linux commands I posted and tell me what is missing or wrong?
page 1of 1 pagesof 2 pages