Issues with RTC 5.0.2 to 6.0 upgrade on IBMi
I did an upgrade from RTC 5.0.2 to 6.0 and encountered the following issues. We run everything on the IBMi (V7R2). I used the interactive upgrade guide. * The DB2 pre-instructions did not work -verify would not run. The RUNSTATS is not applicable on IBMi. The files listed to be checked did not exist in the JAZZ* libraries/schemas. This step also did not have appropriate help links, as none of the links were for IBMi.
Action: skipped this step * None of the RTC502 teamserver.properties files (ie. /QIBM/ProdData/JazzTeamServer60/server/conf/jts, ccm, qm, rm) had the public URL line in them. The RM file was also missing JTS URL. This caused the upgrade scripts to fail. ADDLICPGM for RTC502 apparently did not add those lines as expected.
Action: added public URL, and JTS URL to files and restarted * Restarting the upgrade scripts failed due to locks. Action: ran the QSH command ./repotools-ccm.sh –resetRepoLockId each time for the respective application ( ccm, jts, rq, rm) before rerunning script. * * We have QM and RM installed though we have not used. The QM and RM upgrade steps failed for no apparent reason (based on the logs).
Action: reran upgrade script. Appeared to complete successfully the second time. * Ran the Websphere upgrade with the incorrect product names. The script ran without apparent errors. However it did not complete correctly - we later found the errors buried in the logs. After much research determined problem and reran script. Though the rerun was not clean, and we still had issues to resolve
Question: Should the script have failed if the 502 applications did not exist? This would have let me know there was a problem with the names. Suggestion: We used ccm as the JazzAppName name, when it expected ccm.war. An example would have been helpful. An example of how to enter the maximum heap size would have also been helpful (did we need units, or just the numbers?). * * Verify Upgrade Steps: The 60 teamserver.properties files did not have the public URLs in them. Even though the 502 files had been updated to contain them prior to the upgrade. The publicURLs are not added to the files during a standard RTC6.0 install either (checked this on a clean install on another server) Action: add public URLs to all teamserver.properties files. Has anyone else had any similar issues with the upgrade? Any suggestions to help make it run smoother next time? I have additional servers to upgrade In the near future, and am sure others could benefit from additional information. |
Accepted answer
4 other answers
The problem may be that you are running repotools, upgrade, and was_upgrade scripts from the wrong directory. There are two directories you need to be concerned with. /QIBM/ProdData/JazzTeamServer[502|60]/server and /QIBM/UserData/JazzTeamServer[502|60]/server.
ProdData contains the CLM installation and UserData contains the configuration. As the "Run the upgrade script on IBM i" step in the documentation says, "In QShell, navigate to the Jazz Team Server 6.0 configuration directory /QIBM/UserData/JazzTeamServer60/server." The verify should be run from /QIBM/UserData/JazzTeamServer502/server and the upgrade scripts and was_upgrade script should be run from /QIBM/UserData/JazzTeamServer60/server. When you run repotools and jts/setup, the UserData versions of the teamserver.properties are used and updated. The ProdData version remain in their original install state. Likewise, resetRepoLockId will update the UserData versions of the teamserver.properties. Use -oldJTSHome /QIBM/UserData/JazzTeamServer502/server/conf when running the jts upgrade script. For other applications use -oldApplicationHome with the same value. As for was_upgrade.sh, I will take your suggestion to improve the documentation and operation for this script. You can also look in the script to see the default values that are used by the script. The script will update applications that you installed in both 5.0.2 and 6.0 and will install new applications that you installed in 6.0 but had not installed in 5.0.2. It will not fail if the 5.0.2 applications do not exist, assuming of course the correct names are used. |
|
Thank you for the clarification of the directories. I restored my system back to Rel5.0.2 and tried the upgrade again. I am still having issues.
the verify command worked, but it was still unclear as to which directory to use, I used the one you told me to.
The upgrade script still got an error for missing URI. Here is the print of what I typed.
cd /QIBM/UserData/JazzTeamServer60/server
$
upgrade/jts/jts_upgrade.sh -oldJTSHome
/QIBM/ProdData/JazzTeamServer502/server/conf
got this error:
CRJAZ2106E The Public URL property "com.ibm.team.repository.server.webapp.url
" must be present in the teamserver.properties file "/QIBM/ProdData/JazzTeamS
erver502/server/conf/jts/teamserver.properties". Add the property to the tea
mserver.properties file and set the value to be the URI root that all clients
use to reach the server. The public URI root is essential for the proper fu
nctioning of your server. The upgrade will not succeed without this property.
For more information, see the product documentation topic on "Planning your
URIs".
The jts upgrade failed at step 0. Correct the problem and run the script aga
in starting at step 0.
|
|
Those values were carried over from your 5.0.2 teamserver.properties. The upgrade does not change that location.
Comments That you. I also created this work item https://jazz.net/jazz/resource/itemName/com.ibm.team.workitem.WorkItem/367087 to have the instructions clarified. |
Your answer
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.