How to address the OS change with CLM 501
Dear Team,
Currently we are running CLM 501 using distributed topology on windows server 2008 R2 OS.
As the support for Windows 2008 OS is coming to an end by this quarter.
We are looking for ways to get the OS upgraded along with the CLM 501. Let us know the best practices or cases which you have come across.
1. Does performing an In Place upgrade of OS affect the application ?
2. Another option we can think of is to have a new VM setup with Windows 2012 OS and get the CLM 501 installed. During scheduled hours shutdown the current VM running 2008 OS then rename the new VM host to that of old name.
Does renaming the host will have any negative impact on the application ?
One answer
Both approaches are valid. The OS upgrade is obviously the easiest. I am nit sure about performance issues, as this is something that the OS provider (Microsoft) would have to answer.
Assuming the installed applications are compatible with the new OS version, everything should still run.
To change to new hardware/image is basically a new install on the new image and a backup/restore of the old data to the new image, followed by making sure the public URI is resolved for the new server.
See:
https://jazz.net/library/article/686
https://jazz.net/wiki/bin/view/Deployment/BackupCLM
https://jazz.net/wiki/bin/view/Deployment/DeploymentPlanning
There are also several related questions and answers:
https://jazz.net/forum/questions/128796/clmjts-ccm-migration-from-one-server-to-another
https://jazz.net/forum/questions/171406/what-are-the-steps-to-move-to-new-clm-application-servers
https://jazz.net/forum/questions/101883/physically-move-rtc-on-tomcat-from-one-server-to-another-server
https://jazz.net/forum/questions/167513/recommended-method-of-moving-the-existing-clm-environment-on-windows-to-linux
Assuming the installed applications are compatible with the new OS version, everything should still run.
To change to new hardware/image is basically a new install on the new image and a backup/restore of the old data to the new image, followed by making sure the public URI is resolved for the new server.
See:
https://jazz.net/library/article/686
https://jazz.net/wiki/bin/view/Deployment/BackupCLM
https://jazz.net/wiki/bin/view/Deployment/DeploymentPlanning
There are also several related questions and answers:
https://jazz.net/forum/questions/128796/clmjts-ccm-migration-from-one-server-to-another
https://jazz.net/forum/questions/171406/what-are-the-steps-to-move-to-new-clm-application-servers
https://jazz.net/forum/questions/101883/physically-move-rtc-on-tomcat-from-one-server-to-another-server
https://jazz.net/forum/questions/167513/recommended-method-of-moving-the-existing-clm-environment-on-windows-to-linux
Comments
Hi Ralph,
Thanks for the information. I have gone through the links and found the below URL similar to our scenario
Based on this I am going to plan this out and get reviewed by an SME and will take it from there.
Note: I suppose only the Public URL matters and no other values ( I was doubting if the mac address or ip address ) does it make some entries to the application. (jts/ccm/qm and rm)
IP addresses should never appear in any public URI. I think this is made clear by mentioning fully qualified domain name. This domain name should also be machine independent, so you can change the hardware and just change the DNS entry to point to a new hardware.