Recommended method of moving the existing CLM environment on Windows to Linux
Abish Mathew Zachariah (252●5●11)
| asked Nov 09 '14, 7:41 p.m.
edited Nov 10 '14, 11:25 a.m. by Geoffrey Clemm (30.1k●3●30●35) Hi Experts I am in the process of upgrading one of our clients CLM 4.0.3 Standalone environment (CLM 4.0.3, WAS 7.0, RRDI and DB2 9.7) on Windows to CLM 5.0.1, DB2 10.5, WAS 8.5.5 and Insight 1.1.1.5, in a fully distributed environment with reverse proxy on Linux. Since there is no direct migration from CLM 4.0.3 to CLM 5.0.1 from Windows to Linux ( I presume and please correct me if I am wrong), I am in the process of replicating their existing environment in Linux and then upgrade it to CLM 5.0.1. Here are the steps I am planning to perform:
1. Take a back up of Windows CLM 4.0.3 JazzTeamServer directory
Best Regards
|
Accepted answer
Ralph Schoon (63.7k●3●36●48)
| answered Nov 17 '14, 2:37 a.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
If you have a common public URI root (e.g. https://myserver/) than this can be used by the proxy. You don't have to do a server rename, in fact it would be the wrong thing to do.
The applications keep the public URI, they just run on a different machine. Since the proxy forwards all requests they simply are not aware. See the pictures in https://jazz.net/wiki/bin/view/Deployment/RecommendedCLMDeploymentTopologies5 . It is important that the applications think they have the same public URI that is used by the proxy. If the applications don't have a common public URI root (the same hostname/port prefix) you would have to do a server rename to get a common one. Abish Mathew Zachariah selected this answer as the correct answer
|
3 other answers
Ralph Schoon (63.7k●3●36●48)
| answered Nov 10 '14, 2:20 a.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
In general the approach seems to be OK.
There are other files you might want to consider too. See https://jazz.net/wiki/bin/view/Deployment/BackupCLM |
Hi Ralph
Thanks. I have created a staging environment for CLM 4.0.3 on Linux just to replicate their current production environment on Windows ( CLM 4.0.3, RRDI 2.0.x, DB2 9.7 and WAS 7)
Here is what I have tried:
I am now in the processes of upgrading the CLM 4.0.3 on Linux to CLM 5.0.1 (using the CLM interactive upgrade http://www-01.ibm.com/support/knowledgecenter/SSYMRC_5.0.1/com.ibm.jazz.install.doc/topics/roadmap_clm_upgrade.html?lang=en ) and then make it to a full distributed environment with reverse proxy.
I presume I need to do a server rename after upgrading to CLM 5.0.1 to make it to a fully distributed environment. Please correct me if I am wrong or anything I need to consider before this move. Thanks
Best Regards
Abish M Zachariah
|
Hi Ralph
Thanks. I have created a staging environment for CLM 4.0.3 on Linux just to replicate their current production environment on Windows ( CLM 4.0.3, RRDI 2.0.x, DB2 9.7 and WAS 7)
Here is what I have tried:
1.Export the CLM DB2 9.7 database on Windows using Db2move “database name” export –l “
Comments
Praveen Nind
commented Dec 01 '14, 1:36 a.m.
Hi Abish,
Abish Mathew Zachariah
commented Dec 08 '14, 3:10 a.m.
Hi Praveen In case if the applications are on the same machines then I don’t foresee any problems here. In my case I have followed the CLM 5.0.1 interactive upgrade guide to upgrade from CLM 4.0.3.After upgrade I could use the same Public URI to access CLM 5.0.1. Since the client want to change the public URI, I have done a server rename after upgrading to CLM 5.0.1.
Best Regards
|
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.