/jazz/setup hangs on database connection settings step
I'm in the process of installing RQM 2.0.1 on a new server, a Windows machine with WAS 6.1 on it, using DB2 on another server. This setup will replace a RQM 2.0.0.1 ifix4 setup on WebSphere 6.1 on a Linux server.
I installed RQM 2.0.1 on the Windows server using Installation Manager, then deployed RQM on WAS and updated the LDAP settings on it and configured LDAP group mappings.
I was able to restart WAS, log into WAS console with a user from the configured LDAP server and start RQM's jazz_war from there.
I copied the relevant values from the teamserver.properties on the previous RQM instance running on Linux (with LDAP, DB2 connection and other misc settings).
Then, I started /jazz/setup on the new server, it shows the first screen that allows to choose the installation type and I choose custom setup. It then proceeds to the next screen, database connection settings. A notification appears saying "Loading Database Connection settings..." but it just hangs there.
I double checked the values for the DB2 settings and they are correct.
Just in case, I reset the contents of the teamserver.properties file to see if that might be the cause of the problem, but after restarting WAS, with the default values (i.e. Derby connection values) on the teamserver.properties file, the same problem appears.
Any ideas of what the problem might be?
I installed RQM 2.0.1 on the Windows server using Installation Manager, then deployed RQM on WAS and updated the LDAP settings on it and configured LDAP group mappings.
I was able to restart WAS, log into WAS console with a user from the configured LDAP server and start RQM's jazz_war from there.
I copied the relevant values from the teamserver.properties on the previous RQM instance running on Linux (with LDAP, DB2 connection and other misc settings).
Then, I started /jazz/setup on the new server, it shows the first screen that allows to choose the installation type and I choose custom setup. It then proceeds to the next screen, database connection settings. A notification appears saying "Loading Database Connection settings..." but it just hangs there.
I double checked the values for the DB2 settings and they are correct.
Just in case, I reset the contents of the teamserver.properties file to see if that might be the cause of the problem, but after restarting WAS, with the default values (i.e. Derby connection values) on the teamserver.properties file, the same problem appears.
Any ideas of what the problem might be?
2 answers
Hi Daniel,
You still need to migrate your data, which is currently stored in DB2. Right now, your data is at v2.0.0.1 ifix4 and you want it to be at v2.0.1 in order for it to work properly with your new Windows server. You can use repotools -export to get the data out of 2.0.0.1 ifix4 and repotool -import to get the data into 2.0.1. You should consult the upgrade instructions available for 2.0.1 for more detailed instructions.
Also, keep in mind you don't have to run through the /jazz/setup wizard again if you're upgrading. You always do that on new installs with new data.
You still need to migrate your data, which is currently stored in DB2. Right now, your data is at v2.0.0.1 ifix4 and you want it to be at v2.0.1 in order for it to work properly with your new Windows server. You can use repotools -export to get the data out of 2.0.0.1 ifix4 and repotool -import to get the data into 2.0.1. You should consult the upgrade instructions available for 2.0.1 for more detailed instructions.
Also, keep in mind you don't have to run through the /jazz/setup wizard again if you're upgrading. You always do that on new installs with new data.
Here is the link to the relevant upgrade steps for WAS:
http://publib.boulder.ibm.com/infocenter/rqmhelp/v2r0/topic/com.ibm.rational.test.qm.install.doc/topics/t_instl_upgrade_was.html
Regards,
John Nason
http://publib.boulder.ibm.com/infocenter/rqmhelp/v2r0/topic/com.ibm.rational.test.qm.install.doc/topics/t_instl_upgrade_was.html
Regards,
John Nason
Hi Daniel,
You still need to migrate your data, which is currently stored in DB2. Right now, your data is at v2.0.0.1 ifix4 and you want it to be at v2.0.1 in order for it to work properly with your new Windows server. You can use repotools -export to get the data out of 2.0.0.1 ifix4 and repotool -import to get the data into 2.0.1. You should consult the upgrade instructions available for 2.0.1 for more detailed instructions.
Also, keep in mind you don't have to run through the /jazz/setup wizard again if you're upgrading. You always do that on new installs with new data.